Friday, February 7, 2025
2 changes · saas-17.4
Resolved issues and error corrections
A configuration issue in the Point of Sale product form was corrected so Odoo no longer shows an unnecessary access rights warning in the technical views area. This helps administrators avoid confusion when reviewing or customizing product-related views.
Original PR description
Steps to reproduce : -open settings/technical/views -search "product.template.form.inherit" -select the view with external id "point_of_sale.product_template_form_inherit" -A Yellow Warning Message should appear indicating an Access Rights Inconsistency Problem: In the product_view.xml file of the point_of_sale module, in the view named product.template.form.inherit for the field "color", the invisible condition was invisible="true". This caused an accessed right inconsistency because the python code did not recognize true as a Boolean but looked for a field named "true" in the product.template model and didn't find any. https://github.com/odoo/odoo/blob/abf0b5f102a0bad3ed0feb8b8e967f5e3c8d2288/addons/point_of_sale/views/product_view.xml#L69 opw-4520474
Updates to the Belgian reports post wizard module now avoid rewriting the official FPS bank account during module upgrades. This prevents upgrade failures when the account has already been marked as trusted, while keeping the official default account available for payments.
Original PR description
When updating the module, the bank data is reloaded. When the account is already trusted (`allow_out_payment == True`), the write fails due to checks to prevent fraud. To fix this, we wrap the data in a `noupdate` to prevent further writes from happening. If ever the account number changes, a new record will be created instead of updating the existing one. Since this account is the default one stipulated on the official fps site, it can be trusted by default. Issue reported by upgrade team.