topic Published UN webmap showing coded domain value instead of description in ArcGIS Utility Network Questions

Published UN webmap showing coded domain value instead of description

angiexx1 — Fri, 05 Jun 2026 04:56:32 GMT

I have published my UN in the enterprise portal as a Webmap , also i have given the asset group as unique values to have the symbology but after publishing all i can see is coded domain instead of the description , how to resolve this? also when i have published without symbology the description worked correctly, but if i do with the symbology its not working correctly.

Re: Published UN webmap showing coded domain value instead of description

MikeMillerGIS — Fri, 05 Jun 2026 12:01:28 GMT

Publish the service rendered by the Asset Group. This sets the type field in the service to the subtype. In some clients, this is required to show coded value domain descriptions. Then bring that service into ArcGIS Pro and symbolize like you want. Share that back to your Portal as a webmap.

Re: Published UN webmap showing coded domain value instead of description

angiexx1 — Fri, 05 Jun 2026 13:04:30 GMT

I have published the service using Asset Group for the symbology yet when i try to create its only showing numbers

Re: Published UN webmap showing coded domain value instead of description

RobertKrisher — Fri, 05 Jun 2026 13:14:29 GMT

@angiexx1 in the screenshot above the symbology is using three fields (Asset group, status, operating status). Can you post a screenshot of the symbology on that layer in the map used to publish the service?

Re: Published UN webmap showing coded domain value instead of description

MikeMillerGIS — Fri, 05 Jun 2026 13:27:07 GMT

There is also a setting in the map service that you might need to increase. "maximum number of domain codes"

Re: Published UN webmap showing coded domain value instead of description

gis_KIWI4 — Sat, 06 Jun 2026 12:45:43 GMT

@angiexx1 - Assuming you have published the map as Mike suggested in the first suggestion, you can try Increasing the Coded Domains value on the service page and that has fixed this issue for us in the past.