I believe this is a bug because it used to work fine on v16. but maybe im doing something wrong
My specific situation is, uploading a file into the product import form I have a few items which contain new attribute values. the attribute and values fields I am trying to use here are '
Product Attributes / Attribute' and 'Product Attributes / Values'
I click test, and as expected a red box appears allowing me to choose what should happen when a value cannot be matched. I select "Create new values"
then upon import, I receive the same blocking error, even though create new values is already selected. in order to move forward I have to go add the attribute values into the color attribute.
Am I using the wrong field(s) for this functionality?
Ive since discovered more information about this issue, here's a full report:
Environment:
Odoo version: 17
Clean Install no added modules
Steps to Reproduce:
-Prepare a CSV file for product import with columns for "product attributes / attribute" and "product attributes / values".
-Go to the product import interface in Odoo.
-Upload the CSV file and map the columns appropriately.
-Set the system to create non-existent attributes during the import. said attributes should be instant variant creating attributes
-Initiate the import process.
Expected Result:
-The system should create non-existent attributes and values specified in the CSV.
-Product variants should be automatically created based on the attributes.
Actual Result:
The import process fails with an error due to non-existent attribute values.
After manually creating attributes, the products are created but variants are not automatically generated.
In the product form, the 'Configure' option next to attribute lists shows an empty table despite having several attribute values listed.
Workaround:
Deleting the products and re-uploading the CSV with the attribute values field renamed to "attribute_line_ids/value_ids" (still mapped to the same field "Product Attributes / Values") surprisingly works and imports correctly.
There seems to be an inconsistency in how the system handles the mapping of attribute fields during the import process.