Skip to main content
Solved

featurejoiner automatic mode (form vs flow)

  • June 6, 2025
  • 5 replies
  • 66 views
fdw
Contributor
Forum|alt.badge.img+6

I'm joining two features in a featurejoiner in Form (2024.2.1). In AttributeManager one is a uint8, the other is varchar(200).

Both contain value '2’.

In Form these featues are joined with the joiner set to Automatic mode. When the workspace is published to Flow (also 2024.2.1) suddenly they are not joined anymore. I would expect the Automatic mode to work the same way in Form as in Flow. Especially since we run the same version in both environments

 

I can't find any registered bugs on this issue. Has anyone else encountered this?

Best answer by takashi

Hi ​@fdw ,

I was able to reproduce the issue with your workspace, FME Flow 2025.0.2.

I have inserted another Logger immediately after the Creator, select two classes, and run. The Logger logged:

Attribute(string: UTF-8) : `CLASSES' has value `"6"."2"'

I think it’s a kind of bug, would recommend you to submmit this case to Safe support.

https://support.safe.com/hc/en-us/p/Support

 

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.

5 replies

virtualcitymatt
Celebrity
Forum|alt.badge.img+47

Yeah weird, in the end this definitely shouldn’t be happening - for the most part I think FME usually ignores types except for readers and writers. 

Are you 100% sure that it’s the join that’s the issue?

I would double check by throwing down some loggers before the FeatureJoiner to make sure that the data are actually there. 

If you can confirm in your logs the values are the same then that would be really weird. Does the behaviour change if you switch from Automatic mode to something else?

fdw
fdw
Contributor
Forum|alt.badge.img+6
  • fdwContributor
  • Author
  • Contributor
  • June 6, 2025

Thanks Matt,

 

I added loggers and ran in Form. I get this (changed value 2 to 6, doesn't matter):

 

2025-06-06 14:02:17|   2.4|  0.0|INFORM|Logger: Choice Class is: 6
 

When published to Flow is logs:

 

2025-6-6 14:00:16 | Logger: Choice Class is: "6"

 

So it had quotes around it and thus doesn't join in the featureJoiner/Merger.

I put a stringreplacer between to remove the double quotes on both sides and then it does work. Personally I really don't understand this behavior. Could this be caused by different settings on Flow? Kinda new to that.

 

I added a debugging workspace and las file for testing.

1 Attachments
takashi
Celebrity
  • takashiCelebrity
  • Best Answer
  • June 6, 2025

Hi ​@fdw ,

I was able to reproduce the issue with your workspace, FME Flow 2025.0.2.

I have inserted another Logger immediately after the Creator, select two classes, and run. The Logger logged:

Attribute(string: UTF-8) : `CLASSES' has value `"6"."2"'

I think it’s a kind of bug, would recommend you to submmit this case to Safe support.

https://support.safe.com/hc/en-us/p/Support

 

Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
fdw
fdw
Contributor
Forum|alt.badge.img+6
  • fdwContributor
  • Author
  • Contributor
  • June 6, 2025

Thanks ​@takashi 

 

I will send in a support ticket.

 

timatsafe
Safer
Forum|alt.badge.img+4
  • timatsafeSafer
  • Safer
  • June 18, 2025

This does appear to be a bug. I've filed a ticket with our development team (FMEFLOW-25712). The StringReplacer as you mentioned should work as a workaround for the time being.

takashi

Community Stats

32,129
Posts
121,967
Replies
39,779
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.