Herencia de la configuración de las ventanas emergentes

Question

Me pregunto si alguien entiende mejor cómo se heredan en AGO las configuraciones de las ventanas emergentes.

Tengo una capa de AGO (Capa 1) y dos vistas (Vista 1 y Vista 2) creadas a partir de la Capa 1. La Vista 1 se creó antes de que configurara las ventanas emergentes de la Capa 1, y la Vista 2, después. Según la ayuda de AGO, ambas vistas deberían heredar las configuraciones de las ventanas emergentes, pero solo lo hizo la Vista 2. Si vuelvo a configurar las ventanas emergentes en la Capa 1, ninguna de las dos vistas reflejará los cambios.

Esto no tiene sentido. ¿Tengo que volver a crear las vistas de una capa si hago algún cambio en las ventanas emergentes para que las ventanas de información sean coherentes?

GLCAdmin · Answer

Thank you for your explanation, Katie!

Right now we are migration our old web mapping application to AGO apps, and one of them has several maps using various symbologies but all based on attributes from the same data layer. So I am creating views to mimic the scenario. These views will share the same popup configuration, so I am configuring the layer popup so that I do not have to customize each view. But as a prototype, the information in the popup may change anytime. It is just becoming a hassle to repeat the configurations for all views after the layer changes and I am hoping I can cascade the settings. It is just something not technically incapable but inconvenient. Maybe to include a checkbox to allow the user to choose whether cascade the layer's setting to its views in the future release?

Anonymous User · Answer

I believe this is expected behavior. The documentation states that the pop-up configuration (on the visualization tab) is inherited from the hosted feature layer from which they are created. To me this makes sense that whatever the configuration on the visualization tab at the time of creation is what would be inherited.

I don't think this implies that the relationship would be maintained in such a way that if the pop-up configuration changes on the hosted feature layer (in this case case layer 1) that those changes would be proliferated to the views.

The intent of the views is to be able to maintain reference to the same underlying data in order to get the most up to date version of that data while also allowing the symbology and pop-up configuration, editing privileges (among other things) to be changed independently.

I would like to hear more about your workflow and project to better understand the use case for pop-up configurations remaining in sync. Could you share the following:

What are you using the views for?

What is the project you are using views in?

What is it about the workflow that requires the pop-up configuration to change frequently?

GLCAdmin · Answer

In the Visualization tab. Actually, I started from the Web Map viewer, but the latest editing was done in the Visualization tab.