I have a project based on Survey123 Connect forms and an Experience Builder front end.
Users access the main page, which has a list widget with a list of Incidents populated from feature service A. The list item has a button that links to page 2 using a URL, not through a page link, to allow for URL parameters to be passed from the data.
On page 2, there are a variety of list widgets that hold buttons are linked to windows that hold embed widgets linked to Survey123 web forms. When I interact with any of these list items, it selects the list item, changing the URL and encoding the URL parameter delimiters.
The URL looks like this before interacting with list items on page 2:
https://experience.arcgis.com/experience/<EB App ID>/page/<Page 2 Name>/?data_filter=<Feature Service B Datasource ID>:<Field Name>%3D%27<Incident Name>%27,<Feature Service A Datasource ID>:<Field Name>%3D%27<Incident Name>%27
After interacting with a list item's button to open a window, the URL looks like this, even after I close out of the window to return to the current page:
https://experience.arcgis.com/experience/<EB App ID>/page/<Page 2 Name>/?data_filter=<Feature Service B Datasource ID>%3D<Field Name>%3D%27<Incident Name>%27%2C<Feature Service A Datasource ID>%3D<Field Name>%3D%27<Incident Name>%27
When the user goes to refresh the app page in the browser, this breaks the URL parameters and the filter parameters do not function as intended. Am I missing a way to preserve delimiters in an unencoded state when using button links, or is this a limitation I will need to have users learn to work around? Ideally, we would want to preserver delimiters in an unencoded state.
