Daily updates from Odoo
Friday, December 20, 2019
4 changes · master
Enhancements to existing features
Odoo now recognizes custom archive fields named x_active in the same way it handles the standard active field. This lets Studio-created or customized models support archiving, unarchiving, and automatic filtering more consistently in lists and forms, while imported modules are also cleaned up after uninstall.
Original PR description
Support active fields `x_active` like their equivalent `active` base fields: - `active_test` context key should take them into account - ditto for archive/unarchive methods - list/form views should support them OoB through the action menu Small fix for importable modules while i'm there This is the first brick in an incoming studio task that allows users to add per-defined behaviours on their new models. Archiving is one such behaviours and it requires this PR to work properly.
Users now see a clear, actionable message when their Google API key is invalid while adding video content. This helps them quickly fix the setting instead of receiving a confusing technical error.
Original PR description
Purpose ======= - Parse the JSON returned by Google - Show a custom message if the API key is invalid Task #2082857
Manufacturing orders now keep their planned start and finish dates aligned with the expected dates of their related stock movements. This improves rescheduling accuracy, fixes delay alerts for orders created from stock rules, and avoids confusing automatic date changes once production work has been planned.
Original PR description
- Now, the field ``date_planned_start`` now reflect the ``date_expected`` of the ``move_raw_ids``. - The field ``date_planned_finished`` reflect the ``date_expected`` of the ``move_finished_ids``. - Fix the delay alert on the manufacturing order - Stop date propagation if the manufacturing order is planned Task #1970595
Bulk reconciliation now avoids unnecessary cache refreshes, reducing slowdowns when processing many invoice and payment lines. This should make large payment order workflows faster and more reliable without changing user-facing accounting behavior.
Original PR description
Consider the case of a payment order when reconciling the invoices with the amounts that are transferred to a clearing account. Every time a move line is reconciled, the creation of the reconciliation clears the cache of account.move.line's reconcile_id and reconcile_partial_id which leads to a new prefetching of the growing amount of move lines in the env's prefetch dictionary. This change only clears the cache of the records that are actually referred to in the new record's relation fields. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr