Problems on imports where CSV header has duplicate column names for product and variation

Created on 18 June 2024, 3 months ago
Updated 19 June 2024, 3 months ago

Problem/Motivation

It seems like we can create a situation whereby if there is a field that is present on both the product and the variation then only the variation field gets used and the product one gets skipped.

For example if you have a field_image on products and variations we get errors after parsing the upload saying that the field is empty using default - and if we continue we see values populated for the variation but not the product.

I wonder if it makes sense to add a unique identify to product and variation column headers?

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report
Status

Closed: duplicate

Version

1.0

Component

Code

Created by

🇳🇿New Zealand luke.stewart

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @luke.stewart
  • 🇳🇿New Zealand luke.stewart

    It seems like we can add a third parameter to formatFieldDefinition that defines whether we are calling with a variation or not then we get all fields for product and variations present although weirdly weight is now included after the variation fields for a product.

  • Status changed to Closed: duplicate 3 months ago
  • 🇳🇿New Zealand luke.stewart

    Closing as address this in 3455205

Production build 0.71.5 2024