topic Re: Add null override category to selector in ArcGIS Dashboards Questions

Add null override category to selector

JoeBryant1 — Thu, 18 Apr 2019 15:43:45 GMT

I'm trying to add a Category Selector to my dashboard that selects by "Receiver" from the GNSS metadata field populated from the Collector App. Looking at my data, the high accuracy receivers and the iOS devices populated the field, but if the editor was using an Android device (and the new Collector Beta for Android), the receiver field is blank (null).

I have successfully loaded all of the categories that have defined values, but I would like to add the null value records and label the category as "Android".

When using the "+ Override" button, what string do I need to enter to select the blank or null values? I've used "", null, {}, {null} and " " with no luck.

Re: Add null override category to selector

MaximeDemers — Tue, 02 Jun 2020 19:35:21 GMT

Hi Joe,

I have the same quesiton. Have you found something for this?

Re: Add null override category to selector

JoeBryant1 — Tue, 02 Jun 2020 21:18:04 GMT

Hi Maxime,

I went back and reviewed this dashboard and it looks like I never figured it out. I have a loaded category value that is blank that I have labeled "Android", but I don't have this choice in smart-filter buttons, so the app must not recognize that value when it populates.

Maybe a good enhancement request?

Re: Add null override category to selector

MaximeDemers — Wed, 03 Jun 2020 13:48:44 GMT

Thank you for your reply. In my opinion, yes that would be a good enhancement idea. If you want to make the suggestion, please share the link here and I will give a thumbs-up.

Re: Add null override category to selector

WillHughes — Mon, 10 Aug 2020 18:06:28 GMT

Did someone create an enhancement request? Please share.

Re: Add null override category to selector

JoeBryant1 — Mon, 21 Dec 2020 18:07:35 GMT

I thought I had piggybacked this onto another request, but I couldn't find it in the new ESRI Community forums.

Here is the Idea I just created. Please upvote!

Add Null Override Category to Dashboard Selector

Re: Add null override category to selector

JayHodny — Tue, 16 May 2023 20:48:21 GMT

Hi Joe et al on this thread......I was trying to make this same idea happen, then found your posts. I have a Survey123 Connect survey (editable) embedded in an internal review Dashboard. The Survey is completed by residents and provides information on their water service line, as part of our lead service line inventory program. Once the survey is submitted, we review the information internally, and select 'Yes' if we conclude the service line is properly identified (validated) or 'No' if we conclude we need to investigate further (invalid). The field remains "empty" in the survey attribute table until we select yes or no. I would like the Category Selector to List All, Validated Surveys, Invalid Surveys, and those Waiting Validation. The last category is the one in question - how can I list only those survey records still waiting our review? I am guessing I may have to add a "null" choice to the yes/no choice list in the Connect XLSform, to get this to work. Any other ideas are welcome. I did upvote your idea. Regards, Jay

One of my many iterations......clicking on 'Waiting Validation' returned 'No Data' in the element.

Re: Add null override category to selector

PaulodeCastroVilli — Wed, 28 Jun 2023 18:03:45 GMT

If you want a component to hide records with Null value in that attribute used for the categories, you can use a filter

If not, you'll probably need to use Arcade to replace Null with "Android" in an Arcade data source based on your current data source:

Documentation: https://developers.arcgis.com/arcade/profiles/dashboard-data/
Arcade Data Source Examples: https://github.com/Esri/arcade-expressions/tree/master/dashboard_data

Re: Add null override category to selector

Evan_Sepa — Thu, 09 Jan 2025 00:17:39 GMT

Some workarounds...

1) If you are working with survey123 create a new field that has the calculation

if(${FIELDNAME}!='',${FIELDNAME},'desired_value')

you can even add in a relevant of

${FIELDNAME}!=''

This will be a complete duplicate of the existing field but with 'desired_value' instead of NULLs

2) Similarly, if you can create a view layer in your own GDB / server service then create a view layer with a field that autocalcs from the main field... essentially duplicating the original field but with 'desired_value' instead of NULLs

SELECT CASE WHEN field_name IS NULL THEN 'desired_value' ELSE field_name END AS new_field_name FROM table_name

You should be able to use the new field in either case to get the results you need from filters.

Re: Add null override category to selector

Evan_Sepa — Thu, 09 Jan 2025 00:20:09 GMT

Some workarounds...

1) If you are working with survey123 create a new field that has the calculation

if(${FIELDNAME}!='',${FIELDNAME},'desired_value')

you can even add in a relevant of

${FIELDNAME}!=''

This will be a complete duplicate of the existing field but with 'desired_value' instead of NULLs

SELECT CASE WHEN field_name IS NULL THEN 'desired_value' ELSE field_name END AS new_field_name FROM table_name

You should be able to use the new field in either case to get the results you need from filters.