Because you have columns which are the same name, it will cause a conflict resolution.
You can choose what to do here by expanding the Attribute Accumulation section in FeatureMerger
In the event of a conflict, you can use Requester, supplier or prefix supplier.
Alternatively, you can rename the attibute in one of your files before it reaches the FeatureMerger
Because you have columns which are the same name, it will cause a conflict resolution.
You can choose what to do here by expanding the Attribute Accumulation section in FeatureMerger
In the event of a conflict, you can use Requester, supplier or prefix supplier.
Alternatively, you can rename the attibute in one of your files before it reaches the FeatureMerger
Hi @david_whiteside,
Can you perhaps show me what the FeatureMerger is supposed to look like?
I have no idea how I should set up the Requestor / Supplier.
Cheers,
Ed
Because you have columns which are the same name, it will cause a conflict resolution.
You can choose what to do here by expanding the Attribute Accumulation section in FeatureMerger
In the event of a conflict, you can use Requester, supplier or prefix supplier.
Alternatively, you can rename the attibute in one of your files before it reaches the FeatureMerger
If you have your main file going into requester and your abbreviations going into supplier. Then set up the FeatureMerger to look like the attached and try the image below.
featuremerger.jpg
Run the workspace and see if that is giving you what you need.
If you have your main file going into requester and your abbreviations going into supplier. Then set up the FeatureMerger to look like the attached and try the image below.
featuremerger.jpg
Run the workspace and see if that is giving you what you need.
Hi David,
Thanks for the info - I've finally managed to merge the fields using these settings:
Not sure how... but it work! ;-)
Best,
Ed