Intersect Attribute Rule Failing when Splitting Existing Features "Invalid search geometry"

RexRobichaux

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

 

KimberlyGarbade

You know.... I used your code (had to change some names of course) on some sample data and it works like a charm.  I've tried to break it by disabling the script from running on "Update" (which at first I thought was the problem - its not) and by setting "Exclude from application evaluation" (even though not sure it would matter in this case) and it just keeps working.  The one time it didn't work was when I had an error in the polygon geometry I was splitting.... So maybe your problem isn't the script but the data it uses.

As an FYI and probably apropos of nothing:   I didn't set a variable named "intersecting_field" so, for example, my script used "return '51'+intersected_feature.FIPS;"... but like I said, can't see why that would make any difference at all.