Hello!
I have created a couple attribute rules that update a related table with values from the parent point feature. We found that the attribute rules work well in all platforms (pro to field maps), however they do not work when pulled into a new Pro project or published from a new Pro project. Other attribute rules that don't reference the parent feature still work. Does anyone know why this might be the case? Is there a problem with the code or the way the code accesses the relationship class?
Here's a sample of Arcade the code I used:
// Retrieve the parent features based on the relationship with the child feature
var parentFeatures = FeatureSetByRelationshipName($feature, "DBO.RelationshipClassName");
if (Count(parentFeatures) == 0) {
return null; // Return null if no parent features were found
}
for (var parentFeature in parentFeatures) {
return parentFeature["SITE_NO"]; // Return the SITE_NO field value from the first parent feature
}
Thanks!
