Question about query strings showing up on popups

DeanWilson — Fri, 18 Apr 2025 14:07:58 GMT

Hi All!

I've been looking for awhile and I'm not finding a reason why when I click on a webmap to show a popup in a deployed ExB application, it's adding this:
#data_s=id%3AdataSource_1-19547facb76-layer-17-7%3A88283
in the URL. I can use my custom search widget and it finds features and whatnot all day. But when I click on the feature on the map, or even when I click on a result item in my custom search widget, it shows this querystring data in the url.

Now I know that if I copy the entire url and use it in a new browser window it'll show the mapping app as well as the highlighted feature that's been clicked on.

My question (other than the fact that it requires a login to display, which may be the reason I DON'T use ExB and go back to WAB) is why it automagically adds that data to the end of the url? Is there somewhere to configure it to NOT do that?

I'm flagging @JeffreyThompson2 since he seems like an excellent resource to get ahold of. Anyone that has any answers for me are welcome to reply too.

Thanks again!

- Dean Wilson

Re: Question about query strings showing up on popups

TimWestern — Fri, 09 May 2025 16:50:33 GMT

The #data_s=id%3AdataSource_1-19547facb76-layer-17-7%3A88283

Is indicating which datasource and layer its trying to use. Some of the widgets seem to update this on their own. If you were developing a custom widget and looked at the useDataSources array for what is configured in the widget or application, you might see a corresponding datasource id or layer id that references them. I presume they are indicating some kind of selection that occurs as you use the map/experience/widgets, but have not seen anything 'definitive' about why they appear in the address url.

topic Re: Question about query strings showing up on popups in Experience Builder Custom Widgets

Question about query strings showing up on popups

Re: Question about query strings showing up on popups