Enable Group Layers in Map Viewer to stay synced with original item for automatic updates

[KeesHoogenboom]

Creating and sharing Group Layers enables efficient distribution of bundled data packages. However, these packages evolve over time. I would like the ability to update a Group Layer from its original item, ensuring that all associated Web Maps are automatically updated. This would keep everything in sync seamlessly.

For instance, a Group Layer containing geographical reference layers could prove useful in GIS viewers, but these layers may require periodic updates.

[SSWoodward]

Thanks for the idea @KeesHoogenboom,

When you mention that the layers might required additional updates,  what type of updates do you have in mind?  Are you thinking about schema/service level changes, like adding or removing layers from the feature service, or adding new fields? Or updates to the data contained within the existing published layers?

[KeesHoogenboom]

@SSWoodward thank you for your question. I am talking about adding or removing layers to the grouplayer. Data updates within the existing layers should already go through. 

[SachaSmart]

@SSWoodward 

Just wanted to add to this, I work with group layers which have other nested group layers containing the feature layers. It appears that even though maps or group layers are linked, they exist as specific copies at the time they are added/saved, rather than update dynamically with the content in the linked item. 

It would be nice if there was a sync/update option for group layers to update their content based on the linked item, or perhaps a refresh interval similiar to how the data layers work.

Eg. I have a Parent group layer (or map) A, which includes a group layer B, which contains feature layers.
Updating the feature layers in B should ideally also update that B group layer within parent A.

Currently the workflow is one must open map viewer, remove and then re-add the same group layer to update any content added since the last time the parent group layer or map was saved via MapViewer. This is pretty cumbersome to do when dealing with group layers with large amounts of data.