I'm trying to set up an Experience with a layer that can be filtered on one of two potential fields using URL parameters. Based on answers to some other forum posts, I've embedded the "main" experience within a "shell" experience and am trying to set up the URL parameters. It seems like the software is having trouble accepting the multiple field options.
In the Embed widget setup within the "shell" app, the URL I've created is:
https ://arcgis.[ORG]/portal/apps/experiencebuilder/experience/?id=[MAIN-APP-ID]&data_filter=[DataSource1]:CO_CODE%3D%27{appURL.search.co_code}%27,[DataSource1]:CTU_ID%3D{appURL.search.ctu_id}
The goal is that the end user can visit the app and have DataSource1 automatically filtered by either the co_code text field or the ctu_id integer field:
https ://arcgis.[ORG]/portal/apps/experiencebuilder/experience/?id=[SHELL-APP-ID]&co_code=003
OR
https ://arcgis.[ORG]/portal/apps/experiencebuilder/experience/?id=[SHELL-APP-ID]&ctu_id=2393954
But in practice, this will only work for whichever parameter is listed last in the Embed widget setup. For the example above, the filtering works with ctu_id but not co_code. If I swap the order of them (.../experience/?id=[MAIN-APP-ID]&data_filter=[DataSource1]:CTU_ID%3D{appURL.search.ctu_id},[DataSource1]:CO_CODE%3D%27{appURL.search.co_code}%27), then the filtering works for co_code but not for ctu_id.
Any suggestions on how to solve this? This is in Enterprise 11.3, I believe.
