nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Include the child form in the parent form so they can be completed in a more streamlined fashion

RuimengPang

Can we make editing the parent form and the child form more streamlined?

Since I use the datastore to update the record from the child visit record to the parent location record on fields like "latest visit date", "latest status", "latest occupancy", so the information from the visit can be used for symbology in the parent layer to provide useful information for the field workers.

Right now the ideal workflow is: create location - enter info - submit - insert visit record (which most people already forget) - submit - go back to location layer - edit location - submit location (to update the auto populated fields from the visit record just inserted)

if the parent and child forms are more unified the workflow can be:

create location - enter info - save - child form pops open - (if no need to enter just cancel) enter - user chooses "Save Child" or "Save All" - all records updated at the same time and no one forgets to add a child record.

Find more posts tagged with

Data collection

Mobile App

Smart forms

offline

Status: Open

Comments

HollyTorpey_LSA

This is a major pain point for us as well, and I agree with your idea.

A use case example is nest monitoring, where we create one point for each nest and then add observations to a related table. We'd like the nest point symbology to automatically reflect the most recent nest status, but in order to do this, we have to instruct our field biologists to click edit + submit on the nest point after they add a nest observation. This is the part that needs to become automatic (or at least easier... a single obvious click of a button to update the parent feature rather than a non-intuitive workflow that our field biologists frequently forget to carry out). It's complicated by the fact that when they click edit on the nest point, they see that giant blue "Update Point" button that seems like it would do the trick but actually just moves the feature, which we do not want.

Here are the instructions currently on our nest monitoring template (and people still rarely remember to update the nest point):

(Plus icons are in different places depending on the device and version, so I keep having to update the instructions, and I can see that I need to do that now.)

Some related posts, lest anyone think this is an isolated need:
Solved: Updating Feature Layer Attribute with Related Reco... - Esri Community
How do I update a field value for a related table ... - Esri Community
Field Maps Inspection/Maintenance Workflow & Recor... - Esri Community
Run Calculate Field or a TRIGGER when performing a... - Esri Community
How to update a feature layer from related table d... - Esri Community
Editing parent attribute from child - Esri Community
Solved: Symbolize by Related Table in ArcGIS WebMap - Esri Community
Solved: Using Field Maps to Inspect Infrastructure Multipl... - Esri Community