Hi there,
Importing PIM data via the Actions->Import functionality makes an educated guess on the field mappings. Can this be extended to the selection of primary keys? Or a default setting.
For example, the following import file: (very bare-bones)
- The combination of ProductId, ProductVariantId and ProductLanguageId makes the PK here, this is the most used, default PK in the PIM. It might get spicy when ProductNumber and/or ProductEAN is in the file aswel. But if Id/VariantId/LanguageID is present, chances are high it is used as PK.
The goal is to show the export/import mechanism to the client, and I want to avoid manual actions by automating a lot of configuration. The client does not need to know that assigning the PK is necessary, they just need to upload the file and import the data.
Thank you for considering this, kind regards!
Barend Mosch, Bluedesk
Hi there,
Importing PIM data via the Actions->Import functionality makes an educated guess on the field mappings. Can this be extended to the selection of primary keys? Or a default setting.
For example, the following import file: (very bare-bones)
The goal is to show the export/import mechanism to the client, and I want to avoid manual actions by automating a lot of configuration. The client does not need to know that assigning the PK is necessary, they just need to upload the file and import the data.
Thank you for considering this, kind regards!
Barend Mosch, Bluedesk