Select to view content in your preferred language

Hang when creating Hosted View layer via UI

159
1
Jump to solution
08-13-2024 08:40 PM
Labels (3)
DavidBroadhurst
New Contributor

Trying to create a new View Layer from an existing Feature Layer. The source feature layer has 7 layers contained within it (created from ArcGIS Pro). The view I'm trying to create pulls through 3 of the layers and filters them.

Was able to successfully create 14 views from the source layer but now it is just hanging when I hit the +Create button after defining my filters. The system displays a progress dial which continues to turn, but it never completes.

I thought this might be due to a limitation of the number of views created from a single feature layer, so have pushed a duplicate copy of the source layer into AGOL. I was able to successfully create one view from that duplicated layer, but when trying to create a second view from the duplicate the create process hangs.

I can see a hosted view layer being created in my home folder (this seems to happen as soon as I hit the create button) but the definition of this view is incomplete (it doesn't contain the filters I've defined).

I need to create 20 views of the original data, and I don't think I should have to load multiple versions of the layer from ArcGIS Pro. The use case here is exactly what Views are created for (in my understanding).

Anyone seen this sort of a problem before? Did anyone find a solution?

0 Kudos
1 Solution

Accepted Solutions
DavidBroadhurst
New Contributor

Issue resolved (we think). Seemed to be a technical glitch in the platform that was stopping the service update API calls to work. I traced the network calls and the browser was just polling for the completion of the service request and that never happened). Raised it via our local ESRI office and I don't know if they had the support folks do anything but it started working again.

Network tracing when it is functioning correctly shows it create the service, update it, then do a few more updates, then rename it and move it to the folder you defined it should go in. It does this over multiple API calls.

View solution in original post

0 Kudos
1 Reply
DavidBroadhurst
New Contributor

Issue resolved (we think). Seemed to be a technical glitch in the platform that was stopping the service update API calls to work. I traced the network calls and the browser was just polling for the completion of the service request and that never happened). Raised it via our local ESRI office and I don't know if they had the support folks do anything but it started working again.

Network tracing when it is functioning correctly shows it create the service, update it, then do a few more updates, then rename it and move it to the folder you defined it should go in. It does this over multiple API calls.

0 Kudos