Electric Distribution Data Management for ArcGIS Online fail to deploy

1170
3
Jump to solution
05-22-2021 06:40 AM
TimoSjösten
New Contributor II

Electric Distribution Data Management for ArcGIS Online repeatedly fail to deploy at 49 percent. Any suggestions highly appreciated.

TimoSjösten_0-1621690777571.png

Update 23.5:

I was able to deploy both Stormwater and Communications Data management for ArcGIS Online but Electric Distribution, Water Distribution and Sewer Data Management didn't work despite several retries. Also now I have ended up with a folder named "Electric Distribution Data Management for ArcGIS Online" with a feature layer named ElectricDistributionMapNotes that I'm unable to delete. Gives me the following information when I try to delete the feature layer:

TimoSjösten_1-1621777985109.png

and the following when trying to delete the folder:

TimoSjösten_0-1621777869747.png

2 Solutions

Accepted Solutions
Todd_Harrington
Esri Contributor

@TimoSjösten 

Click on the item details for the feature service that refuses to delete,

Scroll down and click View above the Service URL box:

Todd_Harrington_0-1621863737987.jpeg

 

 

Confirm the “Has Views” property is true:

Todd_Harrington_1-1621863737993.jpeg

 

 

Click the Views link, just below Has View: true

The views page will show the Views that the system believes exist:

Todd_Harrington_2-1621863737996.jpeg

 

 

Click the link for one of the views and you should get an invalid URL

Back on the views page, copy the full name of the view: for my example, the top view full name is “WaterMapNotes_editing_490a541df35a4ca7a2e02e3d2ce6795d”

 

Back on the Service Item details page in ArcGIS Online for the Feature Service that won’t delete, scroll up and click Create View Layer:

Todd_Harrington_3-1621863737997.jpeg

 

 

Paste the copied name into the Title box:

Todd_Harrington_4-1621863738000.jpeg

 

Click OK to create the view accepting all other defaults.

After the view is created, delete the view.

 

Repeat the process of creating a new view with the old name and deleting for each view that shows in the views page:

Todd_Harrington_5-1621863738001.jpeg

 

Now you can delete the feature service.

 

Todd

View solution in original post

Todd_Harrington
Esri Contributor

Great @TimoSjösten . It's a known issue with the deployment app. It's not a particular solution but rest assured it's being looked into. 

 

Todd

View solution in original post

3 Replies
Todd_Harrington
Esri Contributor

@TimoSjösten 

Click on the item details for the feature service that refuses to delete,

Scroll down and click View above the Service URL box:

Todd_Harrington_0-1621863737987.jpeg

 

 

Confirm the “Has Views” property is true:

Todd_Harrington_1-1621863737993.jpeg

 

 

Click the Views link, just below Has View: true

The views page will show the Views that the system believes exist:

Todd_Harrington_2-1621863737996.jpeg

 

 

Click the link for one of the views and you should get an invalid URL

Back on the views page, copy the full name of the view: for my example, the top view full name is “WaterMapNotes_editing_490a541df35a4ca7a2e02e3d2ce6795d”

 

Back on the Service Item details page in ArcGIS Online for the Feature Service that won’t delete, scroll up and click Create View Layer:

Todd_Harrington_3-1621863737997.jpeg

 

 

Paste the copied name into the Title box:

Todd_Harrington_4-1621863738000.jpeg

 

Click OK to create the view accepting all other defaults.

After the view is created, delete the view.

 

Repeat the process of creating a new view with the old name and deleting for each view that shows in the views page:

Todd_Harrington_5-1621863738001.jpeg

 

Now you can delete the feature service.

 

Todd

View solution in original post

TimoSjösten
New Contributor II

Thanks Todd, your instructions on how to get rid of the orphaned feature service and folder worked well for me.

I did a few more tries to deploy the Electric Distribution Data Management for ArcGIS Online but that one still repeatedly fails (now at 57 %). Any ideas of what could lay behind this problem?

Timo

0 Kudos
Todd_Harrington
Esri Contributor

Great @TimoSjösten . It's a known issue with the deployment app. It's not a particular solution but rest assured it's being looked into. 

 

Todd

View solution in original post