Change View when Selection is Cleared

Question

With the recent update, a much needed feature for me was added, where selecting a feature in a map widget can be used to change the view/section. This allows me to show the feature info widget over top of a list (similar to the old Shortlist StoryMap template) and it works beautifully.

What I am wondering now though is if there is a way to have it revert the view back to the other view (list) when the selection is cleared? Now when I click off of an item in the map without selecting a new item, it just shows the default page without any of the data filling it in or reverts to the initial item in the list of features. Maybe I'm thinking too hard on this but I am wondering if it's possible? Some sort of "only render when there is a selection" type thing like in the Operations Dashboard items?

Shen_Zhang · Answer

This workflow is supported by a combination of new features in the June release.

You can now set a default view for a Section widget. The default view will be loaded for the first time when loading the app/section widget.

For the Open view action, it is possible to return to the default view of a Section widget when the selection is cleared.

Please refer to the Section documentation for more details: https://doc.arcgis.com/en/experience-builder/latest/configure-widgets/section-widget.htm#:~:text=Return%20to%20default%20view%20when%20selection%20is%20cleared

HuajunChenGarland · Answer

@Shen_Zhang

I’m experiencing the same issue as Robert. When a user unselects an item instead of clicking the back button I provided, the panel continues to display the feature information rather than returning to the item list as intended. This function is very important, so I’d really appreciate it if you could look into it.

Thank you very much!

Shen_Zhang · Answer

@RobertAnderson3, this is a really good way to go! But unfortunately, I don't think this is possible with open view action for now. A possible workaround is to add a button to do that, which I assume you must already know. I'll discuss with the team and see what's the best way to do this. Thank you for the idea!