Daily updates from Odoo
Navigate
Branch
Monday, August 2, 2021
11 changes
New functionality added to Odoo
A new VAT reporting feature has been added for Italian localization. This helps businesses in Italy prepare VAT statements more easily and supports local compliance workflows within Odoo.
Original PR description
Task: https://www.odoo.com/web#id=2079462&model=project.task
Enhancements to existing features
Manufacturing orders now include duration handling so scheduled dates are rounded up by default. This makes production planning more consistent and helps teams avoid schedules that underestimate required manufacturing time.
Resolved issues and error corrections
The Swedish point of sale receipt now separates services and products without blocking other receipt customizations. This helps businesses keep legally or operationally required receipt formatting while preserving compatibility with other receipt changes.
Original PR description
In the sweden localisation, the services and products must be separated on the receipt, and override as been performed to do this, but it now prevent of correctly override the receipt. So now, we are getting the line separately instead of changing the Orderline template
Code cleanup and technical improvements
This update adjusts several Enterprise web, VoIP, and Studio components to follow a shared internal structure for reusable hooks. It helps keep the codebase aligned with core platform changes, reducing maintenance effort without changing user-facing behavior.
Original PR description
This commit adapts imports w.r.t. the hooks refactoring of [1] [1] https://github.com/odoo/odoo/pull/74535
Miscellaneous changes
Whatever a payment is reconciled or not with an invoice, the user wants to match unmatched payments with a bank statement line. The confused has been introduced by: https://github.com/odoo/enterprise/commit/b4b0b8f4840ed2325f189313bf94b54ddcba09ce issues: 2556740 2522224 Forward-Port-Of: odoo/enterprise#19990 Forward-Port-Of: odoo/enterprise#19827
Original PR description
Whatever a payment is reconciled or not with an invoice, the user wants to match unmatched payments with a bank statement line. The confused has been introduced by: https://github.com/odoo/enterprise/commit/b4b0b8f4840ed2325f189313bf94b54ddcba09ce issues: 2556740 2522224 Forward-Port-Of: odoo/enterprise#19990 Forward-Port-Of: odoo/enterprise#19827
If you cancel a Mexican invoice and then attempt to print it, a red message will show on the invoice saying a signature is required. This doesn't make sense since the invoice was cancelled. This fix doesn't display that message if the invoice is in the cancelled state. In V13 and earlier the logic was different: the message would display if the folio fiscal was expected but not filled in. In the case of cancelled invoices in V13, the folio fiscal would remain filled in, so the message d
Original PR description
If you cancel a Mexican invoice and then attempt to print it, a red message will show on the invoice saying a signature is required. This doesn't make sense since the invoice was cancelled. This fix doesn't display that message if the invoice is in the cancelled state. In V13 and earlier the logic was different: the message would display if the folio fiscal was expected but not filled in. In the case of cancelled invoices in V13, the folio fiscal would remain filled in, so the message didn't trigger. In V14 the folio fiscal is cleared in that case, and the trigger logic was rewritten. opw-2582779 Screenshots of the behavior before the fix:   Forward-Port-Of: odoo/enterprise#19935
In the fix of avoid errors comming from SUNAT the error management was broken, now the original message in the CDR is correctly shown, giving useful information o the user to fix their documents. Included a better help for debugging due to the dual way of receiving this information the reading process of a CDR is a little bit complex, having the use cases in the documentation of the code will be useful for maintainance. Forward-Port-Of: odoo/enterprise#19939
Original PR description
In the fix of avoid errors comming from SUNAT the error management was broken, now the original message in the CDR is correctly shown, giving useful information o the user to fix their documents. Included a better help for debugging due to the dual way of receiving this information the reading process of a CDR is a little bit complex, having the use cases in the documentation of the code will be useful for maintainance. Forward-Port-Of: odoo/enterprise#19939
This is a legal requirement when one of the two following scenarios are given: * The SAT (Mexican government) asks to check the JEs to the company to audit (compulsory). It can happen to any company at some point the bigger the higher the chances of getting asked. * Our MX office could be a case that will need this in the future. When the company asks for compensation or return from the SAT (Government) An export of all Journal Entries from a specific period of time
Original PR description
This is a legal requirement when one of the two following scenarios are given:
* The SAT (Mexican government) asks to check the JEs to the company to audit (compulsory).
It can happen to any company at some point the bigger the higher the chances of getting asked.
* Our MX office could be a case that will need this in the future.
When the company asks for compensation or return from the SAT (Government)
An export of all Journal Entries from a specific period of time is needed, exported in an XML
so later this can be uploaded to the SAT webpage.
Task: https://www.odoo.com/web#id=2577821&model=project.task
Target Versions: v14 & Master
Forward-Port-Of: odoo/enterprise#19376Bugfix v13.0 add correct join to _get_query_amls to make commit a45a0694445537483c7396963dcff847df20d315 as mentioned in comment https://github.com/odoo/enterprise/commit/a45a0694445537483c7396963dcff847df20d315#commitcomment-52846627 Forward-Port-Of: odoo/enterprise#19891 Forward-Port-Of: odoo/enterprise#19585
Original PR description
Bugfix v13.0 add correct join to _get_query_amls to make commit a45a0694445537483c7396963dcff847df20d315 as mentioned in comment https://github.com/odoo/enterprise/commit/a45a0694445537483c7396963dcff847df20d315#commitcomment-52846627 Forward-Port-Of: odoo/enterprise#19891 Forward-Port-Of: odoo/enterprise#19585
The blackbox module will now depends of pos_restaurant_iot and not from both pos_restaurant and pos_iot. The view inheritance for the pos.config could lead to some issues. This commit fix this by properly choosing the right view to inherit. Change the controller to filter the pos config. the blackbox context won't be added anymore to session that are not blackboxed. Add the super() call that was missing in the close function. Forward-Port-Of: odoo/enterprise#19821 Forward-Port-Of: odoo/enter
Original PR description
The blackbox module will now depends of pos_restaurant_iot and not from both pos_restaurant and pos_iot. The view inheritance for the pos.config could lead to some issues. This commit fix this by properly choosing the right view to inherit. Change the controller to filter the pos config. the blackbox context won't be added anymore to session that are not blackboxed. Add the super() call that was missing in the close function. Forward-Port-Of: odoo/enterprise#19821 Forward-Port-Of: odoo/enterprise#18519
- Install timesheet_grid - Activate dev mode - Go to Settings > Technical > Server Actions - Create a server action: * Model: Analytic Line * Action To Do: Execute Python Code * Python Code: [any valid python code] - Take note of id of server action (i.e. 123) - Go to Timesheets > My Timesheets (in grid view) - Click on bug icon > Edit View: Grid - In grid element, edit adjustment and adjust_name attributes as followed: * adjustment="object" => adjustment="action" * adjust_
Original PR description
- Install timesheet_grid - Activate dev mode - Go to Settings > Technical > Server Actions - Create a server action: * Model: Analytic Line * Action To Do: Execute Python Code * Python Code: [any valid python code] - Take note of id of server action (i.e. 123) - Go to Timesheets > My Timesheets (in grid view) - Click on bug icon > Edit View: Grid - In grid element, edit adjustment and adjust_name attributes as followed: * adjustment="object" => adjustment="action" * adjust_name="adjust_grid" => adjust_name="123" - Refresh page and try to fill a timesheet slot The following error is triggered: "AttributeError: type object 'account.analytic.line' has no attribute '123'" Adjustment of type "action" is not handled by grid view anymore. opw-2523970 Forward-Port-Of: odoo/enterprise#19981 Forward-Port-Of: odoo/enterprise#19795