nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JS API 4.7 WebMap : layers visibility defined in AGOL not respected ?

NicolasGIS

Playing with the following sample, loading a webMap from a PortalItem id:

Load a basic WebMap | ArcGIS API for JavaScript 4.7

I noticed that a WebMap containing a MapService with custom layers visibility defined in AGOL (overwriting thus the default ones from the service) are not respected using arcgis js api 4.7. Layers visibility configuration is the one of the service and not the one of webmap.

I know WebMap is partially supported:

WebMap | API Reference | ArcGIS API for JavaScript 4.7

but even with a map service that has dynamic layers enabled, it is still not respected.

Is it a temporary limitation ? Maybe linked to AGOL ?

Cheers

Nicolas

Trouver plus de publications taguées avec

Accepted answers

All comments

NicolasGIS

Finally ! This is great news

Thanks for the follow up. Will test that on next.

Noah Sager

Update: we should have this fixed for the next release (4.15), and this will be available to test on js-next sometime next week.

feedback-js-api-next/CHANGELOG.md at master · Esri/feedback-js-api-next · GitHub

NicolasGIS

Hello Bjorn Svensson,

It seems like the issue remains in 4.9.

Any hope for 4.10 ? Is there NIM for following the status ? It is a big a limitation for us as it prevents us from fully exploiting AGOL webmap philosophy.

Thanks,

Nicolas

NicolasGIS

Hello Bjorn Svensson‌,

Thanks for the reply. Glad it has been logged.

Nicolas

BjornSvensson

Yes, I was able to replicate with the webmap you shared.

This is a bug with the 4.x API. Thank you for reporting.

deleted-user-RAnWn8DDSd1P

I just noticed exact same thing. visibility property on a service seems to be respected but not visibleLayers array, which is what ended up in the webmap JSON for me when I checked a few on and saved the webmap

https://pdx.maps.arcgis.com/home/webmap/viewer.html?webmap=5082731585b14a00b4e69a5c4ad1ffcd

https://www.arcgis.com/sharing/rest/content/items/5082731585b14a00b4e69a5c4ad1ffcd/data?f=json

https://jsbin.com/fukikit/edit?html,output

rishishady

Hey Bjorn,

I also having the same issue. So, I am directly dealing with the Feature layers or WFS using ArcGIS API for JS rather than struggling with Web Map. FYI shared webmap is also having the same limitation.