[6.1][7.0][trunk]Pricelist doesn't take category depth into account

[Yann Papouin]

Attached is a proposal that fix this issue

eg: If you create two rules:

- Apply a discount of 25% on products in category A with sequence 5
- Apply a discount of 50% on products in category B (where B is a child of A) with sequence 5

Depending on the order of these two lines, your product could have a discount of 25% OR 50% (that's a random order from postgresql)

The sequence number (the only way to make priority) is not usable here as you have to manually link the sequence number with the category depth !!! That's impossible to do when you have 6 and more levels of category.

In my patch, the category depth is first computed then used in the result order

[Amit Bhavsar (Open ERP) (amb-openerp)]

Hello Yaan,

I have checked your Issue with latest revision. But It's seems fine. That's why I have attached screen cast for your reference. so would you please check It and notify us where you have faced the problem.

Thanks and waiting for your reply!

[Yann Papouin (yann-papouin)]

Please see my demo:
I've done exactly like you, except that in a second part, I'm switching pricelist item content:

Before:
RULE 1 : Sequence 5 - Discount 25% on CatA
RULE 2 : Sequence 5 - Discount 50% on CatB

After (by editing content):
RULE 1 : Sequence 5 - Discount 50% on CatB
RULE 2 : Sequence 5 - Discount 25% on CatA

As you can see the result is not the same at all !!!

[Amit Parik (amit-parik)]

Hello Yann.

Thanks for the video and detailed explanation!

Faced the same problem at my end.

Thank you!