I am thinking about how to approach this issue and would greatly love any input you all might have.
Currently we have 100+ maps in our Portal that use the same layer that is just filtered by the design, the site, and it's label.
To consolidate these maps into 1 useful application I thought about creating an experience where the user could filter that layer on their own and it would show up in the experience application.
However, when testing this, users felt they would like to have the most important layers already be filtered on the map. How would I get around having a map with 100+ filters of the same layer.
Do you all think it is possible to have a custom experience builder widget to add a filtered layer to the map and then another custom widget to save the map. That way when "Bob" at Site X wants his filtered layer he can use those custom widgets to add / save the map so that way the next time "Bob" loads the experience application he sees what is important to him at his sight.
So to summarize, do you think this is possible? / How would you all accomplish this goal?