Recurring Inspections - Survey 123

3512
16
01-04-2018 10:22 AM
JonathanGerardo
New Contributor II

How can I link several Survey123 forms to one point? For example, a field staffer is required to perform annual inspections of stormwater outfalls. One point - same form - multiple surveys. 

16 Replies
DamienHoffman
New Contributor III

If you have your question set in a repeat (child) and your geopoint outside the repeat (in the parent) you could collect the point (applied to all surveys), fill out the survey, and upload.  Then on the second visit to the site, select the survey from your sent surveys, select "edit and resend survey," hit the repeat (with your survey), fill out the next survey portion in the repeat, then upload to update.  

I'm not sure that is the solution that you want but it seems like it would work.

0 Kudos
BrandonArmstrong
Esri Regular Contributor

Hi Jonathan,

Please take a look at the following Blog Post and let us know if you have any questions.  You may find this video particularly helpful.

Brandon

0 Kudos
JonathanGerardo
New Contributor II

Thanks for the responses. Initial thoughts - By using repeats and editing a previous survey the user would have to delete all of the past information for each field/question which wouldn't make for a very efficient workflow. Also, how do you access/analyze previous surveys. Are they all part of the same XLS or are they different forms that are not linked to the geopoint?

0 Kudos
DamienHoffman
New Contributor III

I was thinking based on "One point - same form - multiple surveys," being the form doesn't change, you could put the form questions in a repeat.  Users wouldn't have to edit previous data. Just hit the + on the repeat and add a new record.  Add a date field to the form (in the repeat) to distinguish when the additional surveys at the point happened.  All repeat (child) records are linked via parent global id.

JonathanGerardo
New Contributor II

Thanks Damien, we'll try this approach. Sounds like this may work. 

0 Kudos
JonathanGerardo
New Contributor II

Having trouble creating a survey with an existing feature class (issues publishing, creating questions, etc). We have no problem creating surveys from scratch, however, linking to existing data using Survey 123 Connect is not working.

Is there a resource that provides step-by-step instructions for Survey123 beginners. The intro Survey123 webinar that was recommended to us by ESRI did not address these issues. 

0 Kudos
JamesTedrick
Esri Esteemed Contributor

Hi Jonathan,

Are you publishing the feature classes to ArcGIS Online, a service (either hosted or federated) in ArcGIS Enterprise, or a service on a stand-alone ArcGIS Server?

A good guide to getting started is https://community.esri.com/groups/survey123/blog/2017/09/25/working-with-existing-feature-services-i... 

JonathanGerardo
New Contributor II

James,

We read the suggested article but we are having trouble creating a survey that will work. Our understanding is that you need to remove the fixed field types from the survey which will not change (ID, coordinates, etc) and add the questions that will be answered during each inspection. 

Also, if the first survey is created (Year 1) and we return in Year 2 to complete an annual inspection report, where are these copies stored and how can each survey (past and present) be retrieved from the point data. The Survey123 function is exactly what we need, but the implementation for existing features is very confusing. Thanks.

0 Kudos
JamesTedrick
Esri Esteemed Contributor

Hi Jonathan,

How is the inspection data set up in the geodatabase?  Normally, we suggest the following set up for inspections:

- A feature class of the assets

- A table/feature class for the inspections

There should be a 1:M relationship from assets to inspections

The semi-permanent information is stored within the asset table, while the information that changes from year to year is the inspection information; additional year's information are stored in new records in the inspection table.  In the XLSform, this is implemented by having the asset information be stored in parent portion of the form, with the inspection being stored in a repeat section.