Any ideas on how to bulk create (and possibly edit) related table records?
Hi,
We have a ?point feature class and a 1:M related table. Users want to be able to select say 10 points and bulk create a record in the related table eg the point was inspected at cetain date, by certain person and the condition was good. I have it working in the HTML5 viewer to be able to create records one at a time, but was hoping to have a way to bulk create records. Not sure if it would be possible to bulk edit because of the 1:M relationship but maybe if I assume its always going to be the latest record? Any ideas on how I would achieve this using Workflow 5 or even 4 if I needed to?
Belinda
-
Belinda,
We did this for a tree inventory workflow. It's been a while, but if I remember correctly, you will need to remove the Esri relationship and manage the relationship entirely in SQL. This is because the Esri does not expose the sequencers for relationships in the REST interface and does some other backend things that if you tried to fiddle with cause nasty problems. So just create a table that contains a Foreign Key field to store the Features object id or other unique id.
Then in the Workflow, have the user select the features that they want to add related records to. Store the Primary key. Have the user fill out the information in a form. Then for each feature, write into your table.
To rebuild the "relationship", use the Data Connections.
0 -
Did you ever try doing it using the global id and keeping the relationship? I need to keep it so ArcGIS Collector can still add related records in the field.?
0 -
As I remember the issue was updating the rid (the foreign key) field. It was either locked or is managed deep inside sde and I wasn't able to find a way to maintain it without breaking sde. It was a couple years ago. Just a warning that if you are going to be that deep in sde. Please make sure that you are working on a test database or have excellent backups. You will need them. If you find a way, please let us know. Sent from Nine 0 -
@Tom Neer? I ended up editing the table record via a feature service. I just needed the global id from the point and then I did an add feature with the global id becoming the parent global id. We are storing our data in SQL storage format rather than the older SDE binary so it was easier than I thought. I can share the? workflow if you are interested.
0 -
Belinda Kerr, we are working on a similar workflow to edit related tables through a feature service and would love to see your workflow. Thanks in advance.
0
Du måste logga in om du vill lämna en kommentar.
Kommentarer
5 kommentarer