I've run into a potentially undocumented limitation with Joined Views and Experience Builder, and am wondering if anyone has run into this before or could replicate/enlighten.
As a simplified example—say I have an ExB app with just a Filter widget and a Table widget. The Table widget has two Sheets in it, and both sheets point to different Joined Views which share a common join layer (an ArcGIS Online hosted feature layer (Layer A)) but use different target layers in their joins (two other ArcGIS Online hosted feature layers (Layer B and Layer C)). So one Joined View is Layer A + Layer B and the other is Layer A + Layer C. Layer B and Layer C both share a field that contains common data, let's say colors, as an example. The Color field in both Layer B and Layer C are string fields and do not use Domains, however the Values inside the field do match across both layers. So there is a "Red" in both fields of both layers, a "Green", etc. etc. The only difference between the fields is the name (example: one is "Color" and another is "Colour").
I set up my Filter widget to have a Group Filter set up to "Ask for Values" (Unique), using the Color/Colour fields from my Joined Views.
When I go to test, I get a dropdown for Colors as expected and select my choice. In the Table widget, however, only one of the sheets gets filtered. Whichever Joined View in the Group SQL Expression that was used as the "Main field" gets filtered in the table, while the other does not. If I switch the "Main field" in the expression to use the other Joined View, then the other sheet gets filtered in the table, and not the first.
Unlike single data filters (non-Group Filters), I can't actually see what the underlying SQL looks like, so I'm unsure if the cause is just that the underlying field name is different across both views. I've never run into that issue using two hosted feature layers, rather than Joined Views. That seems to be the whole point of the Group SQL Expression builder, letting you map values to the filter across different fields.
I suspect it's a limitation of using Joined Views, but haven't seen that documented anywhere and I'm hoping that someone can confirm.
-Aaron
