Utility Network Sewer Main Lines: Labeling Issue

Bloper

Hello, 

I have created a custom Label Expression for our wastewater main lines, lateral lines, and manhole assets. The custom labeling is requested from our Sewer Collections crew. This is the labeling standard that we want and are achieving in Pro and in a Map Image service:

But this is what we are getting when putting the Feature Service, with the same labeling expression, into a web map and viewed via Experience Builder:

 

1. We lose the 'Center-straight' placement for the sewer main label.
2. The length label for the sewer laterals are center and not 'place at end of feature'.
3. For the manholes, we lose our white-circle callout for the number label.

I am not sure why the Map Image service retains the custom label expression, while the Feature Service equivalent does not. 

We're on ArcGIS Pro 3.7 and Enterprise 12.0. 

Look forward to your response. Thank you for your time sir.

joyoung_kerrvilletx

The Map Image is being rendered on ArcGIS Server and an image is passed to the client. It supports all the symbology and labeling as the client that published the service. The Feature Service on the other hand has its data passed to the client and is downgraded to what the client supports. If you open the Feature Service in ArcGIS Pro it should look like the Map Image, but if you open the Feature Service in Map Viewer you are limited to what Map Viewer supports for symbology and labeling.

Symbology in Map Viewer has come a long way and most of the time it will match what you would see in ArcGIS Pro. Labeling in Map Viewer is very simplistic compared to ArcGIS Pro, especially the Maplex Labeling engine. You will run into similar limitations viewing the Feature Service in other clients like ArcGIS Field Maps.

Also, I noticed that you are on ArcGIS Pro 3.7 and ArcGIS Enterprise 12.0. The matching version of ArcGIS Pro for ArcGIS Enterprise 12.0 is ArcGIS Pro 3.6. I have run into odd issues when using a version of ArcGIS Pro that is higher than the matching version of ArcGIS Enterprise. If you can, you may want to try to republish the service using ArcGIS Pro 3.6 and see if the issue still happens.