Turn all layers on/off at the same time in ExB

[Thomas1]

In WAB it is possible to turn all layers on/off at the same time using Ctrl + click on the visibility box of any layer. Alt + a does the same in Map Viewer. But neither of those works in ExB. Any other way to do it or it is not possible in ExB?

Ctrl + click the visibility box works in Map Viewer Classic based WAB, Map Viewer Classic and Scene Viewer but neither in Map Viewer, ExB nor Scene Viewer based WAB... 

[TonghuiMing]

@Thomas1 This has been added in the recent AGOL release

https://community.esri.com/t5/arcgis-experience-builder-ideas/enable-disable-all-layers-as-a-whole-a... 

Let us know if you encounter any issues.

[Thomas1]

@TonghuiMing Thanks for the update.

Nice that this is added this is not really helping in maps with groups as it turns on/off all layers, sublayers, groups from the map. This would be much more usefull if this would change layer visibility only at the "first level" (tick boxes in the far left column, see attached image) and that the turn on/off option would be available for each goup.

[Thomas1]

@TonghuiMing Hei, have you seen my comment from februar? Is this going to be fixed?

[TonghuiMing]

Hi @Thomas1, unfortunately, we do not plan to support either of these two UX - only checking the first level, or providing options for each group individually.

[JohnGargiulo]

I 100% agree with Thomas 1.  I just tried the "Enable layer batch options" which turns on/off every single layer in the map. Map Layers widgets are a great way to organize layers into logical groups for the users.  A map with 50+ layers, you may only want to keep 3-5 layers in a single widget.  When a user goes to "Turn on All layers" I am positive they will not want to turn on all layers in the entire map.  This all worked perfectly fine in WebApp Builder for many years.  Please fix so this option make sense with the end-user in mind.

[Thomas1]

Hi @TonghuiMing. Thanks for your answer, but why not? Is Esri not aiming to make Experience Builder more user-friendly?

[TonghuiMing]

We are definitely aiming to provide better user experiences, but in the scenarios mentioned above, the cases are a bit different.

For example, providing options for each group individually - this option is designed to fulfill cases where many users want to quickly check or uncheck all the layers once, instead of checking them one by one. If they have ~100 layers, options for each group do not introduce the desired better UX; yet, they are the same - users would need to click ~100 times to enable each group. Checking only the first level is not a supported behavior across Esri products, which means this is a tailored new UX that could disrupt other users' regular workflow.

I understand that it could be a bit frustrating that we could not provide this feature any time soon, but we need to make sure any options we add to the OOTB widget do not break other users' cases.

It would be possible if you try the developer edition, which could give more opportunities to customize the behavior of the widget. Here is one of the custom widgets developed by the community users, which might cover your second scenario - https://community.esri.com/t5/experience-builder-custom-widgets/map-layers-widget-custom-1-17/m-p/16... 

Thanks,

[Thomas1]

Thanks for your reply @TonghuiMing 

I don't really understand your example. Checking layers one by one is exactly what we want to avoid.

"Checking only the first level": the goal is not that only the first level is checked, but if you have many layers checked in a group and you want to show only 1 or 2 is it better UX to uncheck all layers in the group and then check the one(s) we need. Or if you have many layers/group layers and you want to show only one group, you want to turn off all the layers/groups without to loose which sublayer are checked inside that Group you want to show.

What is needed here is nothing but a behavior supported across Esri Products for over 20 years (using Ctrl + click). 

The link you sent have nothing to do with the issue in this thread.