Select to view content in your preferred language

UtilityNetwork Asset Group - Asset Types showing IDs when publishing a Web Map (data source Feature Layer)

564
4
09-04-2025 05:48 AM
Labels (1)
CJara
by
Emerging Contributor

Dear all,

There is an issue I am not able to overcome and I am not really sure how to solve it. I have shared a Utility Network web Feature Layer from ArcGIS Pro into a portal and all the layers: Water Device, Water Junction, Water Line, etc. have their correspondent textual names when either opening the attribute table or clicking in a pop-up in Map Viewer: Tanks, Junctions, Lines, or whatever name they might have. (Please see the first screenshot below for the "InstalacionesFijas" layer within Water Device - be aware the names are in Spanish-)

CJara_2-1756988391755.png


However, when sharing a Web Map from ArcGIS Pro, into the same portal, using these Feature Layers as the data source, having symbology, grouped layers, etc. the textual names are overwritten by the coded domains IDs, and instead of InstalacionesFijas, ID number 12 and 14 are displayed (Please see the second screenshot below for a Water Device layer):

FYI: When firstly sharing the Feature Layer, I have increased the "Max number of coded domains" to 1000000 just in case, but this hasn´t seem to made any difference whatsoever. 

CJara_4-1756989341372.png

 

Going furhter and publishing a Web Map only using the raw Feature Layer dragged into an ArcGIS Pro map  (with no symbology, or grouped layers, no filters, etc.) the attribute table in Map Viewer shows the textual Asset Group name (InstalacionesFijas) and the coded domain ID (14):

CJara_3-1756988893873.png

 

Please be aware this occurs through many other layers, there are no definition queries set and the above one is just an example. Additionally some of the maps had Subtype Group Layers added and we originally thought the root of the issue was that, but we have ruled it out.

I am stuck with this and any help would be much appreciated.

Thanks,

Carlos

0 Kudos
4 Replies
RobertKrisher
Esri Regular Contributor

How are the feature services published? Do they match the recommendations included in this article: Deploying a utility network to ArcGIS Enterprise. This note is particularly important, and is usually the cause of the problem you are seeing:

RobertKrisher_0-1756992944923.png

 

0 Kudos
CJara
by
Emerging Contributor

Hi Robert,

Thank you very much for your answer. We always say Yes to the "Do you want to add all classes that participate in the Utility Network to the map" question and when publishing the service, the asset group/asset types names are being displayed correctly.

Exactly, as we use the symbology in ArcGIS Pro based on other fields (subnetworkname, isconnected, issubnetworkcontroller, etc.) when publishing the web map  the Asset Group - Asset Type names are "lost" and only the IDs are showing. So, how can we see the Asset Group - Asset Type names instead of the coded values IDs if we use a symbology based on other fields? 

Thanks,

Carlos

0 Kudos
RobertKrisher
Esri Regular Contributor

If you publish the feature service 'simply' (as you said, accept all classes and publish as-is), then the features should appear correctly in the feature service. When creating your web map, you add the feature service to ArcGIS Pro and apply your symbology, field properties, etc, then share the Web Map. If it's still not appearing correctly, log a case with support. I have noticed that sometimes when this happens, the issue can correct itself if you open the published web map in the Map Viewer then save it using ArcGIS Enterprise.

0 Kudos
CJara
by
Emerging Contributor

Thank you Robert,

We have done as you said, saving the web map in ArcGIS Enterprise, and the Asset Group shows the coded ID domain (3, 4, 7, 17, etc.) and the Asset Type shows the textual name (Tanks, valves, or whatever) in one of the web maps.
However, following the same solution, it shows both Asset Group - Asset Types textual names in a different web map we have published earlier on, hence this behaves randomly. We will log a case with support.

Cheers,

Carlos

 

0 Kudos