Daily updates from Odoo
Navigate
Branch
Wednesday, July 20, 2022
15 changes
Enhancements to existing features
Belgian payroll users can now sign DmfA declarations directly during file generation using the certificate-based method required by ONSS. This reduces manual work and helps companies stay compliant after older eID SHA-1 signatures were disallowed.
Original PR description
Purpose ======= The sha-1 signatures using eid cards is now forbidden by the ONSS, which requires to use an authorized certificate (mainly GlobalSign). As the process is rather complex, allow to sign the file directly when generating the DmfA file, using sha256 and pkcs7. TaskID: 2743863
The Intrastat report now shows system and type information together as a single Commodity Flow field, reducing duplicate information for users. Spreadsheet exports keep the simpler system code only, making exported data cleaner while preserving the needed reporting detail.
Original PR description
On the intrastat report the system and type fields represent the same thing and are thus redundant. It therefore makes sense to consolidate them into one field called 'Commodity Flow'. In this commit…
On the intrastat report the system and type fields represent the same thing and are thus redundant. It therefore makes sense to consolidate them into one field called 'Commodity Flow'. In this commit the two fields instead represented as one field, with the 'system' first, and the 'type' following it in brackets e.g. 19 (Dispatch). The xlsx export should instead contain only the 'system' (the 'type' is actually redundant when considering the 'system' codes), so the 'print_xlsx' function is modified such that only the 'system' is used. In order to achieve this distinction, a key 'country_format' is inserted into the options inside of the 'print_xlsx'. The content of this report 'Commodity Flow' field is generated depending on this key. The tests are updated to match this new structure and a new test has been added to test the content of the report under the same conditions as an xlsx export (i.e. codes instead of names). task-id: 2884333 This PR contains the majority of the contents of the original PR: https://github.com/odoo/enterprise/pull/28630, which was closed in v13.0 as the contents would have violated stable policy. The part that is fine to merge in stable is not included in this PR, and is in a different PR in v13.0: https://github.com/odoo/enterprise/pull/29505 (It involves altering the dictionaries containing the key-value pairs of country-code to 'system' for the Netherlands)
The Chilean electronic invoicing setup has been adjusted to stay compatible after email retrieval features were consolidated into the main mail system. This helps keep configuration records aligned and reduces upgrade or setup issues for affected deployments.
Original PR description
With linked community PR, the `fetchmail` module is moved into `mail` and so this commit adapts the changes by improving xml ids of the records that are now part of the `mail` module. task-2797458
This update refreshes the spreadsheet engine with fixes that improve formula recalculation, chart formatting, menu interactions, and demo data links. It also adds support for the TEXT formula, helping users format values more flexibly inside spreadsheets.
Original PR description
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/765361db [FIX] Tests: Clean *Registry after tests https://github.com/odoo/o-spreadsheet/commit/1b830e98 [IMP] husky: allow use of pre-commit hook for windows https://github.com/odoo/o-spreadsheet/commit/6306bad9 [FIX] evaluation: re-evaluate async formulas when changing sheets https://github.com/odoo/o-spreadsheet/commit/2b5cf2b4 [FIX] evaluation: re-evaluate errors in other sheets https://github.com/odoo/o-spreadsheet/commit/f3e4efc6 [IMP] Functions: Add `TEXT`function https://github.com/odoo/o-spreadsheet/commit/01f93c8d [FIX] Charts: Set a format on a cell invalidates runtimes https://github.com/odoo/o-spreadsheet/commit/0bf9533f [FIX] formats: use `cell.evaluated.format` https://github.com/odoo/o-spreadsheet/commit/7dd1bc3f [FIX] top_bar: bugged top_bar menu item hitbox https://github.com/odoo/o-spreadsheet/commit/67ec2703 [FIX] spreadhseet: fix link demo data
Resolved issues and error corrections
This fix makes automated tests for spreadsheet date filters more consistent by using the right event when selecting dates. It reduces false test failures, helping development and releases stay predictable without changing user-facing behavior.
Original PR description
The tests using the new date picker were indeterministic. I'm pretty sure the problem was that the input was triggered by a click in the tests rather than by a "change" event. Odoo task 2925733
This update removes an unnecessary access restriction from Australian KeyPay settings. It prevents settings-related test failures and keeps the configuration behavior aligned with other accounting settings, with no expected impact for regular users.
Original PR description
Some settings are using the group "account.group_account_manager", which causes issue with a test on the settings. As this group is not really necessary, and no other accounting settings are using it, we can just remove it.
The app creator form now displays checkbox options with the correct spacing after the Bootstrap 5 update. This prevents confusing or misaligned fields when users configure a new model in Studio.
Original PR description
Since BS5, the checkbox input are visible, so we must set margin on the parent. Note in BS4 the input was hidden, and instead we rely on pseudo-element (`::before` and `::after`) Also removed `custom-control` class as not present in BS5 anymore.
This change fixes an unreliable automated test in the document spreadsheet area. It helps keep development checks stable so future updates can be delivered with fewer false alarms.
Historical refund values in the subscription dashboard are corrected so monthly recurring revenue reports show accurate totals. This ensures pivot views and past reporting data align with the fixed calculation, improving confidence in revenue analysis.
Original PR description
https://github.com/odoo/enterprise/commit/9812998643668bc1eaacef69e957b3ff66f0f6fc fixed the MRR computation but older value remained. These value were prefixed with the right amount but pivot views were still wrong for historical data. This commit and the associated upgrade script fix these values. taskid: 2909297
Fixed an issue where spreadsheets with a global filter set to a year could fail during export. Users can now export these spreadsheets reliably without the export crashing on year-based filters.
Original PR description
odoo-dev/enterprise@6645e89eacf8f40dcc46d9e4cb35bd41b9250220 introduced advanced year picking for global filter, but the year was returned as a year in the getter `getFilterDisplayValue()` instead of a string. This caused the export of the global filters to crash, since the export tried to call the method `.trim()` on a number. Odoo task 2896941
This fixes a styling issue where Odoo Studio used the browser's default font instead of the intended application font after the Bootstrap 5 migration. The change restores a consistent look in Studio, improving visual consistency for users without changing functionality.
Original PR description
Since BS5 migration, font in studio was not the same. This is because
it uses the SCSS variable `$font-family-base`, but in BS5 this variable
is set with:
```scss
$font-family-base: var(--#{$variable-prefix}font-sans-serif) !default;
```
but since it use `--#{$variable-prefix}` and there is no
`bootstrap_overridden.scss` for studio there was a missmatch and so no
font was set and use the default font set in the browser.
To avoid this, we set the `--#{$variable-prefix}` to empty to avoid
missmatch.Code cleanup and technical improvements
The dashboard view now relies on the standard onboarding banner that is already provided by default. This removes duplicate setup and helps keep dashboard behavior aligned with the rest of the system without changing the user experience.
Original PR description
Community: 9620deb7dc84b599b5085e942eb1eedbc3c85ecc
Miscellaneous changes
Before this commit, the printed layout of the report did not use any css. Trying to print the report would also produce a traceback because the subscription_id variable was not defined anymore. Forward-Port-Of: odoo/enterprise#29286
Original PR description
Before this commit, the printed layout of the report did not use any css. Trying to print the report would also produce a traceback because the subscription_id variable was not defined anymore. Forward-Port-Of: odoo/enterprise#29286
The diot report was completely wrong, as we did not have a refunds column, in which should have be present the amounts of the refunds paid with following taxes : IVA 16%, IVA 8%, IVA 0%, Whithheld taxes. We made a little refactor in _get_lines method in order to make it a little more readable, and allow to processcredit notes from above taxes on last column. Add also the refund column on diot and dpiva txt reports. opw-2733076 opw-2751671 Forward-Port-Of: odoo/enterprise#29614 F
Original PR description
The diot report was completely wrong, as we did not have a refunds column, in which should have be present the amounts of the refunds paid with following taxes : IVA 16%, IVA 8%, IVA 0%, Whithheld taxes. We made a little refactor in _get_lines method in order to make it a little more readable, and allow to processcredit notes from above taxes on last column. Add also the refund column on diot and dpiva txt reports. opw-2733076 opw-2751671 Forward-Port-Of: odoo/enterprise#29614 Forward-Port-Of: odoo/enterprise#29115
Previously, owl would not overwrite the value of an input when patched if the value computed in the render was the same as the previous render, even if the value in the DOM was changed (by the user or programmatically). This was fixed, but this can cause issues in components that relied on the old behaviour such as the timer header component. This commit simply puts the input value in a state and updates it as necessary, so that it is not lost on render. Forward-Port-Of: odoo/enterprise#2
Original PR description
Previously, owl would not overwrite the value of an input when patched if the value computed in the render was the same as the previous render, even if the value in the DOM was changed (by the user or programmatically). This was fixed, but this can cause issues in components that relied on the old behaviour such as the timer header component. This commit simply puts the input value in a state and updates it as necessary, so that it is not lost on render. Forward-Port-Of: odoo/enterprise#29626