Hello,
I'm looking for information on how Experience Builder evaluates records selection changes from one widget to another. In my case, I have map that has features from three different layers. I also have a list widget that contains a table from a sql view that unions all three of those layers (different geometry types, same schema). When the list is populated with a table, the option to zoom to a selected feature on the map is not present, even though the list can correctly select the feature on the map based on matching GlobalIDs.
So I thought, let's try adding a hidden table widget with those layers contained therein, and have that widget do the zoom-to on record selection. So the setup would be:
1. List widget: user clicks, Message Action triggers the selection in the table
2. table widget: Hidden behind the map, the table widget receives the record selection change from the list, then has it's own Message Action to zoom to selected feature on the map
3. Map widget: zooms
Unfortunately it didn't work like I want, so I'm left wondering how it would be possible to string together those selections, if indeed it is possible, or if there's a better/simpler way to trigger a map zoom from a list widget containing a table.
Hi @ZachBodenner,
@ZachBodenner wrote:
I also have a list widget that contains a table from a sql view that unions all three of those layers (different geometry types, same schema). When the list is populated with a table, the option to zoom to a selected feature on the map is not present, even though the list can correctly select the feature on the map based on matching GlobalIDs.
Currently zoom to or pan to is not supported when using a table without geometry.
@ZachBodenner wrote:
how Experience Builder evaluates records selection changes from one widget to another.
When a record is selected in a widget, the widget sends record selection changes to the Map widget, which receives them and processes them accordingly.
The select view is shared between widgets. So when you add List, Table widget, and they use the same data source. When you click a record in List, the record in Table will also be selected. But record selection changes are sent by List widget.
Thanks,
Ke
Thanks for the response,
So my list widget has that SQL view table, but my Table widget has that table as well as the tables for the geometry features. If I understand correctly, you're saying that it is not possible to have the list select a record from one of the geometry features in the Table widget, and then have the Table widget trigger a selection on the map?
Yes, SQL view table is a table with no geometry.