+23I want to reopen an old case that is still of interest:
Geodatabase Error (-2147219884): The Field already exists (safe.com)
My error isn't of the "reserved word" origin nor related to having "shape" as an attribute name.
When trying to dynamically create tables in a GDB I get the "Field already exists" error.
If I send each feature type to a corresponding table it runs.
For what I am trying to do, connecting readers and writers by hand is not worth it.
Can someone from Safe comment on this?
Best answer by nielsgerrits
I have attached a screenshot of the writer and the workspace.
I can reproduce your issue, but when using FeatureReader/FeatureWriter instead of classic Reader/Writer it works, but with a bunch of warnings.
+65How are you passing the schema through to the writers? Can you shouw us the configuration of your writer(s) in the first example?
+23How are you passing the schema through to the writers? Can you shouw us the configuration of your writer(s) in the first example?
I have attached a screenshot of the writer and the workspace.
+62I have attached a screenshot of the writer and the workspace.
I can reproduce your issue, but when using FeatureReader/FeatureWriter instead of classic Reader/Writer it works, but with a bunch of warnings.
+7I think the source of this problem might be the objectid field. If a geodatabase is the schema source then the dynamic writer tries to add the objectid field to the output but in fact this field is automatically created whenever a geodatabase feature class is created. I personally solved it in the destination feature types using the parameter "Attributes to Remove" and entering objectid
