Saturday, May 23, 2026
5 changes · saas-19.1
Resolved issues and error corrections
This update fixes an issue where fiscal positions weren't correctly created for US companies due to an outdated configuration. Now, fiscal positions are automatically generated based on a company's localization (US or Canada), ensuring accurate accounting and reporting. This simplifies the system and improves data accuracy.
Original PR description
The fiscal position was being created specifically for countries using the Generic CoA. This stems from before the US had its own CoA [1]. Because of this, US companies no longer had an Avatax fiscal position created for them. Now that the US has its own CoA, we move to a simpler `@template()` approach and take the opportunity to add Canada as well. [1] odoo/odoo#223745 task-6228639 Forward-Port-Of: odoo/enterprise#117966
This update enhances the Timesheet Assistant by opening internal links within a modal window. This keeps users within the Timesheets Assistant menu, providing a smoother and more intuitive experience when navigating related tasks and information.
Original PR description
This commit opens the internal links in the custom form view displayed in the timesheet assistant inside a modal to stay in Timesheets Assistant menu. task-[6132392](https://www.odoo.com/odoo/project/4105/tasks/6132392)
This update corrects a formatting error in invoices generated with large prices. Previously, invoices displayed extra decimal places due to a calculation issue. The fix reduces the precision used in calculations to ensure invoices display only the necessary digits, improving data accuracy and presentation.
Original PR description
Issue: - Create an invoice with a line having a price of `528,000,000.00` - Print the invoice -> pdf displays `528,000,000.000001` Cause: In `value_to_html` from `ir.qweb.field.float`, we compute the maximum precision that we can get from the value, to avoid parasite digits. The maximum is 15, so if a number has 11 digits, we won't ask for a precision higher than 4. But in `float_round`, they multiple the value with its precision, then add `epsilon` (a small value). So we're now working with a 16 digits float, which is what we want to avoid. Solution: Reduce the maximum precision from one digit before calling `float_round`. opw-6012129 Forward-Port-Of: odoo/odoo#265696 Forward-Port-Of: odoo/odoo#260955
This update fixes an issue where embedded actions didn't always display the correct translated names, especially after language changes or server action updates. The fix delegates the action's display name to the linked server action, ensuring consistent and accurate translations across all languages. This improves the user experience and avoids confusing untranslated names.
Original PR description
When an embedded action is created from a server action, its name is just stored as is. When using these actions e.g. in the Documents top bar, there is already a "hack" to copy the name of the…
When an embedded action is created from a server action, its name is just stored as is. When using these actions e.g. in the Documents top bar, there is already a "hack" to copy the name of the server action to the embedded action in each active language. This has a few issues: - When a language is activated after the embedded action creation, the name of the server action is not copied to the embedded action, resulting in an untranslated name. - When the name of the server action is changed, the name of the embedded action is not updated, resulting in an outdated and possibly untranslated name. The workaround is to disable/enable the action now, but it's not very user-friendly and can be easily forgotten. To fix this, we can simply delegate the display name of the embedded action to the linked server action. This way, the name of the embedded action will always be up to date and correctly translated. Related: https://github.com/odoo/enterprise/pull/116369 Forward-Port-Of: odoo/odoo#265342 Forward-Port-Of: odoo/odoo#262981
This update removes a redundant step in creating embedded actions within Odoo. Previously, a separate translation was required, but now that embedded actions inherit their display names directly, this manual process is no longer necessary. This simplifies the action creation workflow and ensures consistent translations.
Original PR description
Now that `ir.embedded.actions` delegates its display name to the linked action, the manual translation copy on embedded action creation is no longer needed. Related: https://github.com/odoo/odoo/pull/262981 Forward-Port-Of: odoo/enterprise#117772 Forward-Port-Of: odoo/enterprise#116369