Skip to main content
Question

Join 2 tables

  • November 16, 2025
  • 3 replies
  • 38 views

gisgis
Contributor
Forum|alt.badge.img+4

I have a pretty simple problem but I cound not find any solution. I tried feature joiner and added counter so that I have a field in common for bot tables but still didnt work. Attribute manager does like “what I get” which is not really what I want. Any Idea ? 

 

 

3 replies

j.botterill
Influencer
Forum|alt.badge.img+53
  • Influencer
  • November 17, 2025

Have you tried FeatureMerger with the key values of 1 to 1. Inspect what if out of the merged port you get the answer you are looking for. You can always swap the requestor and supplier around. Note the supplier shouldn’t have duplicates typically, the transformer has advanced options on handling such

There is a good webinar from Safe regarding joining  https://www.youtube.com/watch?v=dB3Y_Gtw5Rc


s.jager
Influencer
Forum|alt.badge.img+21
  • Influencer
  • November 17, 2025

From what you show, the Table C “what I get” is correct. There is no common identifier between Table A and Table B, so a full outer join between the two would give you that result.

Why would the single row in Table A only be joined to the first row in Table B? Can you explain? Your screenshot does not give any common data between the two (remember that in a database there is no order in rows in the table, unless you specifically use order by - or a Sorter in FME).

So without a bit more info on what you actually have, and why you want to achieve what you’re looking for, I can’t really suggest anything. The Featuremerger method j.botteril recommends might work, but that also depends on the actual data you have...

Btw: if these are database tables, it’ll save a lot of processing power if you’d join these tables using an SQL Creator (or SQL Executor, or Feature Reader - something that will allow you to execute sql on the database). Let the database do most of the work, I always say...


geomancer
Evangelist
Forum|alt.badge.img+59
  • Evangelist
  • November 17, 2025

Using the FeatureMerger with dummy values, like ​@j.botterill suggests, gives me exactly the results you want (see the attached workspace, built in FME Form 2023.1.1).