Configuring app such that changes to map layers affects both map and charts

[JohnForne]

Happy new year!

I'd like to create an app with maps and graphs using Arc Experience Builder and I've come up against what seems to be a limitation...

I'm looking to publish an app with map and related chart that allows users to explore many different variables/fields within a feature layer (relating to nitrogen in water). I've got 10+ different variables, including for example modelled nitrate-nitrite nitrogen, modelled ammonical nitrogen, etc.

I've figured out how to create an action so that the chart changes to reflect changes in the extent of the map (see below). 

What I need to do is configure the app so that the chart changes when the user changes the map layer and/or zooms in/out and changes the map extent.

However, the chart doesn't change even though I changed the map to Modelled ammonical nitrogen.

An issue seems to be that chart app seems to be able to interact with a single and specified layer in the map widget only. It is not clear whether it is possible to make my Experience Builder chart category field reactive to map selections.

https://support.esri.com/en-us/knowledge-base/synchronize-charts-based-on-the-selection-in-a-chart-u...

Selecting 'Framework' will filter this layer across the application, including the second chart and the map.

However, when I select a trigger and click Record selection changes - I don't appear to have the option of choosing "Framework" as the Target.

Does anyone know how to resolve this?

Thanks

[JoseBarrios1]

Some of this functionality is possible in ArcGIS Experience Builder, but not exactly as you might expect out-of-the-box. You are correct that a chart interacts with a single, specified layer in the Map widget—this is by design. Changing the visible map layer does not automatically update the chart’s data source. A chart widget is bound to a single data source (layer). 

Possible workarounds to explore:

1. Stacking multiple charts or using Layer Views + a selection control—create one chart per layer and use Sections or Views to control which chart is visible.

2. Combining your data into a single feature layer—add a field (e.g., layer_Type) to distinguish each dataset, create multiple views for each dataset, and bind the chart to those views.

Note: These approaches can become messy if there are many layers and may increase the app size.

[Wei_Ying]

@JohnForne Currently yes a single chart widget only work with single layer. So if you change a different layer in the map, it won't act. You may try the workaround that Jose suggested above.

But is using the same layer, the map extent change should trigger data action on the chart. You may share more details if that does seem to work for you. 

[JohnForne]

Thanks Jose and Wei - much appreciated.
Good to clarify that this is a limitation and there are work arounds.