Happy to help you with this as I had struggled with this and with the help of others on this forum learned that it's absolutely possible! Here's the code example:
// Calculation Attribute Rule on Inspections
// field: leave empty
// Triggers: Insert (and Update, if you want the rule to trigger upon editing an already existing form. Kind of up to your workflow.)
// Exclude from application evaluation!
// get the related asset
var asset_id = $feature.GUID
var assets = FeatureSetByName($datastore, "parent_feature")
var asset = First(Filter(assets, "GlobalID = @asset_id"))
// if there is no related asset, end expression
if(asset == null) { return }
// else populate attribute with the edit
return {
edit: [{
className: "parent_feature",
updates: [{
objectID: asset.OBJECTID,
attributes: {
Status: $feature.Struct,
LastInspDate: $feature.InspDate
// add additional attributes as necessary
}
}]
}]
}
So you add this attribute rule to the form table itself, not to the parent feature class. In this case, my parent feature is "parent_feature". You can get your correct parent feature name if you use the Arcade helper in the attribute rule and search for FeatureSetByName.
Basically, you use the GUID of your child feature class and then run a filter statement to match up the GlobalID of the parent to the GUID of the child. Then, down in the return statement, you enter in the attributes of the parent you want to edit based on the values from the newly created (or edited) child record. In the example above, the attribute "Struct" from the related record will be populated into "Status" from the parent record, etc.
