We have set up a new ArcGIS Enterprise version 11.3
We are trying to migrate old QuickCapture Projects from our 10.9.1 Enterprise (Note this was not an upgrade - this was installing a new environment and shutting down the old)
I have downloaded my Quick Capture Point and Line Layers and loaded them into the new 11.3 Hosted database. I have configured my new Quick Capture App to use these layers.
The app appears to capture points and lines, however lines are not captured and points have coordinates of 0,0 and show off the coast of Ghana. The coordinates populate into the table and appear ok.
I also tried creating a brand new Quick Capture using one of the ESRI templates - I used the wildlife template. I get the same results - Points are at 0,0
When I set my Quick Capture up about ten days ago - I was able to capture points and lines, but am now unable to. Any suggestions appreciated.
Thankyou
Solved! Go to Solution.
Issue resolved in 1.21.18 - available in stores now.
@JonathanPollack - Good point. Please see the updated steps above. These have been simplified and work for points, lines and ploygons.
I am having this problem now, slightly differently in a portal QuickCapture App. My QuickCapture app writes to two different point layers. The first is an editable enterprise service which has been working perfectly, and the other is a layer created in my portal account with the [+New Item] button. The points created in the enterprise service are showing exactly where they should, but points in the new layer are writing at 0,0.
We are on portal 11.3, iPhone app version is 1.21.20
I figured out a work-around: When I created an empty portal feature layer with "Define your own layer" option, I had the above issue, I then tried the "Provide an ArcGIS Server layer URL" option to create my new point feature class and it works as is expected, the points store in the location I place them in the QuickCapture app.
@KevinN_CSJ - You should not be seeing this issue on 11.3 and 1.21.20 with hosted feature services.
What authentication method is your portal using?
We use SSO authentication