Daily updates from Odoo
Thursday, May 28, 2020
10 changes
Enhancements to existing features
This update standardizes how shared configuration values are managed across several Odoo Enterprise apps. It reduces the risk of inconsistent settings behavior during accounting, payroll, reporting, renting, and stock accounting operations, with no expected change to day-to-day workflows.
Original PR description
Do not make direct CRUD to ir.property records, use appropriate methods for that Enterprise part of odoo/odoo#51658
Resolved issues and error corrections
The salary contract process no longer sends an unused token value to certain server routes. This reduces unnecessary network data and prevents repetitive log messages, making the system cleaner to operate without changing user behavior.
Original PR description
Since b2f9403 the param `token` is no longer necessary for some routes. We should avoid sending unnecessay things via the network. Moreover, it logs this everytime the route is called which brings noise to the logs. `INFO odoo-db odoo.http: <function odoo.addons.l10n_be_hr_contract_salary.controllers.main.onchange_advantage> called ignoring args <token>`
Salary contract simulations now handle internal saving steps with the right permissions, preventing test and workflow failures when employee data is not already cached. This makes the payroll salary package flow more reliable in limited module setups without changing user-facing features.
Original PR description
We flush the contract to avoid writing anything after the rollback (maybe everything should be flushed and not only the contract?). Flushing triggers fields recomputation which read and writes some records. However the user might not have the required access rights here. This leads to the following problem: Install `test_l10n_be_hr_payroll_account` only and run the module tests. => The tour fails, trying to read the employee without the required access rights. Note: the tour does not fail if all modules are installed; hence it does not fail when tests are run on Runbot. The reason is that the employee is already loaded (by some other module) in the cache with a sudo'ed environnement.
Features or functions removed from Odoo
The Helpdesk ticket and Sales Subscription list views no longer show the activity exception indicator. This simplifies those lists by removing a status decoration that may have been redundant or no longer needed.
Original PR description
activity_exception_decoration widget from following tree view - helpdesk.ticket.tree - sale.subscription.list
Miscellaneous changes
…report Having 'strict_range' as special_date_changer on a line owned by a financial report that uses a single date doesn't make sense. But it works like a 'normal' special_date_changer until this commit: https://github.com/odoo/enterprise/commit/8cb9de9e6acb9bf17b29f813f277d987e0547f4b issue: 2228146 Forward-Port-Of: odoo/enterprise#10689
Original PR description
…report Having 'strict_range' as special_date_changer on a line owned by a financial report that uses a single date doesn't make sense. But it works like a 'normal' special_date_changer until this commit: https://github.com/odoo/enterprise/commit/8cb9de9e6acb9bf17b29f813f277d987e0547f4b issue: 2228146 Forward-Port-Of: odoo/enterprise#10689
Go to Accounting / Reporting / Management / Assets Report Click Save, select 'PDF' and export error will appear "Type error : Object of type "account.assets.report" is not JSON serializable" This occur because between the options to save with a serialization there is a reference to a recordset opw-2258280 Forward-Port-Of: odoo/enterprise#10831
Original PR description
Go to Accounting / Reporting / Management / Assets Report Click Save, select 'PDF' and export error will appear "Type error : Object of type "account.assets.report" is not JSON serializable" This occur because between the options to save with a serialization there is a reference to a recordset opw-2258280 Forward-Port-Of: odoo/enterprise#10831
### Issue - Have a standard V13 with sale_management & documents - Go to Settings => Documents - Check "Product" - Go to Technical => Activity Types - Create Activity Type AT - Action to Perform: Upload Document - Folder: Products - Model: Product Template - Go to Sales => Products => Products - Choose any - Schedule Activity - Activity Type: AT - Save - Upload any document for AT Cons
Original PR description
### Issue
- Have a standard V13 with sale_management & documents
- Go to Settings => Documents
- Check "Product"
- Go to Technical => Activity Types
- Create Activity Type AT
- Action to Perform: Upload Document
- Folder: Products
- Model: Product Template
- Go to Sales => Products => Products
- Choose any
- Schedule Activity
- Activity Type: AT
- Save
- Upload any document for AT
Constraint error
### Cause
We try to change the attachment_id of a document
but this id is already used so a unique constraint
throws an error
### Solution
Check if the attachment_id is already used before
**OPW-2252681**
Forward-Port-Of: odoo/enterprise#10798Forward-Port-Of: odoo/enterprise#10816 Forward-Port-Of: odoo/enterprise#10800
Original PR description
Forward-Port-Of: odoo/enterprise#10816 Forward-Port-Of: odoo/enterprise#10800
In some cases, the field signing_date is not set and it lead to a TypeError '<' not supported between instances of 'bool' and 'datetime.date' when trying to order the records. opw:2254189 Forward-Port-Of: odoo/enterprise#10799
Original PR description
In some cases, the field signing_date is not set and it lead to a TypeError '<' not supported between instances of 'bool' and 'datetime.date' when trying to order the records. opw:2254189 Forward-Port-Of: odoo/enterprise#10799
Before this commit, there was a new line in the end of the mod 303 tax report. opw-2201325 Forward-Port-Of: odoo/enterprise#10791
Original PR description
Before this commit, there was a new line in the end of the mod 303 tax report. opw-2201325 Forward-Port-Of: odoo/enterprise#10791