CSV Import security issues with resolveForeign when key is duplicated on foreign table
Description
When trying to import records in a table like GL Journal with User1_ID configured for example as a Cost Center we get some problems like we can see at attached images.
Account_ID and User1_ID columns are FK from C_ElementValue table, then when we have same values like 11100 for a Account and for a Cost Center, the importer returns the first, causing a wrong data generation.
As a fast workaround to avoid users doing mistakes, i'm attaching a patch that count the results and throws an exception instead of wiring the wrong ID to the imported field.
Thanks , committed a different patch covering the case when System and Tenant has the same resolved value, also, instead of throwing an exception is written in the log file.
Major
When trying to import records in a table like GL Journal with User1_ID configured for example as a Cost Center we get some problems like we can see at attached images.
Account_ID and User1_ID columns are FK from C_ElementValue table, then when we have same values like 11100 for a Account and for a Cost Center, the importer returns the first, causing a wrong data generation.
As a fast workaround to avoid users doing mistakes, i'm attaching a patch that count the results and throws an exception instead of wiring the wrong ID to the imported field.
a better solution should be implemented.