Odoo Changelog — 2022-08-29

Monday, August 29, 2022

5 changes

Improvements(5)

Enhancements to existing features

[IMP] stock: revamp inventory menus + reports

Enterprisemasterstock_enterprisepurchase_enterpriseMEDIUM

This update reorganizes Inventory reporting menus with clearer naming, removes an obsolete forecasted inventory report, and consolidates duplicate Purchase reporting entries. Users should see a cleaner reporting experience with less confusion and fewer overlapping menu options.

Original PR description

Enterprise branch of COM PR: odoo/odoo#97109 (i.e. many small back2basics changes):
Upgrade PR: https://github.com/odoo/upgrade/pull/3819

---

[IMP] stock_enterprise: update inventory menus

Enterprise equivalent of menu renaming/reordering for "Reporting":
 - rename Warehouse Analysis => Performance and place at bottom of menu
   dropdown (i.e. this view aggregates all Warehouses together => name
   could be better)

"menu" part of b2b task: 2882539

---

[IMP] purchase_enterprise: remove duplicated reporting menuitem

The existing "Purchase > Reporting > Purchase" showed the same thing as
the "Purchase > Reporting > Dashboard" menuitem with the exception of
view order and filtering. Therefore we merge them into one by letting
Odoo do the name/order/filter replacing via inheritance.

"other" part of b2b task: 2882539

---

[REM] stock_enterprise: remove Forecasted Inventory view

The Forecasted Inventory view has become obsolete, this is the
equivalent enterprise code deletion of the community removal.

"forecast inventory" part of b2b task: 2882539
Upgrade PR: https://github.com/odoo/upgrade/pull/3819

#inventory#reporting#menus#purchase

[IMP] base: remove groups_id from ir.ui.view

PR #30643

Enterprisemasteraccount_followupaccount_reportsaccount_sepa_direct_debitdocumentshelpdeskhelpdesk_repairhelpdesk_salehelpdesk_sale_timesheethelpdesk_stockhelpdesk_timesheethr_appraisalhr_contract_signhr_payrollhr_referralindustry_fsmindustry_fsm_salel10n_uk_reportsmrp_account_enterpriseproject_forecastMEDIUM

This update removes an older, little-used way of controlling who sees parts of backend screens and replaces it with a clearer approach. The change simplifies future development and enables better performance by making screen layouts easier to cache.

Original PR description

The goal of this revision is to get rid of the `groups_id` field of the model `ir.ui.view`. - This feature wasn't really known or used by most developers, and not straight-forward to understand.…

The goal of this revision is to get rid of the `groups_id` field of the model `ir.ui.view`.

- This feature wasn't really known or used by most developers,
   and not straight-forward to understand.
   Removing it allows one less complicated thing to learn for developers.
   Besides, thanks to odoo/odoo#95729,
   changing the behavior of the `groups=` attribute, 
   we can easily get rid of this `groups_id` feature
   by simply adding `groups=` in the elements of the views
   using the `groups_id` field, it will have the same effect:
   adding the elements in the view only for the users part of the specified group.

- By getting rid of the groups_id many2many field on ir.ui.view,
   it makes possible to cache the view architecture without
   requiring to use the groups in the cache key.
   Currently, if we want to cache the view architecture,
  it would be required to use the intersection of the user
  groups with the groups_id groups of the view,
  making it costly to compute the cache key,
  therefore altering the performance point to cache the view
  architectures.

#views#access control#performance#simplification

[IMP] data_cleaning: Migrate to owl

PR #30666

Enterprisemasterdata_cleaningdata_mergeMEDIUM

The data cleaning and data merge list screens have been updated to a newer interface framework. This keeps these tools aligned with the rest of Odoo, improving maintainability and supporting a more consistent user experience over time.

#data cleanup#data merge#user interface#modernization

[IMP] account: ensure account's code compatibility with reportalypse

PR #30840

Enterprisemasteraccountaccount_assetaccount_reportsl10n_nl_reportspartner_commissionpos_account_reportsspreadsheet_accountMEDIUM

New validation prevents creating account records or templates with codes that the reporting engine cannot process. This reduces the risk of accounting reports failing because of unsupported characters in account codes.

Original PR description

The new account report engine requires account codes to only contain
alphanumeric characters and dots.
(see https://github.com/odoo/enterprise/blob/f435654f70f3d6a1fec7fa696945f2c0eb9a7056/account_reports/models/account_report.py#L2523)
Add two new constrains on account_account and account_account_template
to block the creation of accounts with codes that would cause issues
in account reports.

Task id #2960486

#accounting#reports#validation

[IMP] account: ensure account's code compatibility with reportalypse

PR #30836

Enterprisemasteraccountaccount_assetaccount_reportsl10n_nl_reportspartner_commissionpos_account_reportsspreadsheet_accountMEDIUM

Account codes are now restricted to letters, numbers, and dots so they work reliably with the newer reporting engine. This helps prevent report failures caused by unsupported characters when users create or configure accounts.

Original PR description

The new account report engine requires account codes to only contain
alphanumeric characters and dots.
(see https://github.com/odoo/enterprise/blob/f435654f70f3d6a1fec7fa696945f2c0eb9a7056/account_reports/models/account_report.py#L2523)
Add two new constrains on account_account and account_account_template
to block the creation of accounts with codes that would cause issues
in account reports.

Task id #2960486

#accounting#reporting#validation

Enterprise branch of COM PR: odoo/odoo#97109 (i.e. many small back2basics changes): Upgrade PR: https://github.com/odoo/upgrade/pull/3819 --- [IMP] stock_enterprise: update inventory menus Enterprise equivalent of menu renaming/reordering for "Reporting": - rename Warehouse Analysis => Performance and place at bottom of menu dropdown (i.e. this view aggregates all Warehouses together => name could be better) "menu" part of b2b task: 2882539 --- [IMP] purchase_enterprise: remove duplicated reporting menuitem The existing "Purchase > Reporting > Purchase" showed the same thing as the "Purchase > Reporting > Dashboard" menuitem with the exception of view order and filtering. Therefore we merge them into one by letting Odoo do the name/order/filter replacing via inheritance. "other" part of b2b task: 2882539 --- [REM] stock_enterprise: remove Forecasted Inventory view The Forecasted Inventory view has become obsolete, this is the equivalent enterprise code deletion of the community removal. "forecast inventory" part of b2b task: 2882539 Upgrade PR: https://github.com/odoo/upgrade/pull/3819

The goal of this revision is to get rid of the `groups_id` field of the model `ir.ui.view`. - This feature wasn't really known or used by most developers, and not straight-forward to understand. Removing it allows one less complicated thing to learn for developers. Besides, thanks to odoo/odoo#95729, changing the behavior of the `groups=` attribute, we can easily get rid of this `groups_id` feature by simply adding `groups=` in the elements of the views using the `groups_id` field, it will have the same effect: adding the elements in the view only for the users part of the specified group. - By getting rid of the groups_id many2many field on ir.ui.view, it makes possible to cache the view architecture without requiring to use the groups in the cache key. Currently, if we want to cache the view architecture, it would be required to use the intersection of the user groups with the groups_id groups of the view, making it costly to compute the cache key, therefore altering the performance point to cache the view architectures.

The new account report engine requires account codes to only contain alphanumeric characters and dots. (see https://github.com/odoo/enterprise/blob/f435654f70f3d6a1fec7fa696945f2c0eb9a7056/account_reports/models/account_report.py#L2523) Add two new constrains on account_account and account_account_template to block the creation of accounts with codes that would cause issues in account reports. Task id #2960486