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 "Layer Not Editable" when moving points but all fabric layers are editable?

CoreyMetz

Hey All - I've been editing our tax parcels in Pro (version 2.7 now) with parcel fabric for about 3 months now and one of my favorite workflow improvements has been the ability to just click and move points to make small adjustments to my parcels. It worked great in the beginning, then it started showing this error every now and again when I tried to move a point:

No worries, because I would just close out of Pro, reopen my project, and it would work again. I figured it was a problem with a lock file on one of the fabric layers or something. A few days ago though it started popping up with that message every time I tried moving a point and my old trick or restarting Pro doesn't work anymore.

Everything is checked for editing and the Status dialog doesn't point out anything obvious to me either:

I'm also working in just a file geodatabase so I can't imagine there's any other permission issues occurring. Has anyone else encountered something like this?

Finde mehr Beiträge mit dem Tag

Geodatabase

Desktop

Accepted answers

CoreyMetz

Solved.

My project (.aprx) file ended up being the problem. I tend to keep my project open with multiple tabs since I have 2 different layout and 2 editing maps (one with the topology and one with non-topology layers and my annotations). However, opening the fabric in a brand new project allowed the points to be moved and the topology to update as intended with the fabric.

So in my original project I was able to "reset" it by:

Closing ALL tabs/views except Catalog
Saving the project and closing Arcgis Pro
Re-opening Pro
Opening only the map that contains the fabric

I'm now able to edit points again. My working theory is that one of my layouts contains the map that has my fabric topology in it and "activating" the map in that layout may be conflicting with editing the map itself elsewhere in my project.

All comments

DanPatterson

This sounds related to...

Layer is not editable error message but the layer ... - GeoNet, The Esri Community

The recommendation there might be appropriate

CoreyMetz

My file is in the hands of ESRI's parcel fabric team so I will provide an update here once everything is resolved.

CoreyMetz

Solved.

So in my original project I was able to "reset" it by:

Closing ALL tabs/views except Catalog
Saving the project and closing Arcgis Pro
Re-opening Pro
Opening only the map that contains the fabric

AmirBar-Maor

Hello all,

We are trying to reproduce this issue to no avail.

The problem is that it seems to go away once you close and reopen ArcGIS Pro, so even if you send the data it does not guarantee that we can reproduce it 😞

If you have a project that consistently exhibits this error we would love to get it so we can fix it.

JasonBessert

We encounter this kind of error all the time and I think it has to do with having project files with layer configurations that grow stagnant because the maps/project files were created in earlier releases.

Our solution when this "Layer is not editable" error occurs is to add your parcel fabric freshly to a brand new map. You an either edit the parcel fabric out of that new map, or, if you don't want to abandon your map where the error is returning because you like the customizing you have done with your table of contents (layer colors, labeling configurations, etc) - take the topology layer from the freshly-added map and use it to replace the topology layer in the map giving you the problems by way of copy/paste delete. Save and re-open the project file, and the error should not occur when you attempt to move parcel fabric points.

I can't speak for ESRI but it seems like when there are Pro version updates, there are some very subtle configurations that update to certain layers behind the scenes and .aprx files that have been in-use for editing for long periods of time fall victim to these kind of errors when some of the most important layers kind of need a reboot by way of adding the fabric from the controller object in Catalog to a new map.

MDB_GIS

Thank you for sharing this solution. I have been recreating my map from scratch when it happens, despite how much it pains me to do it. I am going to make sure to try the trick with the topology layer next time.

JasonBessert

Let me warn you that it works some times, and sometimes not. I thought it had something to do with stagnation on one layer (points/topology) over the course of product updates but it could be a combination of them. I typically don't like to re-do my maps because I spend a lot of time configuring layers with color and symbologies, coupled with labeling expressions and scale constraints, etc. This typicall occurs over my fabric type group layers (lines and polygons). Those can be static. But I've found that when behavior degrades with Pro's parceling tools, occasionally layers that store Topology, Records, Points, Anchor Points & Links have to be re-introduced from freshly added maps. I also had to learn the hard way that Anchor Points and Links belong in the default database as thats where the alignment tool builds them in. I made the mistake of storing those datasets in the same databases as my fabrics, but those layers, representing temporary features belong in the database and need re-spawning over time as well. Good luck.

Nimm an der Diskussion teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

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