AssetGroup and AssetType value in Map Viewer

[gpgisandsky]

Hi,

I tried to publish a web map using two methods, starting from a utility network feature service:

1. Using a group layer
2. Using a traditional layer

When I use the map viewer in Portal (11.3) and enable the identity (to display the pop-up) feature, the behavior differs between the two methods:

• In the first case (group layer), the AssetGroup field appears as a code value instead of the name, while the AssetType field appears as the description value.
• In the second case (traditional layer), the result is inverted: the AssetGroup field appears as the name, while the AssetType field appears as a code value.

[BenWalker1 · Accepted solution]

This is a well known bug, which seems to be better in the November release of AGOL, so hopefully will be better in Enterprise 11.4.

To get around it you need to publish you service with each UN layer symbolized on the Asset Group field. Don't bother doing any symbology on the feature layer. Once the service is published you can then add it to a web map and change the symbology. You will need to add each UN layer multiple times if you want to replicate what a sub-type group layers does e.g. if you want to turn valves off, but leave hydrants on.

Web AppBuilder does not support Sub-type group layers and ExB only supports them on the map at 11.3, but support in widgets is better in the new AGOL version and the improvements should be in the next developer edition.

Hopefully that makes sense.

[RobertKrisher]

You can find an article explaining the best practices for publishing services/maps here: https://community.esri.com/t5/arcgis-utility-network-blog/best-practices-for-working-with-utility-ne...

[AmberY]

Hello @BenWalker1 & @RobertKrisher  , would really appreciate ur thoughts on this! I have been struggling with this for a while.

I follow the same step > publish by Asset Group > Add UN layer in Map Viewer > Symbolise by asset type. But the issue that I am facing is that when i tried to create new features, seem that it still refer by asset group? Any idea on this?

Symbolise by asset type in map viewer after publish by asset group from ArcGIS Pro:

When i want to create features, it still point to asset group

Is this something I should expect? Coz i thought i would be able to create features based on asset type directly instead of asset group as my symbology is now pointing to asset type. Am I following the correct flow of symbolising the asset? 

[RobertKrisher]

Once you have the feature service published, you can bring it into ArcGIS Pro using a subtype group layer (or individual layers if you want to) and apply symbology however you'd like.

In terms of creating/managing editing templates, those are driven by your symbology by default. I typically use ArcGIS Pro to author templates, and regardless of what your symbology is you'll want to ensure that each template sets both the asset group and asset type of the feature so snapping and validation works properly.

[AmberY]

Thanks @RobertKrisher . For desktop level, we have no issue at all just that we are unsure when the service is publish to Portal, what is the correct workflow to symbolise it by asset type and status to view the UN layer in map viewer/application level.

We tried to symbolise it at map viewer directly by changing the symbology field from asset group to asset type, it works. But it has limitation that we can only symbolise by one field for feature service, which we actually looking for symbolising using both field (asset type and status).

Limitation of symbolise in map viewer

This is what we have done for SGL (picture below） in desktop level and we want to bring it to web application level., especially on tracing apps, so user can differentiate the type of valve. We tested to publish the following in SGL, just that the asset participate in SGL cannot be selected when i try to make a selection on map and like u said, will have issue on domain code.

Apologies for nagging about this, but we would really appreciate ur kind advise on this!

[RobertKrisher]

When you publish the service do not symbolize using anything but the asset group. If you do that there are a known series of bugs that will cause things to not work. You must symbolize your feature service using the asset group and then do all additional symbology/configuration through your web map. You should author your web map using ArcGIS Pro and then share it as a web map to your portal. This is the best practice outlined in the article above: https://community.esri.com/t5/arcgis-utility-network-blog/best-practices-for-working-with-utility-ne...

Some widgets (like the trace widget and experience builder) currently do not support subtype group layers, but you can work around that pretty easily.

For web maps that can't use subtype group layers, you author a map in ArcGIS Pro that symbolizes features using multiple fields, using a regular feature layer, and publish that as a web map to be used with your web applications. Below is an example of the legend from a Map I published this way to support an experience builder app. I symbolized using asset group and asset type, but I just have easily included device status as well.

Remember that there are some apps that do support subtype group layer. For example, the Web Editor application (released at 11.3) does support subtype group layers. In the example below I have the same data with subtype group layer, but I'm symbolizing each valve based on its asset type, present position, and normal position (to identify any valves in an abnormal status).

[AmberY]

Hello @RobertKrisher  , thanks  for detailing out the steps. I published in Asset Group and symbolise using Asset Type in ArcGIS Pro, then share as web map. It seems okay, but when I look at its attribute table, the Asset Group change to code, but in ExB, it shows description. Any idea on what steps I might be missing? 

Map Viewer:

ExB:

 "You must symbolize your feature service using the asset group and then do all additional symbology/configuration through your web map" >> Does this means that I can do all sort of definition queries and group them together like pic below and share as web map to be used in tracing web app (I have tested, so far it works, just wonder if it might have some unforseen implication).

[RobertKrisher]

For any strange behavior you are seeing, log a case with support. They can look at the specific behavior you are seeing and get you attached to the corresponding bug or provide you with guidance on how to configure the system appropriately.

Every layer is a separate request to the feature service, so 10 layers will be slower than a single layer. Instead of creating separate layers for each of your asset groups, consider making a smaller number of layers for features with similar attribution or symbology (valves, customer equipment, etc).

Others have mentioned using Arcade to work around some of these issues as well. There is also a performance cost associated with Arcade, but if it's just being applied to a single feature in a pop-up its nothing to worry about. If you evaluate arcade expressions for 20 fields on several thousand rows, you'll notice it.

[HazelRiordan]

Yes, this bug has driven many users batty for a while now.  I am curious to know if anyone has tested this in 11.4...