1. Is the layer a vector tile layer hosted in ArcGIS Online?
2. Are you adding this to a previously created map that already contains other layers? If so:
a. What other types of layers are in this map?
b. How many of each type are in the the map?
3. Do you get this message if you add the layer to a new map?
The short answer
You've reached the limit of the number of layers you can add to your map for layers that utilize WebGL.
The longer answer
The long term solution
Hi Mike - so is there a work around on this? For us this happens alot when we use the human geography basemap, and a recently created local base map that uses the Light gray base, a local base vector tile, a local detail vector tile as a reference, and a copy of the light gray reference vector tile as a reference.
How do I stop or otherwise disallow my hosted feature layers in the agol or portal map viewer to not utilize webgl? Is that possible?
How many layers do you have in your map? Are you approaching 16 layers? Could you make separate maps with less layers?
Hi Mike - some of our sections have to have data explorer and lookup maps with lots of layers. Think utilities. Most of staff uses the online web app builder and other online templates so that's not really an option for them. The WebGL usually behaves in the developer edition of the web app builder (in that you can see all your layers and not lose them during a basemap switch in the app) and in any online webmaps that use a raster base.
A workaround may be that staff has to save a map with a raster base in order to have 16+ visible (but scale-dependent) layers, or that more layers have to be set not visible. Either seems to work for the most part. Awaiting the 4x map viewer.
Is this ever going to be changed? We just migrated all our web apps off a web server and have discovered this limitation on a hosted and federated portal platform 10.8.1 using the embedded WAB in portal.
Kind of makes life miserable if you published feature services across your viewers or you are trying to consume another service off your platform like FEMA or USGS who have published their services as feature layers. We went in and changed them all to map services. It is driving our users to perform analysis using the actual portal and not in a WAB, but some users dont like having to hop between 2 processes when they could do everything in a PRO session or ARCGIS desktop.
We also are using the most current version of WAB as imbedded in the portal. This seems like a education problem as well for most of the community of publishers that ESRI is not effectively socializing