Hello,
I've been having some trouble using the updated append tool since upgrading to ArcPro 3.2. So I have a feature class (A) that I am migrating to a new feature class (B). A has global IDs enabled, which are required for photo attachments and a related table, and so B feature class must have them enabled as well. I set up Feature Class B and enabled Global IDs.
Okay, so now when I go to append features from A and use the field mapper, GlobalID is one of the mappable field. If I run the append by filling out the GlobalID field, the correct Global ID does not get written in to dataset B - it's just a new GlobalID
I discovered this after my initial workflow failed: I went into the environment settings and selected Preserve GlobalIDs and then left the field map option blank. But that results in the Global ID of feature class B being written as 000-...
Which, if I'm appending more than one feature, will fail on the second feature because it's trying to write the same value to all the records.
What am I missing? Prior to 3.2 I was able to do work like this with no issues at all.
Accepted Solutions
Absolutely! I will illustrate with pictures:
Attempt 1: I use the field mapper to make sure that the GlobalID from my input dataset is being written into the GlobalID of my Target Dataset. I leave the environment setting "Preserve Global IDs" unchecked:
When I do that, you can see that the GlobalID is not actually written in correctly:
Attempt 2: As above, except this time in addition to matching GlobalID from the Input to GlobalID from the Target, I also make sure the environment setting is checked on too:
The result is now what we're looking for, the Global IDs are written in correctly.
Absolutely! I will illustrate with pictures:
Attempt 1: I use the field mapper to make sure that the GlobalID from my input dataset is being written into the GlobalID of my Target Dataset. I leave the environment setting "Preserve Global IDs" unchecked:
When I do that, you can see that the GlobalID is not actually written in correctly:
Attempt 2: As above, except this time in addition to matching GlobalID from the Input to GlobalID from the Target, I also make sure the environment setting is checked on too:
The result is now what we're looking for, the Global IDs are written in correctly.
