Skip to main content
Solved

Attribute comparison

  • Jul 18, 2025 10:33 PM UTC
  • 5 replies
  • 243 views

navid.fotovaty
Supporter
Forum|alt.badge.img+4

Hey everyone, I hope I am just missing a very obvious point here. 

I am trying to compare two SQL input data sources

One with these columns

And the other with these columns

 

The customer and account number combination is going to be my primary key. I need to extract the email addresses of customers based on that combination. 

I have tried the feature merger which seemed to be the obvious solution, but I am not getting any matches?

Any idea where I am going wrong? 

Best answer by takashi

I think it would be a good solution to add another unique ID column as join key to the two input tables, if possible.

View original
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

takashi
Celebrity
  • Jul 19, 2025 12:18 PM UTC

Hi ​@navid.fotovaty ,

I think FeatureMerger or FeatureJoiner is a way to go, but it's hard to say what is wrong unless you would clarify specifically how you are using FeatureMerger in your workspace.


navid.fotovaty
Supporter
Forum|alt.badge.img+4

Hi Takashi, 
Here you go 

 

and this is the result
 

 


takashi
Celebrity
  • Jul 24, 2025 3:30 PM UTC

The fme_rejection_code EXTRA_REFERENCEE_FEATURE shown in your result table indicates that there were supplier feature with duplicate join key - pair of C_ACCOUNT and C_CUSTOMER. How to resolve this would depend on how you would like to treat supplier features with an identical key.


navid.fotovaty
Supporter
Forum|alt.badge.img+4

Hi Takashi, 

I would need to allow for duplicate to exist, is that possible? I can introduce another column with a unique identifier if needed. 


takashi
Celebrity
  • Best Answer
  • Jul 29, 2025 12:39 AM UTC

I think it would be a good solution to add another unique ID column as join key to the two input tables, if possible.