Hi Sandy,
You're right. Pigment doesn’t allow you to directly combine two transaction lists within the tool.
I would recommand option 1. Combine both datasets at the source level before loading them into Pigment. That ensures you have a single, clean (and consistent!) transaction list and avoids performance issues.
Option 2 is doable but not scalable and I would not recommand option 3.
If option 1 isn’t possible, don’t forget you can also do List-to-List imports to feed a single Transaction list from multiple sources.
Ahmed
Hey Ahmed 👋
Thank you for your answer!
The list-to-list imports only work when there’s a unique key (Code), which isn’t the case on our side
(see the capture below — the Ref unique is repeated).
Transaction list 1 :

Transaction list 2 :

The issue is that if we try to generate a unique key within Pigment (using a RANK or a concatenation),
we end up losing some transaction lines during the import.
What would you recommend to ensure uniqueness without losing data?
Or do you see a cleaner approach within Pigment that I might have missed ?
Thanks!