Linking to related/sub-surveys from a Form

Question

I have an inspection form that creates a point and contains some basic information about the inspection. I then have 13 related tables (repeats) that each have a significant number of questions for each section of the inspection.

The issues I have run into:

-Could not publish a service with so many related tables (originally 16 different sections of the survey), so I combined a few sections until it could be published successfully.

-Published survey will open on Android devices, but the requirement is for it to open on iOS devices. The survey is so large, iOS will not open a new survey (it crashes).

That leads me to the new issue:

-I want to break the survey up into 3 separate surveys. A 'main' survey for the basic information, then 2 'subsections' that contain 6 and 7 sections of the inspection, respectively.

-The hosted service is published with a globalid --> parentguid relationship. This poses an issue, because I have to submit the 'main' survey before I can pass a globalid into a URL scheme to open a sub-survey that will retain the relationship. I have been trying to make it work with the Inbox enabled, but can't figure out how to pull the GlobalID of the point feature and pass it into a URL. ${globalid} is not allowed in a survey since it is a read-only attribute. Thinking about a pulldata() function, but there's nothing to pull until after the survey is submitted. Are there any ideas I haven't tried or am I trying to do something not possible?

dougbrowning · Answer

No we do one form at a time.  If your user has to jump it prob will not go well.  Try and have the forms match the workflow.

bbaker_tngeo · Answer

Thanks for the suggestion, @DougBrowning . I was thinking of using an on-the-fly generated key, but did not want to  reconcile to a globalid/parentguid relationship on the backend, which is how the feature layer is published.

I ended up going a different direction with pre-loading the points and then breaking the inspection between 2 surveys that can be accessed through the Inbox. I was wondering if your workflow required the users to jump between the different forms?

I want to be able to create a URL that allows a user to jump between the 2 surveys, let's call them "Part 1" and "Part 2". However, from what I am seeing, there is no 'autosave' option in the field app. So, if I have a note with a URL and a user clicks it, they will lose their progress in "Part 1" if they go to "Part 2" before saving to Drafts. The same would be true if they went from "Part 2" to "Part 1".

bbaker_tngeo · Answer

They are intended to be single records, but need to be saved to related tables because the inspection schema is too large to publish as a single feature layer. The survey is already split into pages, but crashes when attempting to load on an iOS device. I ended up splitting the survey into two surveys:

The first survey creates the point and contains 6 of the 13 sections with inspection questions. When a user completes the first section, the submit the survey.

The second survey does not allow new records to be created, but is accessed through the survey's Inbox. When the Inbox is refreshed, the user can select the record they just created from the first survey, and complete sections 7-13.