How to keep duplicates when joining two tables?

Hello! I am trying to join two tables using joiner node. I have seen previous videos where in configuration of Joiner node you could decide what to do with duplicates, but I dont see it anymore. Could you please help with advice how to join two tables and keep create duplicate lines if there are more then one match? Currently joiner node is matching only with the first.

Hi Jurgis,

and welcome to the forum.
Are you sure that you really mean the joiner node? I cannot remember this option in this node.

But in the value lookup node there’s this option:

2 Likes

Hi @JurgisEglitis , the joiner node will actually always generate a joined row for every matching set of rows, and usually if you think it is only matching on one row when it should be matching multiple rows it is because the data isn’t actually quite as you think.

For example it might be that one data item contains spaces which aren’t apparent when being inspected in the table viewer.

If you could upload a small sample of data in a workflow that can demonstrate the issue you are seeing, it would be easier to give more specific help.

2 Likes

Hello and thank for help already. Let me first then go back and explain what I want to archieve and lets start from there. I have from a system contract with discounts from specific products and I want to create a table which would say what should be a discount for a Customer/SKU pair in each of the months in 2025 and 2026.
What I have built is a workflow that matches the SKU/Customer pair but it only gives me the first dicount from discount table and not all of them. What I want (and dont know how to do :frowning: ) is to match this pair with all of the discounts possible and then filter for the latest discount where discount (valid from) date is less or equal to data in file GPS data for the same customer/SKU pair. Altough maybe there is different (easier ) approach?

GPS data.xlsx (12.8 KB)

Agreement_List.xlsx (3.9 KB)

OID GPS.knwf (103.6 KB)

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.