Hi -
Hoping for some help in resolving a workflow issue. We are building a new dam inspection form. We have a dam inventory (point) with a 1:M relationship to an Inspection table. Because the inspection form is very long and does not change much from inspection to inspection, we want users to be able to easily copy the previous inspection into a new form, make updates and submit. The relationship between the Dam points & inspection table is based on GlobalID/GUID; this has already been published as a hosted feature layer (AGOL).
I've tested two workflows which both have benefits and drawbacks. I am hoping for some advice on how to accomplish my goal.
GOAL: Easily copy previous inspection to a new form AND maintain the relationship to the Dam point.
Workflow A: Use Survey123 Inbox w/ the following settings - inbox surveys to be viewed (no editing of previously submitted inspections), allow inbox surveys to be copied to a new survey. THIS DOES NOT MAINTAIN RELATIONSHIP -- when I tested, the GUID is not populated with the Dam's GlobalID, hence relationship is broken. This is ideal because the entire form is copied and the user can make updates and submit a new inspection.
Workflow B: Use Survey123 form that contains dam information and all inspections conducted. Allow editing via Inbox. Can view previous inspections, but not edit them. Can add new inspections. Can not copy past inspection into new repeat. MAINTAINS RELATIONSHIP -- when I tested, the GUID is populated with the Dam's GlobalID and relationship is maintained. This is not ideal because while I can view the previous inspections, I can not select the most recent and copy it to a new repeat.
Potential Workaround: Use Workflow A to trigger Power Automate on submission. Power Automate grabs the GlobalID of the dam using another unique identifier and writes the GlobalID to the inspection's GUID field. This would work, however I am wondering if I am missing something obvious that would be a better solution.
Thank you,
Erica