BoM import with IPN as lookup fails

[gunstr]

In PR #11288 the import session was enhanced to allow alternative lookup fields. I tried that now with importing a BoM file where I do not have the part pk pre-populated and I thought I should be able to map the IPN field in the import file as a lookup for the part IPN in the database.

If I select the IPN column in the import file as the Component database field I can initiate the import but the result is a complete mess. I have checked a few of the items and it seems that if there is pk in the database that corresponds to our IPN (we use numeric IPN only) then it picks the part with that pk rather then the part with the corresponding IPN. And if not it picks the part with the correct IPN.

If I remember correctly from the earlier versions with the "old" UI the lookup could be forced to map IPN in the import file to IPN in the database. However, I cannot figure out how to force such mapping in the 1.3 release - is that even possible?

[SchrodingersGat]

There is currently no option to "override" the FK mapping - so the PK will be preferenced over IPN if it exists.

Adding an option for the user to select a FK field (from a list of supported options) would be a good addition. But currently not possible.

[gunstr]

I saw you are already working on a fix in #12180 . Really appreciated as the current implementation basically means that the values across all lookup fields has to be unique in the database to avoid false matches during the import.