Situation: A multi company environment, where there are companies A and B.

Records can be created for different companies, identified via the company field.

When uploading a record via the 'Import from Excel' functionality, the company field can also be uploaded.

In a situation with Company A and B, the 'Import from Excel' functionality can be used to import an Account specifically for company A.

But, next to transactional data, there is also setup data, which are used in lookup field on the transactional tables, such as Customer Group on Account.

It is perfectly possible to setup Customer Groups with the same value (e.g. Customer Group, COM) in both Company A and B. This makes sense because many setup values are valid across companies.

But currently, the 'Import from Excel' functionality cannot cope with this.

When uploading an Account X in Company A with the Customer Group COM, the import fails with the following error: Duplicate reference found for transformation output parameter mapped to: Customer Group Id

This means, that across companies, the same value cannot be used in setup tables, but that each setup value must be made unique, both in the same company (or there is a duplicate error) AND across companies.

This is not something our Clients want to do, understandably.

This would mean, in the example of Customer Groups that our clients should set them up in a way similar to:

• COM_A (= Customer Group 'Commercial' for Company A)
• COM_B (= Customer Group 'Commercial' for Company B)

Suggestion is that the 'Import from Excel' functionality uses the Company value from the record being imported (e.g. Account in Company A), to lookup the respective lookup fields (e.g. Customer Group Id 'COM' in Company A).