Insert into multiples tables and manage foreign keys

There are several ways of doing this, but personally I like using multiple FeatureWriters and chain them with a FeatureMerger set on a dummy merge criteria (e.g. 1 = 1).

The pattern looks like this:

This will ensure that the Master features have all been written and committed before the Detail features.

Here's also an article from Safe with some alternative strategies:

https://knowledge.safe.com/articles/44622/working-with-foreign-keys-writing-database-tables.html

Hi @david_r,

Thanks for your solution.

Thanks

This is what I had in mind, simply typing the same hard-coded value in the Requestor and Suplier join criteria:

This would be what's often called an "unconditional merge", meaning that every requestor is joined with every supplier.

I'll try it and I'll let you know if it is working for me !

Hi @david_r,

I've finally been able to find some time to test your solution.

Do you have any idea on what is wrong ?

I may have found a solution by activating "Process Duplicate Suppliers" and set Build Aggregates and the just after add a Deaggregator process.

The message means that you have more than one supplier for a requestor in the FeatureMerger. You can try enabling the option "Process duplicate suppliers" in the FeatureMerger. Try leaving the associated options as-is.