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

Web App Builder Hosted Feature Not Displaying Correctly

WardMitchell1

Hello All,

I am updating a hosted feature layer due to potential corruption to the current Hosted feature layer. I downloaded the current feature layer to be corrected in Pro then hosted the new layer to AGOL. I added the new layer to the Web Map, saved the map and then I check to see if it automatically loaded it to the Web App Builder map. It did load it; however, it is not honoring the unique values symbology that was set in the web map (see attached video). I have created this layer multiple times from scratch, and each time it does not honor the unique values setting in the web map. Is this the result of the latest update to Map Viewer? I am using map viewer with the web app builder, this was working prior to the update, as you can in the video there are2 layers for the Maintenance Zones one ending with "Zone", the updated version, and the other ending with "Zones" the original version.

Hosted Feature layer not honoring unqiue values in web app builder.mp4

Andrew--Johnson_1-1619038123068.png

Find more posts tagged with

Content Management

Data and services

Mapping

Accepted answers

All comments

kenbuja

The Web AppBuilder uses ArcGIS JavaScript Maps SDK 3.x version and was built to use maps created in Map Viewer Classic. It can use maps that were built in the new Map Viewer, but it cannot render anything that uses the ArcGIS JavaScript Maps SDK 4.x capabilities. This is why your map is not turning out as your expected. You would have to use Experience Builder, which is based on the 4.x technology, to properly render your map.

If you can't use Experience Builder, the safest thing to do is symbolize it in Map Viewer Classic.

WardMitchell1

Thanks for the response. So I symbolized the updated layer in Classic, through the visualization tab, saved it, and had the same negative results. I get what you are saying with the SDK3 vs SDK 4; however I'm curious as to why it worked before when I did everything originally in Map Viewer, not classic? Also were you suggesting the whole map needs to be in Classic view?

kenbuja

If you open your original map in Classic, does it show up properly?

WardMitchell1

Yep

WardMitchell1

Correction not all layers are showing in classic. At this point, I'm leaving things as they are and will eventually rebuild it in Experience Builder and hopefully it will consistently work with the web amp. Thanks for the suggestions, though.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

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