-
-
Notifications
You must be signed in to change notification settings - Fork 791
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sync readonly between pricelist and currency #88
Conversation
Addresses OCA#80, see also odoo/odoo#4598. If we have some states in which the pricelist can be changed but the currency is readonly, the currency seems to be changed, but while saving it goes back. The core purchase module probably needs a similar fix.
LGTM, I've tested it. Thanks 👍 |
@lepistone What happens if readonly is not on field in py file but on view in xml file? If it's not possible, I think it would be preferable to link the bug report in the comment (in code). Otherwise as it fixes the issue #80 👍 |
I agree with you @yvaucher, it's probably a bad idea to be able to change the currency to something different from the pricelist currency. Changing that is non-trivial, and changes the design somewhat, so I'm not doing this here. Instead, I added a longer commentary with reference to odoo/odoo#4598 as you suggest. |
@lepistone Thanks |
sync readonly between pricelist and currency
as far as making the currency always readonly, I think it makes sense only if the user belongs to both groups For that reason I am making this change to currency always readonly in specific code only. |
I am making this only in the NGO verticalisation because it makes sense only if the user belongs to the group_purchase_pricelist. See OCA/purchase-workflow#88 (comment)
Addresses #80, see also odoo/odoo#4598.
If we have some states in which the pricelist can be changed but the
currency is readonly, the currency seems to be changed, but while saving
it goes back.
The core purchase module probably needs a similar fix.