I am trying to create attribute rules in arcade for 2 branch versioned feature classes in a relationship class.

JeffTimm

When I update site_p I want the correlating fields in site_a to be updated as well. The relationship class is realated on the field "rpsuid"

Here is my code:

 

 

// Step 1: Get the related records from site_a using the correct relationship class name
var relatedRecords = FeatureSetByRelationshipName($feature, "usar_hq.rd_81.Site_P_Site_A", [], false);

// Step 2: Get the first related record
// Explanation: We use the First() function to get the first record from the related records.
var related_record = First(relatedRecords);

// Step 3: Check if a related record is found
// Explanation: We check if related_record is null. If it is, we return null to stop further processing.
if (related_record == null) {
    return null;
}

// Debugging: Print the related record
Console("Related record: " + Text(related_record));

// Step 4: Populate fields in the main feature class with fields from the related record
// Explanation: We create an object to return the desired fields from the related record.
return {
    "debug_field": related_record.debug_field
    // Add more fields as needed
    // Uncomment and modify the lines below to include additional fields
    // "accountableorganization": related_record.accountableorganization,
    // "anotherfield": related_record.anotherfield
};

 

 

and I get this error:

Edit operation failed.
Message: Unable to complete operation.
Details: Internal error during object update. Undefined keyword is used in the dictionary return script. [
Rule name: Site_p2a,
Triggering event: Update,
Class name: Site_P,
GlobalID: {AAF25529-13CD-448C-BDC2-C83DE21711EF}], Undefined keyword is used in the dictionary return script. [debug_field]

 

debug_field does exist in the feature class and service.  What am I doing wrong?  I am sure it is a stupid syntax error on my part.

 

 

 

 

 

 

JeffTimm

I finally figured this out.  Something so easy I can't believe I overlooked it.  I was applying the attribute rule to that parent feature class in the relationship class.  This is incorrect.  The attribute rule should be applied to the child feature class.  The one where the edits are applied to once the parent feature class is triggered with an update.  I was also able to simplify the code.  I was making to complex trying to get it to work.  Below is the code that ended up doing the trick.  I did notice a delay in the updates to the child feature class.

// calculation attribute rule on child
// field: if you want to get only one field from the parent, then chose 
// that field. if you want to get multiple fields, leave empty
// triggers: Insert(, update)

// load the related parent features using
// a relationship class between parent and child:
var parent_fs = FeatureSetByRelationshipName($feature, "db.schema.AttributeRuleName")

// return nothing if no parent feature was found
var parent = First(parent_fs)
if(parent == null) { return }

// if you want to return multiple fields:
var att = {
  "accountableorganization": parent.accountableorganization,
  "coordinatex": parent.coordinatex,
  "coordinatey": parent.coordinatey
}
return {"result": {"attributes": att}}