Parcel Fabric Record Dataset not moving with Property Polygon

[MarkWasdahl1]

Version 3.5.4

After selecting the entire parcel polygon, including lines and points, and using the Move Tool to reposition the selection, the Record stays behind at the original position. The Record polygon will move if the Shrink To Seeds and Reconstruct From Seeds Tools are used but in the following situation the property polygon deformed. The moved Encumbrance polygon was accurately placed on top of two other Encumbrance polygons. 

The second photo shows the result of Reconstruct From Seeds Tool use.

Any ideas?

[pt_instructor · Accepted solution]

Hi Mark, simply running Build Extent should reconstruct the boundaries of all Record features. For each record, the tool recalculates its boundary from the current, outer boundaries of all the parcels belonging to it. There is no need to set an active record.

[MarkWasdahl1]

Build Extent worked as you wrote. Thank you for the solution.

[VAAVAA]

thx for your information

[AmirBar-Maor]

@MarkWasdahl1 

Generating the record geometry can be expensive in terms of performance. Imagine there are 1999 parcels associated with the record, and you only moved one parcel.

So not all operations will trigger a record geometry update (Move, Align Parcels, ...) - in those cases @pt_instructor  is correct, simply use Build Active or Build Extent.

For performance optimization, you can also consider reducing the maximum number of parcels from 2000 to a lower value.

[MarkWasdahl1]

I appreciate the information on performance optimization. However, in my industry and location, it is rare to reach even 100 parcels in a highway project (record).

[AmirBar-Maor]

@MarkWasdahl1 

In that case you can lower that number:

1. In the Catalog pane, right-click on the parcel fabric
2. Open Properties 
3. In the General tab, expand 'Parcel Fabric' and type the new value.

A 100 parcels that are very large, along a natural boundary, can also take their toll.
Why do we have a geometry for the record?  It is designed to be the 'footprint' of the record, allowing users to easily understand which legal transaction took place in a given location. It is also used to navigate to the work area.
Do you have other use cases for the use of the record's geometry?

[MarkWasdahl1]

No other use cases yet. At this point, we are still building the database and haven't had other users interact with requests.