Daily updates from Odoo
Friday, February 18, 2022
12 changes
Enhancements to existing features
The mock server used in tests now returns records in the same predictable order as the real system, including more complex sorting rules. This improves test consistency and better reflects real customer behavior, with related spreadsheet document tests updated accordingly.
Original PR description
This PR is the enterprise counterpart of a PR of the same name. Said PR orders the records coming from the mock server the same way they are ordered by the ORM, while also allowing it to support multiple levels of orderby. This has been done to increase consistency in the test suite and provide a more accurate representation of how records would be returned by the actual server. Some tests performed their assertions based on this previous undeterministic system and have been adapted, either by altering the base setup or the assertions themselves. Community: https://github.com/odoo/odoo/pull/84718
This update adjusts automated test setup across messaging and related business apps so tests can prepare data asynchronously. It helps keep quality checks reliable as the mail features evolve, with no direct change expected for end users.
Original PR description
community: https://github.com/odoo/odoo/pull/84845 task-2767820
Dashboards now use the shared sizing setting for embedded pivot views, helping reports fit more consistently in their dashboard layout. This is a small visual improvement that reduces layout inconsistencies for users viewing pivot-based dashboard content.
Original PR description
Prior this commit the width of the Pivot view was managed by different width properties in css. Now we use a css variable to manage the width depending on the context. This commit updates this variable when the Pivot view is embedded in a Dashboard view. Requires: - https://github.com/odoo/odoo/pull/82575 task-2731553
Resolved issues and error corrections
Field service jobs will now rely on the standard address update process to refresh geolocation details when an address changes. This avoids duplicate handling in the field service app and helps keep location information accurate for scheduling and dispatching.
Original PR description
Along with this community PR odoo/odoo#84878 the geolocation info will be automatically recomputed when the address has been modified.
Code cleanup and technical improvements
The Sign app was adjusted to use the updated location of a cursor image asset. This keeps the signing interface aligned with the shared platform file structure and helps avoid missing visual elements.
Original PR description
Adapt CSS rules according to the new image path in community. Community: https://github.com/odoo/odoo/pull/84837
Miscellaneous changes
opw-askraf Forward-Port-Of: odoo/enterprise#23930
Original PR description
opw-askraf Forward-Port-Of: odoo/enterprise#23930
Before this PR: If you select several invoices to post them from tree/list view and one of them has a partner with commercial activity and or dte_email that is missing, you cannot identify which partner or which invoice is the one with incorrect data. After this PR: the raise UserError will tell you which partner you need need to edit, or wich invoice has the incorrect tax selected. Forward-Port-Of: odoo/enterprise#24500 Forward-Port-Of: odoo/enterprise#23613
Original PR description
Before this PR: If you select several invoices to post them from tree/list view and one of them has a partner with commercial activity and or dte_email that is missing, you cannot identify which partner or which invoice is the one with incorrect data. After this PR: the raise UserError will tell you which partner you need need to edit, or wich invoice has the incorrect tax selected. Forward-Port-Of: odoo/enterprise#24500 Forward-Port-Of: odoo/enterprise#23613
Currently, some CL tests are not running correctly, which was exposed by setting a fiscal country before loading journals in 15.3+. Now the mock data is correct. Needed for Task 2717840 Tests in test_l10n_cl_fetchmail_server.py were running successfully before because some things were mistakingly ignored because of several reasons: - 'l10n_latam_use_documents': True was set on purchase journal, but not on sales journal - journal_id.l10n_latam_use_documents was always False, as that is set
Original PR description
Currently, some CL tests are not running correctly, which was exposed by setting a fiscal country before loading journals in 15.3+. Now the mock data is correct. Needed for Task 2717840 Tests in test_l10n_cl_fetchmail_server.py were running successfully before because some things were mistakingly ignored because of several reasons: - 'l10n_latam_use_documents': True was set on purchase journal, but not on sales journal - journal_id.l10n_latam_use_documents was always False, as that is set based on `account_fiscal_country_id.code == 'CL'` and that was not the case in tests Setting the fiscal country before journals are loaded and setting 'l10n_latam_use_documents': True on the sales journal showed that CAF files were missing to run tests successfully and taxes were applied where they shouldn't be. Forward-Port-Of: odoo/enterprise#24475 Forward-Port-Of: odoo/enterprise#24225
Change that archive/delete variant that are excluded will archive a product ("[DESK0004] Customizable Desk (CONFIG) (Aluminium, Black)") in demo data (odoo/odoo#83427). With this change, stock_account_enterprise TestStockReport fails because stock.report is compared to products and stock.valuation.layer that are not archived. With this changeset, the test is updated so it still works even if used demo data are archived. opw-2729329 Forward-Port-Of: odoo/enterprise#24386 Forward-Po
Original PR description
Change that archive/delete variant that are excluded will archive
a product ("[DESK0004] Customizable Desk (CONFIG) (Aluminium, Black)")
in demo data (odoo/odoo#83427).
With this change, stock_account_enterprise TestStockReport fails
because stock.report is compared to products and stock.valuation.layer
that are not archived.
With this changeset, the test is updated so it still works even if used
demo data are archived.
opw-2729329
Forward-Port-Of: odoo/enterprise#24386
Forward-Port-Of: odoo/enterprise#24251Since 1767c9a0681961466de4d7436fe304f5fd942455, the qweb template of the demo data was not correctly generated. Forward-Port-Of: odoo/enterprise#24487
Original PR description
Since 1767c9a0681961466de4d7436fe304f5fd942455, the qweb template of the demo data was not correctly generated. Forward-Port-Of: odoo/enterprise#24487
…racts Currently the payslip is adapted by hand when 1 employee has 2 contracts over the same payslip period. This commit is implementing it. The difficulty is that all the payslips are generated at the same time. Forward-Port-Of: odoo/enterprise#24444
Original PR description
…racts Currently the payslip is adapted by hand when 1 employee has 2 contracts over the same payslip period. This commit is implementing it. The difficulty is that all the payslips are generated at the same time. Forward-Port-Of: odoo/enterprise#24444
Before: Lines of the report were grouped by partner and account_tax_report_line_id. Instead of being grouped by type of operation(L, T or S). Since there are 2 account_tax_report_line_id per operation (one for invoices, one for credit notes), there might be 2 lines for one same type. After: Line are grouped by partner and operation type (grouping invoices and credit notes together) Task: 2751997 Parent task: 2730151 See: https://github.com/odoo/enterprise/pull/23889 Forward-Port-Of:
Original PR description
Before: Lines of the report were grouped by partner and account_tax_report_line_id. Instead of being grouped by type of operation(L, T or S). Since there are 2 account_tax_report_line_id per operation (one for invoices, one for credit notes), there might be 2 lines for one same type. After: Line are grouped by partner and operation type (grouping invoices and credit notes together) Task: 2751997 Parent task: 2730151 See: https://github.com/odoo/enterprise/pull/23889 Forward-Port-Of: odoo/enterprise#23890