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; } } }

Turning on Labels breaks Symbology

MarcRabideau

I am having an issue where I am using a hosted feature layer to create a Web Map, which in turn is being used in a Web Mapping Application on ArcGIS Online. I have a model that runs nightly to update my data which is working fine. However, the problem is that when I label the features(points) in my web map, the symbology disappears from my application. My current fix for this is to rebuild the spatial index of the hosted feature layer, which makes the symbology show up again. Is there something I can do to prevent this from happening? Has anyone experienced something like this before?

Najděte více příspěvků označených jako

Accepted answers

RussRoberts

It looks like when you are updating the service the layers extent is getting set to null

 "useStandardizedQueries" : true, 
  "geometryType" : "esriGeometryPoint", 
  "minScale" : 0, 
  "maxScale" : 0, 
  "extent" : null,

the layer throws an error when querying in 3.x

Rebuilding the index is probably fixing that null layer extent which the 3.x JSAPI (Map Viewer Classic, Web AppBuilder) is needing to draw the features.

Another thing I noticed

The labels also use a scale range which is not supported in WAB apps and other 3.x JSAPI apps like Map Viewer Classic and would recommend migrating to Experience Builder or Instant apps so you can take advantage of this plus additional web map enhancements we have made and WAB is on retirement roadmap.

All comments

RussRoberts

Can you share the web map and layer when it is this state and I can take a look.

MarcRabideau

Layer - WaterServices_Prod - Overview (arcgis.com)

Map - Get The Lead Out Prod - Overview (arcgis.com)

App - Get The Lead Out App - Overview (arcgis.com)

Its currently fixed but will run again at 1am tomorrow morning and be broken again.

MarcRabideau

Thank you, It is currently in the "Broken" state

RussRoberts

thanks taking a look

RussRoberts

It looks like when you are updating the service the layers extent is getting set to null

 "useStandardizedQueries" : true, 
  "geometryType" : "esriGeometryPoint", 
  "minScale" : 0, 
  "maxScale" : 0, 
  "extent" : null,

the layer throws an error when querying in 3.x

Rebuilding the index is probably fixing that null layer extent which the 3.x JSAPI (Map Viewer Classic, Web AppBuilder) is needing to draw the features.

Another thing I noticed

MarcRabideau

Thank you for the quick reply, opening it in experience builder did seem to fix the issue.

Do you have any recommendation for getting it to work in WAB?

This is a public facing map that has taken a while to get exactly how my team wants it, and trying to replicate it exactly is going to be a pain.

Připojte se ke konverzaci

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.