POST
|
Hello! I am running into the same issue that you mentioned above. I recreated the feature class, but I am still receiving the same error. Did you have to change the schema or anything else about the feature class to get this to work? Is your feature service hosted? Thanks in advance!
... View more
12-16-2022
11:25 AM
|
1
|
0
|
908
|
POST
|
Hi Doug, Thank you for the reference to that blog post. It does look like that could work for me. However, I noticed that in your example you are using Hosted Feature Services. Have you implemented this workflow using feature services coming from a non-federated ArcGIS Server? Do you know if the workflow would still be the same? Also, in step #3 ("Create a new GDB in catalog - this holds your collector features"), can I just use an existing SDE GDB? I would rather not create a new GDB and use the existing SDE GDB where all of my data is housed. Could I just copy the Survey123 FC to that GDB and create the Relationship class in there? The only other step I would want to change is #8 ("Publish this gdb as a service") - I do not want to publish the entire GDB as a service. I would just want to publish the FC with the related table. Would this still work with the workflow you described? Thanks for your help!
... View more
11-13-2019
07:10 AM
|
0
|
2
|
2343
|
POST
|
Hello, Ismael Chivite, James Tedrick Our Public Works Department would like create an Asset Inspection workflow using Collector and Survey123. The idea is to view the asset on the map in Collector, tap on it, and be able to edit existing attributes if needed. In addition, there would also be an embedded Survey123 URL in the pop-up that would open a Survey123 form with questions related to asset inspections. Once an inspection has been submitted, we would like to view past inspection records by clicking on the asset in Collector and viewing the related records. The goal is to have the inspection related to the feature and not have a new feature created with every inspection. I have set up a secured feature service with both the features to be inspected and an empty related table for inspections that are being related with GlobalID and GUID. I created a survey in Connect using the feature service as a template and set the survey submission URL to read a secured feature service that passes through AGOL (with credentials stored) from our ArcGIS Server. Next, I open the survey from the pop-up in Collector (using the custom URL scheme) and fill out the form in Survey123. The problem I’m running into is when I submit the survey, it’s not just going into the related table, but it’s also creating a new feature in the feature class. I just want the inspection to be a related record to the asset I’m inspecting and not create a whole new feature for each survey. Is there a way I can set up this workflow so that each inspection (survey) is related to the asset I’m inspecting without creating a new point?
... View more
11-12-2019
11:38 AM
|
3
|
10
|
3656
|
Title | Kudos | Posted |
---|---|---|
1 | 12-16-2022 11:25 AM | |
3 | 11-12-2019 11:38 AM |
Online Status |
Offline
|
Date Last Visited |
12-16-2022
07:28 PM
|