I am trying to use a GUID field to update records in an ArcSDE Writer. It seems to work perfectly when using an integer field for the Update Key, but when I use a field with type=guid the update does not go through.
Solved
Can you do an UPDATE fme_db_operation using a field of type GUID as the Update Key?
Best answer by nathanatsafe
Different versions of FME treat GUIDs slightly differently, including possibly adding or dropping the surrounding { } characters, which can confuse a writer or a transformer like the ChangeDetector. The behaviour also varies slightly between File GDB and ArcSDE GDB. Close inspection of the attribute before the writer, as @david_r suggested, should reveal discrepancies if this is the root issue. Such an issue can be fixed with an AttributeManager.
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
Which version of FME are you using? Older versions of FME didn't fully support GUID fields, but I believe FME 2016 and later should be able to do it.
I also suggest inspecting the contents of the GUID attribute just before the writer to make sure it contains a valid value.
+16- Safer
Using FME 2017.0.
The GUID looks to be a valid value.
+9- Safer
- Best Answer
Different versions of FME treat GUIDs slightly differently, including possibly adding or dropping the surrounding { } characters, which can confuse a writer or a transformer like the ChangeDetector. The behaviour also varies slightly between File GDB and ArcSDE GDB. Close inspection of the attribute before the writer, as @david_r suggested, should reveal discrepancies if this is the root issue. Such an issue can be fixed with an AttributeManager.