Skip to main content
Solved

DatabaseJoiner looses curly brackets in joined attribute

  • February 22, 2024
  • 2 replies
  • 37 views

reservoirdog
Supporter
Forum|alt.badge.img+12

I am using FME(R) 2022.1.3.0 (20220928 - Build 22630)

I noticed while working with ArcGIS Data (FileGeodatabase), that when I use
the “DatabaseJoiner” Transformer to join attributes with curly brackets inside its values, the curly brackets are gone after joining. 
e.g. Original Attribute value: {12C300A2-64C3-4494-A1E2-430CC5C5C7A9}
joined value by DatabaseJoiner: 12C300A2-64C3-4494-A1E2-430CC5C5C7A9

It this a known behaviour? Why would it get rid of the curly brackets? 
Anything to do against it?

Best answer by hkingsbury

I just tried in 2023.1 and its retaining the curly brackets. Two things I can think of

  1. It was a bug that has been fixed
  2. I put the GUID in a text field, the behavior might be different if it is a GlobalID/GUID type?

To rectify it, you can use the StringConcatenator to add the opening and closing squiggly brackets

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.

2 replies

hkingsbury
Celebrity
Forum|alt.badge.img+65
  • Celebrity
  • Best Answer
  • February 22, 2024

I just tried in 2023.1 and its retaining the curly brackets. Two things I can think of

  1. It was a bug that has been fixed
  2. I put the GUID in a text field, the behavior might be different if it is a GlobalID/GUID type?

To rectify it, you can use the StringConcatenator to add the opening and closing squiggly brackets


reservoirdog
Supporter
Forum|alt.badge.img+12
  • Author
  • Supporter
  • February 23, 2024

Thanks for your reply.
Yes, I fixed it using the StringConcatenator, but I found it a weird behaviour.
Yes, the source attribute is a GlobalID datatype, maybe it behaves differently.
At the moment I cannot try a newer version of FME, because newer versions removed
the “old” SQLIte (Spatial) writer completely and I am still quite depending on that.
Thanks again for testing this out,