Filter Widget - All Unique Values of this Field Error

[ChristinaNeal]

Hi, our experience builder app is having issues populating the options within the filter widget when set up to use "All unique values of this field." The list is blank even though this used to work before. I have tried recreating the filters and that did not make a difference.

[LJackson29]

@Jianxia  We are also experiencing this issue on a number of different experience builder apps. I also tried recreating filters and that did not resolve the issue. Please, fix this 😐

[Jianxia]

@ChristinaNeal and @LJackson29 , thank you for letting us know. I was not able to reproduce it. Could you share a reproducible app or contact Esri Support?

[LJackson29]

@Jianxia Per @NeilWebber Ours are also related to published services. We will open a ticket.

[NeilWebber]

Also confirming the same issue, but in my case it seems to be specifically with published web services. Appears to work OK with hosted data sources. 

I have lots of ExB apps that use 'all unique values' filters, all of which were working perfectly before Friday's update, but no longer populate with options as per Christina's post. 

[TonghuiMing]

@ChristinaNeal  @LJackson29 @NeilWebber 

While we haven't seen the issue details in the support system, I am wondering this - 

Can you go to your referenced service URL, find the actual layer you're using, and go into the "Query" function:

After that, don't change anything, just put 1=1, and click enter

All the problematic referenced layers that I could find, they share some sort of database error:

The ones that work fine, the filter unique work fine.

These are just my preliminary findings before the sample is provided. I am wondering if you share the same issue.

Tonghui

[LJackson29]

@TonghuiMing Thanks for looking into this. All the layers I am having issues with are services published to our enterprise portal and then pulled into AGO and used in a map that is used in an experience builder app. In AGO I am not able to access the rest end point. In portal, I tried your steps above for several services and received no error. @ChristinaNeal and I have a call with ESRI support today (Esri Case #04210604 - Experience Builder Filter Issue).

[NeilWebber]

Hi all

@TonghuiMing I've queried as suggested and get no errors on any of my problematic feature services

I've made this ExB as an example of what happens - all data is public so no issue posting it here. Not sure how I can share it so you can see the underlying build (i.e. in Edit mode)?

Test ExB

All of my ExB filters that use published services demonstrate this error. Fine last thursday, not working now, no changes made at this end.  Rebuild from scratch still shows the error, as per the test ExB.

[TonghuiMing]

@NeilWebber Thank you very much for the app and the detailed illustration! That would work as a great addition for verification when we go ahead and fix it.

[hamini]

Hi, 

We are seeing the same issue. All Experience Builder filters that are set up off text fields based on unique values do not load the data. Number fields appear to be working fine and setting up predefined unique values instead appears to be working fine. We are using published feature services.