Here is an example of an INTERSECTING_FEATURE record in the DynamicValue table:
OBJECTID * | Table Name | Field Name | Value Method | Value Info | On Create | On Change (Attribute) | On Change (Geometry) | Manual Only | Rule Weight | Comments |
193 | CENTERLINE | CITY_LEFT | INTERSECTING_FEATURE | ZIP_CODES_WITH_CITIES|CITY|C | True | False | True | False | 1 | <Null> |
Table Name is the target layer with the field that needs to be completed by another intersecting layer
Field Name is the field name in the target layer
Value Method is INTERSECTING_FEATURE (any one of the Attribute Assistant methods)
Value Info is made up of 3 components separated by a | character. The components are: Intersecting source Feature Class Name|Field Name in the source Feature Class|C(Centroid match) (alternatively I could have used P for Prompt for an option or F for using the first feature intersected)
On Create is set to True so that the moment the feature creation is finished the attribute will be updated.
On Change (Attribute) is set to False, since it doesn't need to refresh due to an attribute change.
On Change (Geometry) is set to True so that any change in geometry refreshes the attribute (the intersecting feature should have been fixed first before the target feature geometry changes).
Manual Only is false, but it could be true if I want to use the Attribute Assistant toolbar to force a refresh
Rule Wieght is optional but I ususally set it to 1
Comments provides any explanation of the purpose or use of the rule.
An Expression update does needs to have its Value Info written the same way you would write a VB Script field calculation. Use the field calculator to test your expressions and ask for help here if you have problems with a specific equation.