In Experience Builder, one of the first thing that comes to my mind when developping an app to explore datasets, is using a list. So my basic app template often goes (1) list to the left of the screen and (2) map to the right. However, I always find myself strugling with making the list and the map work in sync. It's like they were not made to be use together when it should in fact be a core feature of Experience Builder. Let me explain.
Let say I have two datasets in a map :
- Polygons of lakes
- Points (centroids) of lakes
Dataset 1 (the polygons) are used to feed the list. I then set two filter actions :
- List action - when a lake element is selected in the list, filter the centroids with the corresponding lake id.
- Map action - when a lake polygon is selected on the map, filter the centroids with the corresponding lake id.
I would expect these two filters to work in sync and allow me to select a lake either by using the map or the list and that there would be no problem. However, both these filters act independantly making them impossible to use in pair. When the list filter is active, and a map filter is then activated, the app tries to filter the already filtered data making all centroids disappear. When a lake polygon is selected in the map, the corresponding list item is highlighted (showing that the app recognise that it's the same feature class), but the "Erase selection" button in the list does not clear the map filter.
In short, make the filter actions of both list and map work in sync please.
