Odoo Changelog — 2023-09-19

Tuesday, September 19, 2023

3 changes · master

Bug Fixes(2)

Resolved issues and error corrections

[FIX] *: compute methods mixing stored and non-stored fields

Enterprisemasteraccount_assetdata_cleaninghr_payrolll10n_be_hr_payrollmrp_plmmrp_workorderproject_timesheet_forecastMEDIUM

This fix separates internal calculations that were mixing saved and on-the-fly values across several business apps. It helps prevent inconsistent results or unexpected behavior in areas such as assets, payroll, manufacturing, timesheets, and data cleaning.

Original PR description

Companion of https://github.com/odoo/odoo/pull/98565.

#reliability#computed fields#payroll#manufacturing#timesheets

[FIX] web_studio: do preload field's value if invisible

PR #47129

Enterprisemasterweb_studioMEDIUM

Odoo Studio now loads values for fields that are hidden in form, list, and kanban views when users choose to show invisible fields. This prevents crashes in form editing and avoids incorrect data being shown in list and kanban editors.

#studio#invisible fields#views#data accuracy

Refactoring(1)

Code cleanup and technical improvements

[REF] pos*: unify order components

PR #45972

Enterprisemasterpos_iotpos_settle_dueMEDIUM

The point-of-sale order view has been standardized across key screens, reducing duplicated behavior and making future updates more reliable. This also improves consistency for staff using product, ticket, split bill, and related POS flows.

Original PR description

At the moment, the pos displays the selected order in multiple screens, such as the `ProductScreen`, the `TicketScreen`, the `SplitBillScreen`, the `self_order` app, but uses completely different…

At the moment, the pos displays the selected order in multiple
screens, such as the `ProductScreen`, the `TicketScreen`, the
`SplitBillScreen`, the `self_order` app, but uses completely
different implementations for each. This means that when
a change needs to be made to the one, it generally needs to be made
to the other as well, which is error-prone.

In this commit we create generic `OrderWidget` and `Orderline` components,
that have not dependencies on POS objects and we refactor the `ProductScreen`,
the `TicketScreen` and the `SplitBillScreen` to use these components.

The `OrderSummary` component was removed and it's contents are now in the
`OrderWidget`.

We also introduce a very simple new component called `CenteredIcon` that
can be used whenever we want to show an icon that fills a whole div. In this
commit we use it for showing the cart icon when the order is empty.

In a future commit, the `pos_self_order` will be refactored in order
to use the same `OrderWidget` and `Orderline` compoenents as the POS.

Task: 3470365

In addition, this commit solves the issue from the task 3491303.
    https://github.com/odoo/odoo/pull/132248

#point-of-sale#orders#maintenance#consistency

At the moment, the pos displays the selected order in multiple screens, such as the `ProductScreen`, the `TicketScreen`, the `SplitBillScreen`, the `self_order` app, but uses completely different implementations for each. This means that when a change needs to be made to the one, it generally needs to be made to the other as well, which is error-prone. In this commit we create generic `OrderWidget` and `Orderline` components, that have not dependencies on POS objects and we refactor the `ProductScreen`, the `TicketScreen` and the `SplitBillScreen` to use these components. The `OrderSummary` component was removed and it's contents are now in the `OrderWidget`. We also introduce a very simple new component called `CenteredIcon` that can be used whenever we want to show an icon that fills a whole div. In this commit we use it for showing the cart icon when the order is empty. In a future commit, the `pos_self_order` will be refactored in order to use the same `OrderWidget` and `Orderline` compoenents as the POS. Task: 3470365 In addition, this commit solves the issue from the task 3491303. https://github.com/odoo/odoo/pull/132248