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.
Hi all, this issue should have been fixed and patched. Let me know if you still see the problems. Make sure to clear the cache first. (Your service version information is still helpful, if possible)
@NeilWebber I tested your app; it looks good now - FYI.
@TonghuiMing I have now found another problem with ExB data filtering that seems to be too much of a coincidence not to be connected with this acknowledged issue.
A List widget has a data source. That data source can be filtered via the settings for the data source in the Content tab (Filter/Sort/Records)
No filter applied, Yes/No values in a field
With a 'Field IS Yes' filter applied (i.e. Unique values), no values are returned where there should be many
With a STARTS WITH filter applied the results are as expected
This suggest to me that the same 'Unique Values' issue that affected the Filter widget is also manifesting in other applications of data filtering within ExB framework.
Thanks, Neil
@TonghuiMing also confirming as fixed - many thanks for your help.
It is fixed, thank you! Version 11.3
@TonghuiMing Thank you - the issue has been resolved in my apps 😊
Were on 11.1. Thank you, I no longer see the issue!
@TonghuiMing Service version here is 11.3
And further to @DennisDKing, we are also using Oracle SDE backend
@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.
@ChristinaNeal @DennisDKing @hamini @NeilWebber @LJackson29
In addition, it would be helpful for our follow-ups with the service colleagues if you could provide us with your service version. Thank you.
Thank you all for the feedback. We have received the details from support and will take a look at this. Sorry for the inconvenience.
@hamini Thanks for pointing out the string field type.
We are also having the same issue. For us, it seems to be the last part of the query being sent to ArcGIS Server and looks something like: %20and%20((PROJECTNUM%20IS%20NOT%20NULL)%20AND%20(PROJECTNUM%20%3C%3E%20%27%27)
PROJECTNUM%20%3C%3E%20%27%27 (PROJECTNUM = '') is the part that makes it return 0 rows from the ArcGIS Server Query.
Support was not able to reproduce but they were using SQL Server. Our SDE backend system is Oracle. Not sure if that is a factor.
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.
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 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).
@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
@Jianxia Per @NeilWebber Ours are also related to published services. We will open a ticket.
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.
@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?
@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 ">😐
Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
