Question about related tables

[SueBoelk]

Here is a Shot in the Dark:

We have a Survey123 project that was initially developed to do an inspection. The 'Begin Inspection' and 'Quarantined Shipment?' and 'Premise Inspection' is completed. Original long form is enclosed.

The user decided the first form was too long and wanted a survey to collect preliminary info and photos and then to fill out Parts II, II, & IV in the office.

Enclosed is the survey as it was first developed. (Also enclosed is the shortened survey that the user requested after seeing the length of the original survey).

Here is a bit of further explanation about how the inspections will eventually work:

If Part II - Farm or Non-Farm Use is chosen, Parts III and IV can be skipped and the inspector can go to the end of the survey.

The same applies if the seed is AG/Grass/Germination  OR Veg Seed Only, the inspector answers the questions only for the type of seed being inspected.

1) The aim of the shorter survey is meant to gather relevant data and photos in the field.

2) The inspector will then return to the office and us the shortened survey and photos to fill out the info for one of the three sections: 

II. Farm or Non-Farm Use

III. AG/Grass/Germination

IV. Veg Seed Only

QUESTION:

Is there a way that we can relate the first, short survey with 'Begin Inspection' and 'Quarantined Shipment?' and 'Premise Inspection' to separate related tables to be filled out in the office? 

II. Farm or Non-Farm Use

III. AG/Grass/Germination

IV. Veg Seed Only

(We are in the process of developing Pts. II, III, & IV for use separately.)

The form will be converted to a report. 

Realizing that this is a big Ask, I appreciate your learned input!

[DavidSolari]

I haven't dug into your specific form, but in general:

• If you aren't linking your survey to an existing feature service then you can create "repeat" question blocks in the survey. Each repeat block adds a new layer to the Survey's feature service with a 1-M relationship class ready to go. You can then have the rest of your workflow make edits to those related layers outside of Survey123, just make sure to use the "relevant" or "readonly" columns as needed to keep the repeats off limits to the initial survey.
• Alternatively, you can create the related table structure in your own feature service, then link the survey to that service. This requires more work than letting the Survey123 tools build the service itself but you get the ability to bolt Survey123 as an interface over existing workflows, use registered services that store your data in an EGDB, and maybe some other benefits.

Either method has the same result: the Survey123 user fills out their part of the data, and then the rest of your org can populate related records for each form submission.

[SueBoelk]

Thank you David. I will look into the directions you've given! 

[TylerGraham2 · Accepted solution]

Keep in mind that a form doesn't have to call on all the fields or related tables in a feature service.  What I would think about doing is creating 3 forms if you're doing all the set up in Survey123 Connect. The first for would be your "template" that you publish, share the feature layer it creates, but not the form. 

The second form would be for the field work portion and point it to the existing feature service created when you published form 1.  

The 3rd form would also point to your existing feature service from the first form but just include the office portions of it.  Set it up to use the inbox and set a query to define what existing records are pulled in, then they can select from the list and edit the record.  

Alternately you might thing about using pages on your existing forms to break them up into more manageable sections which would require less scrolling.  Also look at using the relevant column in your xlsform to show hide fields based on answers to other questions.  

[SueBoelk]

Thank you!

[abureaux · Accepted solution]

Is there a way that we can relate the first, short survey with 'Begin Inspection' and 'Quarantined Shipment?' and 'Premise Inspection' to separate related tables to be filled out in the office?

Honestly, short answer here just seems to be to make those repeats/questions not required or not relevant until such a time as you are ready for them to be used.

EDIT: In case it wasn't clear, I mean to use just the long form, ditching the short form entierly. Then, make use of the "relevant" or "required" columns are necessary to turn your "long form" into the "short form" on the fly.

[SueBoelk]

Thank you abureax!