Arcade expression: Calculation rule to update field upon edit, split

[RobertChaney]

I have a simple calculation attribute rule which calculates the area for the CalculatedArea field, set to trigger on insert and update.

Area($feature, "acres")

When performing a split on a selected parcel, one of the new polygons gets the CalculatedArea field updated the other still retains the original CalculatedArea value prior to the split.  I have to make an edit to some other field to force the CalculatedArea to field to show the updated value based on the split.  How do I get the CalculatedArea field to update both polygons once the edit (split) is made?

This is run on a feature service.

[MikeMillerGIS]

We discovered this issue the other day and logged it with the dev team.  I am not sure of a workaround at the moment.  I think the only option is to log a tech support incident so we can get a bug attached to it.

[RobertChaney]

It seems strange that this would be happening since the Shape.STArea() field clearly shows the change after the split.  I'll take your suggestion and log a support incident.  Thanks.

[RobertChaney]

After opening an incident with ESRI, they came back with the suggestion of reversing the order of the relationship class.  I forgot to mention in my original post that my data is in a Parcel Fabric (sql database, edited through a feature service).  When the Parcel Types are created, relationship classes are created automatically.  Originally, my data shows the TaxParcels being the destination and the Records being the Origin.  We deleted the relationship class and recreated the relationship for the TaxParcels and Records, this time the TaxParcels are the Origin and the Records are the destination.  After recreating the relationship and performing a edit (split), the CalculatedArea field shows the update immediately.  The ESRI support wasn't a Parcel fabric specialist so, I'm not sure what the ramification are of reversing the order of this relationship class since they're created automatically.  If anyone would like to move this topic to the Parcel Fabric community, I'd appreciate it.

Thanks.

[HusseinNasser2]

This bug can be tracked here BUG-000158046

it was fixed and ported to 2.9.10 and will be addressed in 3.1 and 3.0 patches

[JoseSernaUDC]

@HusseinNasser2 Does the attribute rule have a way to detect the split? I can think of checking for the geometry change and doing other logic, but I was wondering if there is a out of the box way. 

[MikeMillerGIS]

No, there is no context that the edit was the result of a split.