Using One Web Map for Multiple Pages in an Experience to Show Different Layers Per Page

[nbarenblitt]

I am building an Experience in Experience Builder. I have one web map that I would like to use on multiple pages in the Experience, but I want each page to display different layers from the web map. Currently, when I select the layers that I want to display on one page, it turns on only those layers for the other pages. Is it possible to set the Experience so that each page can display different layers from one web map?

The solution that I have found so far that has worked is to make copies of the web map and input the copies of the web map into the map widget for each page and then set which layers I want displayed. 

Thank you.

[Leonidas]

From my understanding, there is no way out of the box to turn layers on and off when your application first loads.  In the data panel for your experience, you can turn layers off there but then they are not available in your application.  This is a bit of an issue for me because we use one Webmap as the basis of multiple applications but don't always want the default layers to show up when it loads but want to have the option of turning them on.

I am building a 'hidden' widget that will adjust layer visibility when the application first loads.  It is not ideal as the Webmap will still start to load with the initial layer visibility settings in the Webmap and then the layers in the widget settings be applied and rendered.  If your services are slow, you will see the map adjust the layer visibility.