Experience-wide Views

AnninaRupe1 · ‎06-12-2025

Does anyone know if a view can be made available Experience-wide?

A little more information:
I have an Experience that references several sets of data. These datasets were created in the same formats, mainly so they could be easily understood and didn't require definitions for each attribute in each dataset. One of these attributes is called "Site State." On several pages, I filter the tables and create views for filter widgets based on the region that page is referencing, which focuses on a subset of states. For each page, I have to create a filter on the table and then create a new view for each region. This wouldn't be as big of a deal but the data being referenced are from a view layer, which, if I have to update anything (e.g. domain choices), I have to delete the view layer, update the original layer, recreate the view layer, fix the broken data references in ExB, and then recreate all the filters and views.

It would be nice to be able to filter or create a view once and then reference it throughout the Experience and not have it linked to a specific dataset.

Allen_Zhang · ‎06-12-2025

Hi @AnninaRupe1 .

Is the data source filter what you need?

AnninaRupe1 · ‎06-13-2025

Thanks for the reply, @Allen_Zhang. Unfortunately, no. This filters the entire layer for the entire Experience. I need to have different filters and views on different pages.

When I have to delete the feature layer view from ArcOnline, recreate it, and link it back to the Experience pages, I have to build the filters/views all over again. I would like the filters/views that I built to not be tied directly to a feature layer, or at least be able to copy/paste to another.

Allen_Zhang

Oh, I got you.

The maps and filters were configured with data source A.

Then, you want to replace data source A with a new data source B, while retaining the widgets' configurations.

Is that so?

AnninaRupe1

Yes! Or, if data source C has the same attributes, be able to apply the same configurations.

Allen_Zhang

When I have to delete the feature layer view from ArcOnline, recreate it...

Try overwrite the feature layer but not delete an recreate a new one?

This keeps the same itemId in the data source, and you don't need to re-link it again.

AnninaRupe1

Unfortunately, I can't overwrite. The layer that ExB is referencing is a joined view feature layer. The original base layer was created for and is still attached to a Survey123 form and whenever I have to update the form (adding to domains is the most frequent task), I have to delete the joined view feature layer (even remove it from the recycle bin!) before the form can be republished. If I try to republish the form without deleting anything, it won't--it just spins.

NicoleJohnson

I use ArcGIS Assistant to swap out joined hosted feature layer views in the web map used as a data source in an experience. I almost never use it to edit the experience's JSON--just the web map. You COULD use it to populate data views (changing whatever you need to) for different layers, but being able to swap the data source probably eliminates that need. If you try it, be sure to read the user guide.

AnninaRupe1

Thanks for the suggestion. I will definitely look into this. Do you think that this solution would work on pages that don't have web maps? For this I'm just using a table. It's so users can filter data for reporting purposes.

NicoleJohnson

Yes, you can edit the experience's JSON to change a data source if you don't have that data source coming from a web map (i.e., you brought it in as a stand-alone layer into the experience)*. Otherwise, changing the web map JSON is much easier because there's so much less going on. In Experience Builder, you've got widget configurations, style settings, actions, etc. I've had to do it occasionally, and it's just much more fiddly than changing a web map.

*Just to be clear because I think the terminology could be confusing: it's not relevant whether a page does or doesn't have a map widget. What's relevant is whether the table is in a web map data source or not.