Select to view content in your preferred language

Gas Utility Network Publishes as Feature Layer not Utility Network

467
4
Jump to solution
04-05-2026 05:13 AM
JMathai
Emerging Contributor

I have been wrangling with an upgrade from version 4 utility network to version 7 for electric and gas.  Leaving electric aside for now, I have successfully applied my asset package from version 4 to my new 11.3 enterprise gdb.  I publish and it says successful.  I can view my feature layer, but it is just that, as feature layer.  It doesn't appear to be recognizing it as a utility network.  When I go to my content on arcgis online and look at the url for the layer, the extension is featureServer (https://arcgisqa.gru.com/arcgis/rest/services/Gas_Utility_Network_Dev/FeatureServer)

 

This in addition to there doesn't seem to have most of the items available in the Utility Network Ribbon in arcpro when I add it to the map.

 

I have encountered so many problems with this and just have no idea how to proceed.

My steps:

Stage Utility Network in enterprise gdb...

Apply Asset Package to gdb with new utility network as target

Publish Web Layer (it kept telling me during this that "some layers or tables are not present" that are related so I added them manually.  I would think though if it was reading it properly, I would not need to do that.  

 

Any suggestions?

0 Kudos
1 Solution

Accepted Solutions
RobertKrisher
Esri Regular Contributor

Disregard what @VenkataKondepati said about there being a utility network in the configuration tab. That is not a thing. I think he meant to tell you to enable the version management option (which you do have enabled).

In your statement you said you're going to ArcGIS Online, but I assume you meant to say ArcGIS Enterprise? You will add the data to your map using a feature service (this is discussed in the online help linked to above and the article I posted).

All of the items on the ribbon should be come enabled when a) there is a utility network in the map and b) you have the appropriate licenses applied to your named user.

View solution in original post

0 Kudos
4 Replies
VenkataKondepati
Frequent Contributor

Hi @JMathai,

Please follow the steps.

Delete the service.
Set your DB connection to Branch → pull the UN dataset into a fresh map → publish with Utility Network enabled in the Configuration tab.
If that option isn’t visible, your data is not Branch Versioned yet.
Don’t try to “fix” layers in the map.
Fix the data registration first.

Refer the documentation below:
Publish and consume services with a utility network—ArcGIS Pro | Documentation

 



 

Regards,
Venkat
Book a meeting with me:Get on a Call
Follow me on: LinkedIn

If this response helps or is the solution to your post, please consider marking it as a solution
0 Kudos
JMathai
Emerging Contributor

ok, I do not have that option even though I made sure I was branch versioned and used a fresh map.  

 

 

JMathai_0-1775508768189.png

 

0 Kudos
RobertKrisher
Esri Regular Contributor

Disregard what @VenkataKondepati said about there being a utility network in the configuration tab. That is not a thing. I think he meant to tell you to enable the version management option (which you do have enabled).

In your statement you said you're going to ArcGIS Online, but I assume you meant to say ArcGIS Enterprise? You will add the data to your map using a feature service (this is discussed in the online help linked to above and the article I posted).

All of the items on the ribbon should be come enabled when a) there is a utility network in the map and b) you have the appropriate licenses applied to your named user.

0 Kudos
RobertKrisher
Esri Regular Contributor

Make sure the map you used to publish your feature service has the utility network in it, and you should review the list of missing tables and consider including those in your service as well. The steps are outlined in this article: Deploying a utility network to ArcGIS Enterprise

If you end up dropping/re-adding any layers make sure that edit the properties of each layer so the layer IDs on your updated service match your original serviec.

0 Kudos