Reversing relationship classes in the Pacrel Fabric

[RobertChaney]

I started a topic a while back under a different product\community and didn't get much traction.  So, it was recommended I open a support incident with ESRI.  Based on the communications with ESRI, I decided to post this topic in this community.

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. 

Thanks.

Here's the location of my original post:

https://community.esri.com/t5/attribute-rules-questions/arcade-expression-calculation-rule-to-update...

[AmirBar-Maor]

@RobertChaney 

It's hard to comment on your Attribute Rule with regard to the relationship direction. However, when we perform certain operations we do account for the 'StatedArea' and either combine the areas (merge) or proportionally divide them (split).

The calculated areas field is different, it uses the COGO values, if available, to calculate the area. The Build command  (Active / Extent) will update that field.

How are you splitting the parcel and which commands are you using?

[RobertChaney]

The field I have the attribute rule assigned to is not a designated fabric field.  It's a field that's was copied over from the original data when the fabric was initially created.  The Attribute Rule is: Area($feature, "acres").

It's assigned to the field called "Calculated Area".

I'm performing a split by selecting a parcel and then using the split tool interactively.  If you look at the attached file(s), the two resulting parcels after being split have values in the Calculated Area field.  However the top record still shows the Calculated Area value (22.161064) before the split.  I have to make a edit to say the parcelid field in order the the Calculated Area value to change to it's proper value.

ESRI's suggestion was to reverse the relationship class, once this was done the values in the Calculated Area field changed as soon as the split was made.

[AmirBar-Maor]

@RobertChaney 

While this is not specific to the parcel fabric, and assuming you are trying to populate your own field (not a parcel fabric system field) - this seems like a bug to me, but we'll need to examine it more closely. I'll follow up with you directly to obtain your data and have a closer look.