Latest Contributions by Paul_Christensen

Thank you Amir for your response and assitance! Unfortunately it hasn't been consistent in when it occurs. There hasn't really been a specific sequence of edits that results in the error.  I can confirm that closing and reopening pro resolves the issue for the remainder of the day, or the remainder of that pro instance. I have been using Multiple Workspace editing and have never used the Single Workspace option. I have had the Enable and Disable Editing from the Editing Tab setting turned on.  All of my Parcel Fabrics are in single user/editor deployment in a FGDB with no Enterprise infrastructure in place. Lastly, I have experienced this across multiple machines, in multiple organizations, using multiple versions of Pro, multiple versions of the Parcel Fabric, and multiple Parcel Fabric implementations. I created one of the Parcel Fabric versions very early on, shortly after the Pro Parcel Fabric was launched, and it has been upgraded all the way up to the current version over the past several years. I created another Parcel Fabric version just a few weeks ago using Pro 3.2. ... View more

I have experienced the same error, but not related to georeferencing. It typically occurs randomly during boundary edits when I try and Move or Align or similar topology affected edits. I assume one of the topologically related layers gets locked out for some reason. My status window also shows no errors. I just save and restart Pro and everything works again. This happens maybe once a day.   ... View more

The Relationship Classes can't be added to the map by themselves, they operate in the background. You should add the entire Parcel Fabric item to the map instead. If you go to a map layer's properties, there is a "Relates" section that will show the relationships for that layer. ... View more

The Records' GlobalID field should match the Parcels' CreatedByRecord or RetiredByRecord field. That is how each Parcel is linked to a Record.  ... View more

I've had similar experience with Records with large feature counts on all versions since 2020. When I first implemented pro fabric, I had a 7k+ record for parcels with no record. "No Record". Performance was pretty poor in the beginning of pro fabric anyway, but that massive record really slowed it down. Just think, every time you Build Active or do anything with records/validation/fabric workflows, it is probably running through the whole list of related parcels and validating/building each parcel, line, and point related to that record. The smaller the better. I'd see if there is a way to parse down those feature counts a little. I think your performance would noticeably increase.  Side Note; I also experienced a very distinguishable drop in performance with Administrative Boundaries. If I have an annex and create a retired parcel for the entire city limits, tax districts, school districts, and county Parcel Types, that one record is now associated with every single administrative vertex for 4 different Parcel Types over an area of 700 sq miles.  I really like Esri's documentation, blogs, videos, and webinars for Pro Parcel Fabric and I think the team does a really great job listening and addressing issues, but I think some more overall best practices could be laid out somewhere. ... View more

I spoke with a tech rep and ended up with 4 concerns. Build Extent over several small parcels creates a very large and displaced dirty area. The extent built is not "dirty", however a different area of the map is. The area I built is the small red rectangle in the SW area of the screenshot, but the dirty area is nowhere near that area. This only occurred when working in an area encompassed by administrative parcels. If I created a new tax parcel far outside the boundaries, build extent worked as expected and the dirty area only encompassed the area built. When selecting a point that is shared with an administrative boundary, Merge Points locks up UI for minutes at a time and nothing else can be accomplished. This also occurs with very large standard non-admin parcel types. For instance, I have a large lake in my county that has a Zoning polygon. If I select a point that is used by this large polygon, Merge Points locks up.   Align Features does not align admin parcels.  I manually moved several vertices for an admin parcel and a non-admin parcel. I then used align features to bring them back to where they should be. The admin parcel did not align and the non-admin parcel aligned as expected. Using Copy Parcels to export my fabric for upload to technical service, I had one small issue in the output fabric where two parcel vertices were merged and the lines were not. I only discovered this when validating the fabric and an error occurred be because the lines no longer coincided with the polygons. The vertices were within the horizontal tolerances so Clustering shouldn't have affected this. This isn't related to my original posting, it was just a side bug that occurred when working with tech support. The vertices are .016551 apart and the tolerances are .003280.     ... View more

Absolutely, case created. Thank you Amir ... View more

I just experienced an identical behavior from Excel. When my mouse flies past Excel's top window bar, over the last saved status, the "Workbook last saved: just now" popup will display about one second later wherever the mouse is.   This may be a windows "feature" and not necessarily a Pro issue.   ... View more

I agree with rburke, that I wouldn't like to totally disable popups because I do occasionally use them. Just that I would like to see if we can prevent the popups from displaying where they shouldn't. I just tested this again this morning. It originally looked like the popup displayed wherever the mouse stops. However, If I fly over the tool, and then keep the mouse moving, the popup will display about one second later even if the mouse is still moving. Similar to if I just pause over a tool. ... View more

It does seem to be primarily Modify Features that will cause this. It also seems to be easily reproduceable if the tools are unavailable, such as when working with a Layout.  ... View more

I do not. ... View more