[FIX] point_of_sale: align with backend fp mapping #27825
Conversation
There was a problem hiding this comment.
Although I agree this is necessary, that remains an improvement, not a bug. The POS has been evolving slower than the other modules for the last 4 years, and there are behaviors available in SO/Invoice which are not available in the POS. This is expected, and hopefully the gap will be filled for v13.
|
My 2 cents on this: there are a lot of localizations that need to map several taxes from one source tax, so if you don't put this patch, v11 POS won't be usable for that countries, so although an improvement, it's a needed improvement, and it won't modify any behavior, but add a needed one. |
switch87
force-pushed
the
11.0-pos-fp-mapping-gpe
branch
2 times, most recently
from
bb12859
to
4608715
Compare
The backend allows to map one source tax to various target taxes. The POS diverged from this behaviour. This commit alignes the behaviours and lets the point of sale handle mapping to multiple taxes the same way the backend does. backport of pr odoo#26415 to 11.0 [IMP] account: add fp2m unit test [ADD] point_of_sale: js test for 2m fp
switch87
force-pushed
the
11.0-pos-fp-mapping-gpe
branch
from
4608715
to
0a460c2
Compare
|
I am not in favour of backporting this as well. As said on the ticket, it was not supported so far. |
|
oke, I close this pr 👍 |
|
OK, you're right. Then I suppose this should be added as extra module for versions lower than 12.0 for those that need them. We did something similar with pricelists in the module https://github.com/OCA/pos/tree/10.0/pos_pricelist. |
The backend allows to map one source tax to various target taxes. The POS
diverged from this behaviour.
This commit alignes the behaviours and lets the point of sale handle mapping
to multiple taxes the same way the backend does.
backport of pr #26415 to 11.0
resolves ticket 1889884