Intersect Attribute Rule Failing when Splitting Existing Features "Invalid search geometry"
Hello everyone,
We had a series of attribute rules built out for our editors the methodically produce a unique permit specific ID field. One of the first attribute rules retrieves the county/locality FIPS code for a polygon feature upon create/insert, as this is used in the unique ID field. This works fine when drawing/creating a new record. However, I'm getting an ambiguous "Invalid search geometry" arcade error when trying to split an existing polygon feature in ArcGIS Pro.
Environment:
- ArcGIS Pro 2.9.x
- Geodatabase: Oracle 19c
- Editing through editable 10.7.1 feature service - unfederated server.
Here's a screenshot of the error upon trying a split:
The offending attribute rule's properties:
It seems as though the problematic line below would indicate Pro isn't passing the "new" split feature as the search_feature / $feature into the following line properly...or I might very well be completely misunderstanding how splits are handled in the Pro client and sent to the geodatabase for evaluation.
var search_feature = $feature;
var intersected_feature = First(Intersects(intersecting_featset, search_feature));
// This rule will populate the edited features field with a value from an intersecting feature
// Value to copy from the intersected feature
var intersecting_field = "FIPS";
//Field rule is assigned to in the Attribute Rule
var feature_field = $feature.FIPS;
// Create feature set to the intersecting class using the GDB Name
var intersecting_featset = FeatureSetByName($datastore, 'GIS_DBA.VA_COUNTY_BOUNDARY_STG', [intersecting_field], true);
var search_feature = $feature;
var intersected_feature = First(Intersects(intersecting_featset, search_feature));
// Check to make sure there was an intersected feature, if not, return the original value
if (intersected_feature == null)
{
return $feature.FIPS;
}
// If the intersected feature is null, return the original value
if (IsEmpty(intersected_feature[intersecting_field]))
{
return $feature.FIPS;
}
// Return the intersected features value
return '51'+intersected_feature[intersecting_field];
I'd love to hear any ideas anyone might have on this one and why this rule can't seem to properly interpret the split feature. @HusseinNasser2 and anyone else- thanks for any help and ideas you might have!
-Rex
