Map selection actions on multiple layers competing to select on a shared related table.

[Ken_Doman]

I've run into a complicated situation with the ArcGIS Online version of Experience Builder and I need some guidance.

To simplify an example, I have a web map with Points A, Multipoints B, Polyline C, and a Table D. Table D has a one-to-one relationship with A, B, and C because it is the tabular version of their data (minus the geometry field). This is all noted in the map service. In Experience Builder, I have a Map widget showing A, B, and C, and a Table widget showing Table D. I have three message actions (one for Points A, one for Multipoint B, and one for Polyline C) to select corresponding items when I select a row in Table D. This works great.

When I add message actions to select rows in Table D when features are selected in Points A, Multipoints B, and Polyline C, I expect that selecting features from all 3 will select related rows in Table D. Instead, because Polyline C was the last message action I added, its rows are selected while the others are not.

Am I missing something, or is this a feature our team will need to wait for?

[JeffreyThompson2]

The Message Actions are designed to create a new selection every time. This is a good default as it is the least confusing to the end user and what the end user wants in almost all cases. I wouldn't expect this to be changed in future updates.

If you use the Select Widget, there are options to select from multiple layers at once and to add to an existing selection. This should better suit your needs. 

[Ken_Doman]

That's what I expected. I know my issue is a little complicated.

The users are using the Select widget to select multiple features on the map, and they expect that the table widget would have all those same selections. They also requested that all the features be combined into a single table, rather than separate tabs for each feature layer. To handle the second request, I published a table view on the SQL side to union all the feature data into the same table (minus the geometry). I thought the related data would be selected as well, but that hasn't proven to be the case so far.