Option to Persist Current Layer Visibility For Each Map

DavidSolari

When a user changes which layers are visible/non-visible in a map, there should be an app-level setting to either save this selection for the next time the map is opened or reset to the map defaults every time (i.e. the current behavior). This data would be saved only to the device, much like the feature to return to last session's extent in Web Appbuilder. This data would ideally persist unless an irreconcilable change is made to the map's layer set but having it reset on every map update isn't a deal breaker.

Our organization has many maps with over a dozen layers by necessity and the default layer visibility isn't ideal for all workloads. This would be infinitely less work than creating and maintaining duplicate maps with different layers visible by default and would save our field crews time as well.

TaylorLockwood

YES! My organization's default layers are really only for one function, but the map is all-purpose and is used extensively outside of the "default function". It's incredibly annoying to have to turn layers on and off each time a map is opened. It also doesn't help when the default extent is NOT the user's location and half the time when you click the location arrow it say's you're outside of the map when you're not.

Maintaining the settings of the last session is a pretty basic concept and it's so common for other apps it's generally expected and it's honestly surprising that it's not. I can't just leave the app constantly running in the background just to maintain my layer selection because it's such a battery drain.