Experience Builder Chart Filter Action not working

[LindsayRaabe_FPCWA]

I am building a dashboard style display in Experience Builder that shows features in a map, and provides basic charting and filter functions. The layer of interest in the map is also referenced in a pie chart on the side of the dashboard. When you click one of the feature categories in the chart, a Filter Action is supposed to reduce the features displayed in the map to only show those matching the selected category. However, whenever I select it, it seems to pick a different, random category. I've recreated the chart and the action multiple times but can't get it to behave as it should. It doesn't seem like a complex setup, so what is going wrong?

[TonghuiMing]

Hi @LindsayRaabe_FPCWA - I can reproduce your problem on AGOL and we are not sure what has caused this. We will take a further look at it. Thanks for bringing this up.

[TonghuiMing]

This issue should have been resolved with the recent AGOL June release.

[JennetteDuncan]

Hi @TonghuiMing - I am experiencing the same issue still. It seems to temporarily resolve in the live view or draft mode when I change the DATA > SORT BY from/to "value" or "category " (either way). But as soon in preview or once published, the issue persists.

[TonghuiMing]

Hi @JennetteDuncan 

The cause of this issue should not be affected by value vs. category. I gave it a test and it seems like it works fine in my app:

Is it possible to share the app with us? Otherwise you could reach out to tech support and they will help create a reproducible environment. Thanks.

[JennetteDuncan]

@TonghuiMing Yes! Link here. Could it be the data type? Both the original post and my issue are using polygons. Looks like your example is with a point feature class. Just a thought.

[TonghuiMing]

@JennetteDuncan Thanks for sharing the app. I can reproduce it, and we will take a look.

[TonghuiMing]

FYI - per preliminary investigation, this is a different issue.

This case has something to do with grouping either categories or values to use in the chart component - which causes the index mismatch between the selected chart section vs. the actual selected features. If there is no grouping configured (as in my previous case), this issue wouldn't occur.

We will follow up on this.

[TonghuiMing]

@JennetteDuncan - the mismatch you encountered before related to grouping should be resolved in the latest 2023 AGOL Oct release. Let us know if you encounter any other issues. Thanks!