Experience Builder Help

[NateGIS7]

Hello All,

I'm currently working on a dashboard using Experience Builder and have run into a few issues. The dashboard is supposed to be a park locator for the city of El Dorado Hills for a school project. The issues are:

1. Multiple finder widgets/conflicting filters

I have multiple widgets (amenity finder, trail finder, etc.) filtering the same map and data sources. When used sequentially, their filters stack and cause inconsistent behavior in the Park Locator (a list) and details pane. The goal is that using one filter would automatically clear the other, so they don't stack up. Is there a supported way (maybe through actions) to have the widget clear or override another filter, or is user guidance (e.g., "clear selection before switching tools") the intended approach? I have tried to add a button widget as a clear all, but had no luck.

2. Details widget + related features
My Details widget is configured for my park list and park boundaries. Selecting an amenity or trail correctly narrows parks for the list, but the Details widget only updates when a park polygon itself is selected.
Is there a supported way to propagate a selection from a related point or line feature to its parent polygon, or is this a current platform limitation?

3. Legend behavior with filters
Can the Legend widget dynamically update based on filtered records (for example, only showing amenity types present within a selected park), or does it only respond to layer visibility?
I want to confirm whether this is supported or if there is another way to create a custom widget only showing what is being filtered on the map. 

I mainly want to confirm I’m not working around behavior that already has an intended solution or best-practice pattern.

[VenkataKondepati]

Good questions — you’re running into a few known Experience Builder patterns/limitations, not doing anything wrong.

1) Multiple finder widgets / stacked filters
Filters do stack by design. There’s no built-in “override other widget filters” behavior today. The supported pattern is:

• Use a single filter widget with multiple sections (amenity, trails, etc.), or

• Add a Clear Selection / Clear Filters button wired to the same data source (this does work, but it must target the correct data source and both selection + filter states).
  User guidance is common, but consolidating filters into one widget is the cleanest UX.

2) Details widget + related features
This is currently a platform limitation. Experience Builder does not automatically propagate a selection from a related feature (point/line) to its parent polygon.
Workarounds:

• Drive the Details widget from the Park polygon layer only, and

• Use relationships/joins to filter parks when amenities are selected (filter → park), not selection → details.

3) Legend behavior with filters
Legend responds to layer visibility and symbology, not record-level filters. It won’t dynamically shrink to “only what’s in the filtered set.”
If you need that behavior, you’d need:

• A custom widget, or

• Separate layers/views per amenity type with visibility controlled by filters.

Bottom line:
You’re not missing anything — these are known EB behaviors. Best practice is fewer filter widgets, park-driven details, and accepting legend limitations unless you go custom.