The Experience Builder that I am working on uses the following URL parameter configuration to filter three different data sources that all share the same "Project_Name" attribute to filter towards a specific project (in this case "Random Project"):
https://experience.arcgis.com/experience/[id]/?data_filter=dataSource_2-190a2477a07-layer-4:Project_Name%3D%27Random Project%27,dataSource_2-190a2477a08-layer-6:Project_Name%3D%27Random Project%27,dataSource_2-190a2477a06-layer-3:Project_Name%3D%27Random Project%27
This works great the first time a user loads the page and can be verified as there are three lists in three different views that display the three data source's features after the filter has been applied. However, once the page has been refreshed, the filters appear to be inverted as the lists/map will display features for everything other than "Random Project".
I've noticed with only one data filter applied this does not occur, it is only when multiple filters are applied that this happens.
Appreciate any advice!
Hi BrianGiroux,
I couldn't reproduce this issue with the app: https://experience.arcgis.com/template/796c161a968246da84799fc298f96b11/?data_filter=dataSource_1-Be...
Could you have try at your side?
Thanks,
Ke
Ke_Xu,
Thanks for the quick response. With the link you provided, I am also not seeing the error occur.
A potential difference is the use of sections within my Experience Builder which modify the URL once the app has been opened. For example, the following URL is when a viewer is on the second section using Views Navigation:
https://experience.arcgis.com/experience/[id]/?data_filter=dataSource_2-190a2477a07-layer-4:Project_Name%3D%27Random Project%27,dataSource_2-190a2477a08-layer-6:Project_Name%3D%27Random Project%27,dataSource_2-190a2477a06-layer-3:Project_Name%3D%27Random Project%27&views=View-2
Are you able to add sections to your app that contain lists of the different layers being filtered and see if the error can be replicated this way?
-Brian
After clicking on the Views, then refreshing, issue could be reproduced. I will let you know once issue is fixed.
Thanks,
Ke
Much appreciated. Thanks Ke.
-Brian
@BrianGiroux This issue has been fixed in the November 2024 release.