Daily updates from Odoo
Wednesday, March 18, 2026
4 changes · master
Enhancements to existing features
This update brings the Balance Sheet and Profit & Loss reports for Chinese businesses in line with the latest accounting standards (ASBE and ASSBE). The changes improve report consistency and accuracy, ensuring compliance and reliable financial reporting.
Original PR description
### [IMP] l10n_cn_reports: update BS & PnL We update the Balance Sheet and Profit & Loss reports to be consistent with updated ASBE and ASSBE standards odoo-[251681](https://github.com/odoo/odoo/pull/251681) task-[5939988](https://www.odoo.com/odoo/all-tasks/5939988) --- We encountered an issue where setting `groupby = False` still resulted in an error (no groupby and children lines). This was resolved by setting a co-dependent variable `user_groupby = False`. The reports has lines with "Includes:" and sibling lines' name are expected to be aligned with it. Hierarchy lines and using various space characters (CJK space `　`, and "en" space ` `) was a maintenance nightmare. We instead chose to remove `includes:` as it's implied by the natural indentation of grouped lines. Forward-Port-Of: odoo/enterprise#109175
This update significantly enhances the map view by automating route calculations using the latest technology, providing a more efficient way to plan routes. It also cleans up the pin list UI, isolating unlocated records and improving the overall user experience. This streamlines operations for users relying on map-based data.
Original PR description
*: planning_field_service, project_enterprise, stock_fleet_enterprise, web_studio This commit acts as a follow-up to https://github.com/odoo/enterprise/pull/104618, heavily improving the map view's…
*: planning_field_service, project_enterprise, stock_fleet_enterprise, web_studio This commit acts as a follow-up to https://github.com/odoo/enterprise/pull/104618, heavily improving the map view's routing capabilities and pin list UI: **Routing & Optimization:** * **Automated Routing:** Manual record resequencing has been completely removed. Routing now utilizes the Mapbox Optimization API to automatically calculate the most efficient point-to-point route, including a return to the starting point. * **Dynamic Starting Point:** Added a new input for the starting (and returning) address. It uses the Mapbox or OpenStreetMap API for autocomplete and coordinate fetching. It defaults to the user's location (if available) or falls back to the active company's address. A toggler allows users to quickly reset to their location or clear the input. **Pin List & UI Improvements:** * **Unlocated Records:** Records without coordinates are now isolated in a dedicated group and can be clicked to open their form view directly. * **Empty Groups:** Groups containing only unlocated records are no longer displayed in the pin list to reduce clutter. * **Formatting:** The route duration tooltip now uses the latest duration formatter for a cleaner display. task-5930464
This update enhances the payrun review process by introducing a new warning dialog to highlight unreviewed employee records and pending time-offs. This allows HR staff to proactively address these items, ensuring accurate payroll processing and compliance. The change also includes translations for improved usability.
Original PR description
Task: 5965128
This update automatically populates Partena codes for common work entry types in Odoo, streamlining the payroll setup process for Belgian companies. Previously, users had to manually enter these codes, leading to inefficiencies and potential errors. This change simplifies compliance and reduces administrative burden.
Original PR description
Problem --------- Work entry types for Belgian companies currently lack default Partena codes, forcing users to manually input them, which is inefficient and prone to errors. Objective ---------- Provide pre-configured Partena codes for both common and Belgium-specific work entry types to automate the setup process. Solution ---------- Identified the required records and mapped our internal work entry types to the official Partena documentation, populating the 'Partena code' field with these default values. task-5411465