Global ID exposed for mapping

[ChrisBuscaglia]

• Field mapped into target
• Field not mapped to in target

[previnWong]

Elena will test

[ElenaFernandes]

When loading data from two feature classes in an enterprise gdb, the Global Ids have to match in case or the append data tool will fail. When the Global ID cases match, the tool succeeds and imports the data and Global IDs correctly.

[ChrisBuscaglia]

@previnWong @Elena9170 @MikeMillerGIS Need to hide GlobalID on target when a feature service?

[ElenaFernandes]

Findings

File Gdb Testing (Global ID not mapped)

• Global IDs not preserved in feature class to feature class or table to table
• Global IDs not preserved in feature service to feature class
• Unable to create Source-Target Config File with a feature class as source and table as the target dataset

Enterprise GDB testing (Global ID preserved)

• Global IDs preserved from feature class to feature class
• Global IDs hidden but preserved from feature service in AGOL to feature class in Enterprise gdb
• Unable to create Source-Target Config File when source was a feature class to table or vice versa

[ChrisBuscaglia]

Adding this issue to the next release for hiding the GlobalID when it's a feature service/layer.