Latest Contributions by ChristalHigdon_USFS

This "fix" disrupts a long-standing workflow that we rely on for automated Parcel Fabric builds between Alaska and CONUS with different projections. We used this tool as described in the documentation, to change an incorrectly applied spatial reference on a BLANK dataset. There is no reason to change this behavior, as that's what the tool was advertised to do. Very disappointed in Esri and hope you "unfix" this back to the way it was, and is supposed to be, from an end user perspective (and your own tool documentation).  ... View more

Thank you for this helpful workaround. I will give it a try but generally going to/from XML Workspace Document with a Parcel Fabric dataset doesn't work well, for whatever reason. Worth a try since Esri killed our years-long established and well-working workflow of Define Projection to correct an already defined projection on a dataset.  ... View more

It is not the better way to go in 3.5, as it loses a bunch of our data structure in the parcel fabric dataset: Before Project:   After Project: Even some of the out-of-the-box relationships Esri creates automatically in the Parcel Fabric get lost using the Project Tool. Really kills our workflow and productivity to make this change to the Define Projection tool, with no mention in the release notes, and no working alternative for our use. ... View more

I searched through the 3.5 release notes and saw no mention of this 'loophole fix'. It really throws a wrench in my workflow, using it as described in the Help Docs to correct and incorrectly assigned projection. ... View more

Yes, we use this in a python scripted build process to migrate to Parcel Fabric. We take an empty gdb and change the "incorrect" coordinate system to the correct one after the copy. It is blank of any data but has a complex structure with relationship classes and related stand-alone tables. This is a huge "bug" from my perspective and a blocker for going to 3.5, which we need for the enhanced attribute rule functionality. The "proper" way to change the projection is to use the Project tool, which leaves behind much of our data. Maybe that is the "bug" in 3.5. I am trying to open an Esri case on this myself but have to go through the proper channels in my organization.  GDB before using Project, with 'incorrect' coordinate system: After using the Project tool to 'correct' the coordinate system: Some of the relationship classes made it through, some did not - even the out of the box relationships inherently created by creating the Parcel Fabric geodatabase. The related tables also did not come through. ... View more

We use the DefineProjection tool extensively in arcpy for a scripted process that we re-run during development and migration into ArcGIS Parcel Fabric. In prior versions (3.4 and earlier) there were no issues. We have Pro 3.5.0 and all of a sudden I am getting an error ("ERROR 000146: Cannot alter the spatial reference"), in both arcpy and Pro/UI Toolbox for Define Projection. I am trying to open an Esri case because this seems like a bug. I think it should still run with warning as it always has if there is already a projection defined. There is no way to set Unknown spatial reference, so what if you make a mistake, or are conveniently using it to set up a new gdb that does not have any data in it yet?  ... View more

I am getting the same error, Postgres SDE database. I would like to echo this bug should be fixed! ... View more

We are also missing the automatic versioned views now that we're in branch versioning as a requirement for multi-user editing in Parcel Fabric. We have an established reporting and publication process that takes data (via SQL queries directly on the database tables) and populates a new schema where data is combined and normalized. This would not be used for editing, but is quite a lengthy and complex process for our legal land ownership and survey parcels for an entire government land management agency. ... View more

I found a similar tool reference in the Pro Offline Help. Can something like this be made available online? (Or if it is, does anyone have a link?) I wasn't able to edit my original post. 😕 Thank you! ... View more

There used to be a lookup page that listed all error and warnings by ID. https://resources.arcgis.com/en/help/main/10.2/index.html#//018n00000002000000 We really need something like this in the Pro documentation, updated for any new tool error and warning messages, so we can look them up by ID, or browse through them to find the message_id to use in AddIDMessage in arcpy.  It is unacceptable to say, "you have to do a bit of research" when no where in the online help for tools are the messages listed by ID referencing the six digit number.  ... View more

@SSWoodward 🎉 Hooray! Thank you for the update. 🎉 ... View more

Thanks @AmirBar-Maor that does make sense. My request still stands that if we want to alter the feature classes AND the parcel type name property, I would like the parcel type name property to be exposed for update, either through the Associated Data parameter or a Parcel Toolset (maybe under Administrative?), so I could change it without having to open Pro and do it manually since our entire process is automated using arcpy. That's great they are independent but please expose it so I can change it in a similar manner as the feature class names that participate in the Parcel Fabric. ... View more

Hi @AmirBar-Maor thanks for taking a look. The background provided was to illustrate our overall process. We have a base file geodatabase where the parcel fabric is created and we copy those for the individual contiguous 48 states for processing our large amount of complex data in smaller chunks. That is all well and good and have no issues putting them back together again. The issue is copying that base parcel fabric geodatabase for Alaska, which has some differences and will remain separate from CONUS data. We want the same structure with additional fields, tables, relationship classes, but need to rename the dataset, parcel fabric, parcel type feature classes, and relationship classes because they will ultimately live in the same enterprise geodatabase and be branch versioned and published for multi-user editing.  So the issue is: We are successful at copying the CONUS Feature Dataset and renaming what we need to with the associated data mapping for Alaska, however it does not include the Parcel Type Names in the Properties of the Parcel Fabric as a parameter in the associated data string. We feel like the Parcel Type names property should match the parcel type feature class names as it does out of the box when created (see screenshot in original post for example of how it does not match after Copy). So if I then go in and programmatically list (arcpy.Describe on the parcel fabric) it will not return the parcel type names that match the feature classes I was able to rename in the Copy associated data mapping, and I would like it to. If the Copy tool's associated data parameter allows me to change the names of all of the items, including the parcel fabric controller, it should include the Parcel Type names.   ... View more