topic don't show null values in popup in ArcGIS Online Questions

don't show null values in popup

temprobertcottreau131313 — Tue, 12 Dec 2023 15:00:25 GMT

I have a layer with about 50 fields that show up as 50 rows in the popup. Most of these are Null values.

Is there a way to create an expression that will set it up to not show the fields with Null values in the popup without typing 50 expressions?

I've seen HTML solutions and ideas for Map Viewer Classic but I'm using the New Map Viewer.

Thanks to all.

don't show null values in popup

temprobertcottreau131313 — Tue, 12 Dec 2023 14:59:37 GMT

I have a layer with about 50 fields that show up as 50 rows in the popup. Most of these are Null values.

Is there a way to create an expression that will set it up to not show the fields with Null values in the popup without typing 50 expressions?

I've seen HTML solutions and ideas for Map Viewer Classic but I'm using the New Map Viewer.

Thanks to all.

Re: don't show null values in popup

jcarlson — Tue, 12 Dec 2023 15:13:54 GMT

Yes! You can do this very easily with an Arcade popup element and a single expression. You can build a fields list object programmatically and check for nulls and skip them.

The simplest approach is to just iterate over every attribute in a feature:

var fieldInfos = [] var attributes = {} for (var att in $feature) { if (!IsEmpty($feature[att])) { Push(fieldInfos, {fieldName: att}) attributes[att] = $feature[att] } } return { type: 'fields', title: 'An Expression to Skip Nulls', fieldInfos, attributes }

Here it is in action, with a regular fields list to show it working:

If you have certain fields you want to skip, you can code those in, too. It sounds like there are a lot of attributes you want to catch, so I don't know if it's going to be faster to grab *everything* and then remove ones you don't want, or to manually define the list of attributes you do want. But this should get you started.

Re: don't show null values in popup

BlairMcclenathan — Tue, 12 Dec 2023 15:27:09 GMT

This is how I've accomplished this, its a little manual since you have to add the fields induvial but it loads quickly and works well for our applications (add an arcade element then add the code to that):

var fieldInfos = []

if (!IsEmpty (Trim($feature.facilityid))) {

Push (fieldInfos, {fieldName: 'FacilityID', label: 'Facility Identifier'})

};

if (!IsEmpty (Trim($feature.ownedby))) {

Push (fieldInfos, {fieldName: 'Owned By', label: 'Owned By'})

};

if (!IsEmpty (Trim($feature.presentstatus))) {

Push (fieldInfos, {fieldName: 'Present Status', label: 'Present Status'})

};

if (!IsEmpty (Trim($feature.comment))) {

Push (fieldInfos, {fieldName: 'Comment', label: 'Comment'})

};

if (!IsEmpty (Trim($feature.flowtestcomplete))) {

Push (fieldInfos, {fieldName: 'Flow Test Complete', label: 'Flow Test Complete'})

};

if (!IsEmpty (Trim($feature.inspectionResult))) {

Push (fieldInfos, {fieldName: 'Inspection Result', label: 'Inspection Result'})

};

if (!IsEmpty (Trim($feature.flowtestcomment))) {

Push (fieldInfos, {fieldName: 'Flow Test Comment', label: 'Flow Test Comment'})

};

if (!IsEmpty (Trim($feature.flow))) {

Push (fieldInfos, {fieldName: 'Flow Rate', label: 'Flow Rate'})

};

if (!IsEmpty (Trim($feature.flushingzone))) {

Push (fieldInfos, {fieldName: 'Flushing Zone', label: 'Flushing Zone'})

};

if (!IsEmpty (Trim($feature.firestation))) {

Push (fieldInfos, {fieldName: 'Fire Station District', label: 'Fire Station District'})

};

if (!IsEmpty (Trim($feature.lastflowtest))) {

Push (fieldInfos, {fieldName: 'Last Flow Test', label: 'Last Flow Test'})

};

return {

type: 'fields',

fieldInfos: fieldInfos,

attributes: {

'FacilityID': $feature.facilityid,

'Owned By': DomainName($feature, "ownedby"),

'Present Status': DomainName($feature, "presentstatus"),

'Comment': $feature.comment,

'Flow Test Complete': DomainName($feature, "flowtestcomplete"),

'Flow Test Comment': $feature.flowtestcomment,

'Flow Rate': $feature.flow + ' GPM',

'Flushing Zone': DomainName($feature, "flushingzone"),

'Fire Station District': DomainName($feature, "firestation"),

'Last Flow Test': (month($feature.lastflowtest) + 1) + '/' + day($feature.lastflowtest) + '/' + (Year($feature.lastflowtest)) + ' at ' + Hour($feature.lastflowtest) + ':' + Minute($feature.lastflowtest)

}

Re: don't show null values in popup

KenBuja — Tue, 12 Dec 2023 15:39:37 GMT

I noticed that your code doesn't show the field aliases (if they are present). Here's a modification that shows them.

var fieldInfos = [] var attributes = {} var fields = Schema($feature).fields for (var att in $feature) { if (!IsEmpty($feature[att])) { var alias = att; for (var i in fields){ if (fields[i].name == att) alias = fields[i].alias } Push(fieldInfos, {fieldName: alias}) attributes[alias] = $feature[att] } } return { type: 'fields', title: 'An Expression to Skip Nulls', fieldInfos, attributes }

Re: don't show null values in popup

jcarlson — Tue, 12 Dec 2023 15:43:42 GMT

Good addition!

Re: don't show null values in popup

edward33 — Thu, 25 Apr 2024 17:38:12 GMT

@BlairMcclenathan

Do you know how I would add rounding to this? I tried something like-

'Flow Rate': round($feature.flow, 2)

in the return section but that doesn't seem to do anything.

Re: don't show null values in popup

Michael_V307 — Mon, 17 Jun 2024 15:36:38 GMT

Hey @jcarlson ,

I am trying to use your code but my popup does not look anything like what you are showing. My popup only shows gloablId, objectID, and one other attribute from the layer. I changed the code just to return attributes but that only results in the 3 attributes I mention of about 100, that could have data. Curious if you might have any suggestions?

Thanks

Re: don't show null values in popup

AlderMaps — Fri, 25 Apr 2025 21:02:13 GMT

Reviving an old thread here; I am noticing this today @Michael_V307 and I cannot figure out what is going on. I have tried my own code, the code from both @jcarlson and @KenBuja, on my layer and several random layers from the Living Atlas. For some reason these are not catching all (or even most) of the populated attributes in these features.

Attaching screenshot of popup generated by one of the above solutions and table with values not showing up in the popup. Have been pounding my head against a wall for two days now trying to figure out what is going on, but it appears to be a systemic problem...bug...?

Re: don't show null values in popup

KenBuja — Mon, 28 Apr 2025 13:48:27 GMT

Can you post your code?

Re: don't show null values in popup

KimberlyK — Wed, 18 Jun 2025 18:44:00 GMT

@edward33 Did you ever find a solution to your issue with formatting? I am experiencing the same thing. Thanks.

Re: don't show null values in popup

MDB_GIS — Wed, 01 Oct 2025 20:44:53 GMT

Does this still work for you? It does hide some fields, however the problem is that it hides fields that have data in it it as well. Here is a sample popup from our data:

Here is a screenshot of the selected feature's attribute table:

As you can see, there are several additional attributes that are populated, but are not shown in the popup.

Re: don't show null values in popup

JamesTurner2 — Tue, 05 May 2026 15:28:09 GMT

I am having the same issue, the fields that populate seem to be random. When you run the code in the arcade editor it seems to return the right data. If you add a field list element to the pop up then everything seems to populate just fine. There must be an issue in the background. It seems to work as expected if the map is opened in Field Maps, but not a web map.

I have had a similar issue before with fields being used in the title or description of a pop up's field list - if the field is not included in the field list itself, it does not populate in the title/description.

I am working in Enterprise 11.5