Odoo Changelog — 2023-04-28

Friday, April 28, 2023

3 changes · master

Bug Fixes(3)

Resolved issues and error corrections

[FIX] account_winbooks_import: more correct import of VAT analytics

Enterprisemasteraccount_winbooks_importMedium

This fixes how VAT analytics are imported from Winbooks after a previous correction used the wrong ordering information. The change helps ensure accounting data is imported more accurately and reduces the risk of reporting inconsistencies.

Original PR description

The last fix 177c5d19264e7b27f153c097ada4c9abc7fbc6c3 incorrectly used the LINEORDER data from Winbooks. This commit fixes it. My bad.

#VAT#Winbooks#accounting#import

mail js ref

PR #4427

Enterprisemasterweb_enterprise

This update keeps the chat window manager attached to the main page body so messaging windows remain consistently available in the web client. It supports a more stable user experience when using Odoo's enterprise interface and related chat features.

Original PR description

Linked to https://github.com/odoo/odoo/pull/29617

Task-ID 1914207

#chat#web client#stability

[FIX] mrp_mps: use correct id in schedule stat button

PR #40453

Enterprisemastermrp_mps

The schedule shortcut now uses the record currently being viewed instead of carrying over a record reference from a previous screen. This prevents users from opening or acting on the wrong manufacturing planning schedule when navigating between related records.

Original PR description

Before this commit, the context added to the schedule stat button contained a reference to the active_id value. However, in this case, we actually want the current id of the record that we are looking at, not the id from a previous view.

Note that as far as I can tell, almost every use of `active_id` in stat button is wrong. It just usually works because we don't have an active id set, and there is a fallback in the basicmodel to get the current record id instead.  However, if a user would get to that form view by following some other relations and coming from another form view, then the active_id would not be correct.

#manufacturing#planning#navigation

Before this commit, the context added to the schedule stat button contained a reference to the active_id value. However, in this case, we actually want the current id of the record that we are looking at, not the id from a previous view. Note that as far as I can tell, almost every use of `active_id` in stat button is wrong. It just usually works because we don't have an active id set, and there is a fallback in the basicmodel to get the current record id instead. However, if a user would get to that form view by following some other relations and coming from another form view, then the active_id would not be correct.