nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Experience Builder Filter Widget - Unique Values list not populating properly

RInfante

Hello,

I've just started to have an odd issue with an app I'm building on AGOL's Experience Builder. By 'started' I mean it was working fine last week when I demo'ed it to the client but now it doesn't work anymore.

I have a filter that should allow a user to pick a specific attribute value so they can see only the applicable features in an overlay layer.

My problem is the list of unique values is no longer populating properly on desktop - the pull-down menu shows only one or two values instead of the full list of twenty or thirty it should be showing.

See the screenshot below.

The funny thing is, if I turn on Developer Tools in the Chrome Browser I'm working on (I thought maybe something had broken in the back end), the list then shows all the proper values!

The filter also works properly on the mobile version I'm developing of the same app.

Does anyone know what's going on and what a solution/workaround might be? To recap: this is on a Chrome browser, using AGOL's Experience Builder.

Any help or insight would be much appreciated. Thank you!

Find more posts tagged with

ArcGIS Online

Accepted answers

All comments

TonghuiMing

Based on your screenshot, you might have another issue than that of this original post. Refer to the following post for more details

https://community.esri.com/t5/arcgis-experience-builder-questions/query-widget-unique-values/m-p/1353951#M9571

JohnnySun

Any update on this?

I am having similar issue with the unique values list not showing the full list on the Filter widget.

We are under the environment of enterprise 11.2

Cepero_Eudel

The ESRI representative we contacted said an internal note was added to the Bug with the info as well as the screen shots we share with him. Thank you

TonghuiMing

Hi @Cepero_Eudel

Glad to hear that you've pinpointed the issue. We have come across the distinct + geometry combination conflicts before. It looks like your problem is also caused by the limited advanced query capability of the service.

Same with https://community.esri.com/t5/arcgis-experience-builder-questions/filter-widget-dropdown-empty-when-data-filtered-by/td-p/283206

(FYI - per checking, BUG-000161315 does not seem to be the same issue)

Cepero_Eudel

Update.

There is ESRI BUG-000161315 on this.

Our findings. Attribute query on a map server produce an Input Geometry in the REST that is making the query to fail, see REST image. When this Input Geometry in the REST is deleted the query works.

In addition, if you remove the “return distinct values” and keep everything the query works with all the parameters set by the Experience Builder call. See error in the database image.

We have tested the same Attribute query in the same layer but hosted in AGOL without any problem.

Query.png

TonghuiMing

I see the data is in gdb, and I am not sure if I publish it the service definition would be the same with yours. Is there a published service that you could share with us? I want to take a look at the detailed specs.

Cepero_Eudel

One more thing, this is happening only with numeric fields. I try with Zip code and got the same behavior.

The Asset ID and Zip code fields are in Long numeric format.

Cepero_Eudel

Hello,

Thank you for answering.

Environment is AGOL, data is a feature service hosted in 10.71 ArcGIS server. Data attached.

Noted on the Expression builder the values are listed and populated properly once moved to Live view it get stuck. Thank you

TrafficSignal.gdb.zip

TonghuiMing

@Cepero_Eudel Which environment are you on - AGOL/enterprise? And what is the version? Similar issue might relate closely to the data so it would be helpful if a sample data/app is provided.

Cepero_Eudel

Hello, any update on this?

I am having similar issue with the unique values list not populating properly on the Query widget.

Below the same data and widget in Builder, to the left, and Experience to the right.

Thank you

TonghuiMing

Hi @RInfante, do you want to share the app/data with us to take a look at? That's quite interesting...if the data source hasn't been updated.

RInfante

Follow-up:

It appears that the issue isn't the Filter widget, as I tried using a Query filter and got the same issues. What I'm actually seeing is that it's the layer itself that isn't working on the related map if the app is set to use a desktop-size screen (as in my original post, small screen sizes work alright).

I realized this after I tried setting up the Filter to use the predetermined values option (where I load each one manually). What I saw is that the full list popped-up properly...but switching to different values didn't do anything...as if the layer were turned off or not there in the first place.

That's when I went back to my original map to try and see if maybe there was an issue with the layer in Map Viewer - but no, everything was working fine.

So I left the layer on by default, saved the Map, and sure enough: it wasn't showing up in the app's embedded version of the same map. I went back to playing with the developer tools and screen sizes (all while having the layer in question turned on) - and found that when the screen size dropped below 1000 pixels (and the mobile versions kicked in), the layer showed up as expected...but as soon as those 1000 pixels were exceeded and the Desktop version kicked in the layer just disappeared.

So, it appears that the app can't read that layer properly at those screen sizes. The Filter widget loaded the predetermined values only because I manually 'hardcoded' them within the app itself - but otherwise it's like it just can't connect to the layer to read the proper unique values, or even display it in the map.

Has anyone ever heard of anything like this happening? The really odd thing is that this was working fine just last week! It's not like there was some sort of AGOL update that maybe have jumbled things around!

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.