[13.0][FIX] fix migration with product with twice the same attribute#2488
[13.0][FIX] fix migration with product with twice the same attribute#2488sebastienbeau wants to merge 1 commit into
Conversation
8cd8f6c to
92cb03d
Compare
|
Hi, @sebastienbeau. |
|
Yeah, that my same question: how do you get to that incorrect configuration? |
|
In my case, the data was coming from version 8, so it was possible in V8. |
|
If two product variants have the same attributes, then we should merge those variants into one record. |
|
As I commented before about merging variants, I have done a PR with that approach, which I think is better. Please, could you check #2513? |
|
HI, @sebastienbeau. Could you confirm that #2513 fixed or not your problem? |
|
@sebastienbeau Any news? |
|
There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days. |
Description of the issue/feature this PR addresses:
For some product you can have twice the same attribute
Example you have a bi-color product you can set
attribute line 1: color => white, black, yellow
attribute line 2: color => green, blue, yellow
if both attribute line have same value for the color it's a litle more
complexe to fill the value as you have two product_template_attribute_value
with the same attribute_value "yellow"
Current behavior before PR:
Migration fail
Desired behavior after PR is merged:
Migration work
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr