I have been working to build a new inspection & associated maintenance tracking protocol for my Public Works Dep. I have a point feature layer of representing thousands of stormwater management facilities. Each facility is inspected every two years, and the result of the inspection drives a need for maintenance. The maintenance is then performed, and I need to have a record of both the inspection, and any associated maintenance that was performed. There are only a few fields required to capture the contents of the inspection and the maintenance.
I saw this as a typical relationship class application, and created one with the mapped stormwater facilites as the parent layer, and a table with the required inspection and maintenance fields as the child, using a GLobalID and GUID field for the relate. Then uploaded to AGOL, brought into Field Maps Designer, built a form to capture the inspection data, created some test inspections, and then used the Analysis tab in Map Viewer to create a dynamic feature layer with the inspection records from the related table joined back to the parent feature layer. I can use this to view the inspection results and see what features require maintenance.
I am now at a pivotal point that I feel never gets addressed by ESRI with inspection work flows, task assignents, ets. I need to be able to create associated maintenance records for these features, that will be stored in a database as a one-to-many relationship. I feel like this is something that keeps getting lost in the suite of ESRI inspection work flows. I just went through the functionality of enabling Tasks in Field Maps and I don't think it will work for my needs, as it seems to work in a one-to-one relationship, one task per feature and you can only update the attribute, not build out a one-to-many database over time.
I feel like I can't be the only one needing this funcitonality, so I'm curious what others have done to solve this. It seems like the Joined Feature Layer is somewhat fickle, not allowing updates to the parent or childs schema. If I could reliably update this joined layer with the maintenance data, or somehow use the data from the joined layer to drive updates on another related table for maintenance records, that seems like it would fulfill my needs. I am not skilled enough in Arcade to know how to drive such a function, but would love to hear if anyone has used it for something like this.
Feeling quite dissapointed in this rollout of Tasks not supporting related records, I honestly don't see many cases where the application is even that useful if you can't leverage it with the functionality of a relationship class. I don't really understand why ESRI keeps releasing these AGOL tools with only partial to zero related data functions, when the whole environment is sold as a multi-user solution for applications that typically rely on that function.
