Hi Harmen,
You used the right approach.
If the Suppliers are output through the Unreferenced port, the ID's must be different (trailing spaces?).
Use the Inspector transformer on the output ports of the FeatureMerger to check.
Erik Jan
I agree with erik_jan about using the Inspector to check your data.
If you need to preserve all the suppliers for every requestor, also look into the "Generate list" option in the FeatureMerger. If you specify a list name, every merged feature will contain a list with one element for each matching supplier.
Thank you @erik_jan and @david_r for your reply!
There are no trailing spaces.
The "Generate list" option is not suitable for me.
- independently both suppliers merge correctly with the requestor
- I created different names for both ID attribute fields
- ID value is the name of the file I am using as a string
Still doesn't work...
Thank you @erik_jan and @david_r for your reply!
There are no trailing spaces.
The "Generate list" option is not suitable for me.
- independently both suppliers merge correctly with the requestor
- I created different names for both ID attribute fields
- ID value is the name of the file I am using as a string
Still doesn't work...
Can you post a sample workspace here (e.g. using Creators rather than actual data) that demonstrates this issue?
Hi Harmen,
Could switching the Requestors and Supliers work.
In that case each Requestor will join with one Supplier (sometimes the same).
Erik Jan
sample.fmw
Sample workbench attached
@erik jan : your suggestion doesn't work either...
In the FeatureMerger, the "Join on" settings are evalued together as AND, not as OR.
You have one supplier that contains ID_DATE and another that contains ID_Z, but no supplier that contains both, that is why they won't match. I recommend you rename e.g. ID_Z to ID_DATE and then only join on "ID_XY = ID_DATE"
The FeatureMerger has two join clauses.
They will act as an AND boolean.
Not Supplier fits both clauses and therefor will not merge.
You need tow separate FeatureMergers or have the same joining attribute name on both Suppliers.
Why not joining on fme_basename?
Both answers will do!
Thank you @erik_jan and @david_r !
Most of the time the answers within FME are too obvious ;-)
Hi @h1, I think conditional value setting for the Join On parameter could also be used in your case. e.g.
Hi @h1, I think conditional value setting for the Join On parameter could also be used in your case. e.g.
Thank you @takashi for your reply.