I'm the process of creating an Experience that has two main views: a List of buildings (the default view) and a Map showing the location of the buildings. I also have a third element: the Feature Info widget to display the popup of the selected feature. The default List view looks like this:
The 'Details' link on each building card is a Button that is opens the Feature Info widget for the relevant building:
The problem I'm having is that if the user presses any of the Details buttons without going to the Map tab first, the details don't display:
It only works if you go to the Map first. After the map has loaded the Details buttons work fine:
It's like the app hasn't loaded the map so isn't able to access the feature popup info until the map has been loaded.
Does anyone know if there is a way around this (other than making the map the default view, which I don't want to do for this application)?
Solved! Go to Solution.
@MappyIan are you using the mode "Interact with a Map widget"? If so yes it does need a map to load first.
Can you try using standalone data by "Select data" mode?
Try this: Go to the Data Panel in the Left Sidebar and Add Data. Find your spaces Feature Layer from whatever source you used in the Webmap, but not the Webmap itself, and add it as a new Datasource. Now change your Feature Info Widget to this Datasource. It should load regardless if the Map has loaded or not. I think it should still work with the Map Actions as well, but you should check that before deploying.
Hi @JeffreyThompson2, thanks for the reply and suggested workaround. Sadly I've not been able to get it to work in a way that is acceptable. Changing the data source to the standalone Feature Layer does indeed mean that the data loads fine when pressing the Details button without first going to the map. There are however two problems:
Thanks for taking the time to respond, but I'm wondering if this original problem is a limitation (or maybe even a bug) in Experience Builder.
Thanks @Wei_Ying. I did have it set to 'interact with a Map widget' because I want it to show the Feature Info (popup) as configured in the Web Map. But having set it to 'Select data' and pointed it at the same layer within the map it seems to work fine, which is great. I had got around the problem by adding a second Map Widget to the List but hiding it behind the List so it wasn't visible, but I can remove this now as your solution has worked perfectly.
Thanks again - Ian