Select to view content in your preferred language

Preserving list selection when navigating between pages

1025
2
Jump to solution
10-17-2024 01:25 PM
OliviaAHobson
Emerging Contributor

Hi everyone! I'm new to EB building, so bear with me. I hope this description is accurate/helpful enough to troubleshoot.

I've created an Experience Builder that features a main landing page that uses a list widget and a dynamic image widget to allow a user to select a point they're interested in, see a preview of an associated image of that point, and then click a button that leads them to a unique page with information about that point. 

I'm running into a problem when I try to return back to that landing page from the specific point page. I'm using a menu in the header that allows the user to jump back to that landing page, but when you use it currently, it resets the selection that had previously been there. So they leave the page looking at Point G, for example, but return to it reset to Point A. It feels clunky to have to navigate back to that Point G manually. If you use the back button on the actual browser, it goes back to the correct selection, but I'd like the user to be able to use the menu buttons as a default.

Is it possible in the non-developer version of Experience Builder to preserve that selection when the user goes back to the landing page, using the header menu buttons? The unique point pages (ex. points A through S) are not included in the menu, if that's relevant. I was trying to research using URL parameters or dynamic filters on this list, but I kept running into road blocks that made me wonder if those things only work in the developer edition. 

Let me know if you need any clarification! Here's a link to the EB (I've had to publish it for the non-AGOL client to preview, so it's out there anyway): https://experience.arcgis.com/experience/5970766d175946439703c7191018dbba/page/Community-Map-Explore...

Thank you in advance! 

0 Kudos
1 Solution

Accepted Solutions
ShengdiZhang
Esri Regular Contributor

Hi @OliviaAHobson ,

It seems that all features in your data have the same URL in the Page Link field. This URL is using the data_s parameter, which stores data selection information. That's why your app keeps returning to the first feature.

ShengdiZhang_0-1729477896701.png

To resolve this, you'll need to modify the Page Link field in your data manually. For each feature, you should update the URL to something like "#data_s=id%3AdataSource_1-18f5c25b007-layer-36%3A2", "#data_s=id%3AdataSource_1-18f5c25b007-layer-36%3A3", and so on, using the object id of each specific feature.

You can find more details about how this parameter works in the Experience Builder documentation. https://doc.arcgis.com/en/experience-builder/latest/build-apps/url-parameters.htm#ESRI_SECTION2_27A9... 

Let me know if you have any other questions.

Regards,

Shengdi

View solution in original post

2 Replies
ShengdiZhang
Esri Regular Contributor

Hi @OliviaAHobson ,

It seems that all features in your data have the same URL in the Page Link field. This URL is using the data_s parameter, which stores data selection information. That's why your app keeps returning to the first feature.

ShengdiZhang_0-1729477896701.png

To resolve this, you'll need to modify the Page Link field in your data manually. For each feature, you should update the URL to something like "#data_s=id%3AdataSource_1-18f5c25b007-layer-36%3A2", "#data_s=id%3AdataSource_1-18f5c25b007-layer-36%3A3", and so on, using the object id of each specific feature.

You can find more details about how this parameter works in the Experience Builder documentation. https://doc.arcgis.com/en/experience-builder/latest/build-apps/url-parameters.htm#ESRI_SECTION2_27A9... 

Let me know if you have any other questions.

Regards,

Shengdi

OliviaAHobson
Emerging Contributor

Solved! Thank you so much for that simple explanation - I'm so pleased it was such a simple solution!