Generate Unique IDs as GlobalID when appending a FC without GlobalIDs to one with GlobalIDs

[MarkusWall1]

When appending features from a feature class not having a globalID field to one with a globalID field, all the importet features get the same globalID.

It ist impossible to work with this data afterwards, so the features have to be deleted.

At least a warning would be fine, that the origin data has no globalIDs and that they should be generated before appending the features.

[KevinSaavedra]

Hello,

In Pro 3.6, I appended a file gdb input feature class with no globalIDs to a target feature class with globalIDs and the appended features were all assigned new globalIDs. 

I also verified this is the case when the input feature class is in a file gdb and the target is in a SQL Server eGDB.

Could you please list more detail about your case where the same globalID is used for all appended features?

[MarkusWall1]

Hello,

I was able to reproduce it a few times last week, but it's not reproducible now.

What I figured out is, that when the option "preserver GlobalIDs" is set, the GlobalID of all importet objects is the same, but its {00000000-0000-0000-0000-000000000000}

I found an older screenshot from August, where I documented the problem with the same GlobalID after an import.

BR,

Markus

Origin FColder screenshot of appended dataTarget FC

[KevinSaavedra]

This is implemented in Pro 3.7. If the target dataset contains a Global ID field and the input data does not, running Append with the Preserve Global IDs environment set to True will automatically generate new Global ID values for inserted rows.