We’ve configured an Experience Builder app that’s linked to a Web Map, which references a feature layer. The feature layer includes a field with a coded value domain. In Experience Builder, we’ve set up a data view that filters records based on this field.
Recently, we updated the domain values in the underlying feature layer (e.g., changed or added coded values for the field). However, these changes aren’t being reflected in Experience Builder. When we try to edit the data view to apply the updated filters, the filter options still show the old domain values.
We spoke to ESRI about this, and their reply was to "create new web maps" - while this does work, it's a substantial amount of work given that 1) the original web map has a lot of configurations, filters, edit features etc that will need to be replicated. 2) We would need to then reconfigure the Experience Builder application (which also contains quite a substantial set of widgets/features that would need to be changed), 3) there are a host of other applications that rely on the original web map which would have to be reconfigured as well.
This to me seems like a bug on the web maps / experience builder that should be addressed. As a user I would expect any changes made to underlying feature layers, and web maps to be reflected in all other applications that rely on them - and not have to re-build everything anytime a minor change to one of them is made.
