Definitely need to be able to preserve existing GlobalID. This is important for key relationships for relationship classes between features and tables.
Page 1 / 1
Can you elaborate on what you're trying to do?
Hi @ganbaatarp: What version of FME are you currently using? As of FME 2019.0, FME supports maintaining GlobalIDs: https://knowledge.safe.com/idea/61583/esri-global-ids.html
Can you elaborate on what you're trying to do?
I apologize in front if I'm stealing this thread.
Facing the same problem, using version 2018 and primary key/foreign key uses GlobalID.
Source: Feature class #1 in ArcSDE database using GlobalID as Pk/Fk in relationsship to attachment table.
Destination: Feature class #2 in ArcSDE database using GlobalID as Pk/Fk in relationsship to attachment table.
When merging features from #1 to #2, the features created in #2 receives a brand new GlobalID, thus losing the relationship.
Should I place my hope in http://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_ReadersWriters/geodatabase/GEODATABASE_SDE_writer.htm?Highlight=globalid
Or is there a solution using GlobalID as Pk/Fk?
Maybe I should set up a workbench visualizing the problem?
I apologize in front if I'm stealing this thread.
Facing the same problem, using version 2018 and primary key/foreign key uses GlobalID.
Source: Feature class #1 in ArcSDE database using GlobalID as Pk/Fk in relationsship to attachment table.
Destination: Feature class #2 in ArcSDE database using GlobalID as Pk/Fk in relationsship to attachment table.
When merging features from #1 to #2, the features created in #2 receives a brand new GlobalID, thus losing the relationship.
Should I place my hope in http://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_ReadersWriters/geodatabase/GEODATABASE_SDE_writer.htm?Highlight=globalid
Or is there a solution using GlobalID as Pk/Fk?
Maybe I should set up a workbench visualizing the problem?
Just got FME 2019, solved all the problems