ArcGIS Web App not honouring Web Map Symbology!

10448
25
Jump to solution
03-04-2023 06:51 PM
Marie-AngeFournier-Beck
Regular Contributor

I have 7 web apps and 7 different web maps (one for each app). All of a sudden, yesterday, one of the web maps started to not honour the symbology that was set in the web map. It was only with the polygon layers. The web app has started filling in 3 of the polygons feature services when all of the settings, including in the visualization settings of each feature service, has the polygons shown only with a black outline - no fill. I have deleted the map, recreated an entirely new map. Deleted the app and recreated an entirely new app. I have changed the basemap. I have removed the feature layers from the map then added them again... I still get the same error from the web application - where 3 polygon layers are shown filled in and not as just outlines.


EDIT: Now it is doing this for all polygons within my map and for all maps, but only in the web app builder, not in the map itself.  I hope someone has some advice out there!!?

0 Kudos
25 Replies
RussRoberts
Esri Notable Contributor

Are you publishing to Online or Enterprise? I see the icon for pooling in your screenshot which makes me think you are looking at a map image layer.  The compatible symbol option is for feature layers. 

0 Kudos
Tiff
by
Frequent Contributor

@RussRoberts good catch! I am publishing to Enterprise in this case. Overwriting provides the map image as the only option as it was published as a map image and its respective feature service. Is there a workaround in this case?

(Temporary solution - I republished with a MVC compatible symbol, however it did not update in the associated item in AGOL so I changed that symbol manually).

0 Kudos
RussRoberts
Esri Notable Contributor

Map Image Layers will not have the same advanced symbology case where its coming in. You would have to click on the feature layer options to change those properties for the feature layer case. In that case Pro would be publishing to the service case and not overwriting what is at the item level for a layer for symbology. This I believe is coming at 3.2 .

0 Kudos
JaneMiller1
New Contributor

I was having the same issuing publishing from Web Viewer Classic so switched to Map Viewer (despite hating it), but as of today, my Web Apps are not honoring symbology I created in Map Viewer (not Classic). Let me know if anyone else is having this issue going forward.

RussRoberts
Esri Notable Contributor

Would like to hear what issues you have with Map Viewer?  No recent changes have gone out this week. Can you share the map and give additional details on what the expected vs. actual results are?

 

Thanks!

0 Kudos
jbelak_audubon
Occasional Contributor

"Use symbol types compatible with all clients" should be the default, not the exception. How many hours have been wasted, cumulatively, by this faulty default setting and the need to remember to "check the box" each time a layer is shared? I don't think there are many users that want their symbol types to be incompatible with some clients, so why is this the default?

0 Kudos