nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Parcel Fabric Workflow - Selected parcels are not contiguous

MichelleHoisington

I received an unexpected message using the parcel workflow in the parcel fabric. There are two parcels that are connected to each other. I wanted to use the Parcel Workflow to complete a parcel update (Parcel Split: Parent Parcel or Boundary Line Adjustment). I selected the Parcel Parent, but received an error message when I proceeded to the next step. The message read, "the group of selected parcels are not contiguous." These parcels are joined correctly with minor residual errors. I tried to possibly fix this message by 'regenerate the fabric', 'merge courses', rejoined each parcel, unjoined each parcel (separately) and then joined. Nothing seemed to work. Any idea?

I am aware of a work around - which is to bring in an XML file and mark the original parcels as historic.

Find more posts tagged with

Accepted answers

MichelleHoisington

I have received an answer from ESRI Customer Support. In the case of these two parcels, the only links connecting them are at line points, not parcel points. They are not connected for purposes of construction. The workflows use the Construct from Parent command, which requires true network connectivity (using Parcel Points) of the parcel being updated.

To work around this restriction, users can either join an XML and mark the original parcels as 'Historic' OR select one or more parcel that does not share a parcel point with each of the parcels of interest, and run the workflow. This should allow the construct from Parent operation to succeed.

All comments

MichelleHoisington

Jeff,

Yes, I can use a different method to complete this parcel update. I am able to bring in an XML file. Join using the ‘Append to File’. Select the two ‘Voided’ parcels and mark them as Historic. This works.

All parcels in Nevada County, CA are in the Parcel Fabric. I ran the Parcel Error report and did not find any errors on these two parcels.

I submitted an ESRI case (01788610). Moving forward; I may not have an XML file and would like to rely on the Parcel Workflow. Since the parcel workflow did not work after rejoining the parcels; I suspect it may be a bug.

JeffWard

Have you tried it outside of a workflow?

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.