Keeping pts, lines, and polygons from a single incident together

[SueBoelk]

Okay, here goes:

We have a quick response HazMat team that gets called out at all hours. The Quick Capture app will be used to collect pertinent info about each call-out. It will be used over and over and needs to follow an orderly process, making collecting cohesive and orderly.

They have requested an app where they can gather info about the incident with 6 point features that will have the ability to collect photos. 

The Incident# is assigned later in the process and the team needs to get out in the field and begin collecting data as soon as possible.

Statement: I've thought about using a unique identifier to assign to each pt, line, and polygon collected to keep them all related to the same Incident. Initially I thought that the Incident# would suffice, HOWEVER, the Incident# might not be assigned immediately

Question: Is there a way to do what I have proposed? ....to id the pts, lines, and polygons as part of Or related to the same Incident.

Thank you!

 

[VenkataKondepati]

You can achieve this with Relationships based on auto-generated Unique id (a GUID). If you click on polygon, it will show related points, lines and other records.

Example: HazMat-20260123-1405

[SueBoelk]

Thank you Sir! I will try it.

[DavidSolari · Accepted solution]

Unless something's snuck in over the years, QuickCapture can't handle related records in the same way Field Maps & Survey123 can. You can link to layers in relationship classes but features you create won't be related to each other. My suggested workaround: use a Project User Input that maps to a "Temporary Group ID" field in all of your Hazmat layers, and have your team use another app to generate a random ID to copy-paste in before starting the work. Once all their data is in you can use the temp IDs to assign the same incident ID to everything and the rest flows from there.

[SueBoelk]

Thank you David!