Saturday, June 6, 2026
4 changes · saas-19.3
Enhancements to existing features
This update introduces a new button to streamline the process for French users switching between Peppol and PDP accounts. Previously, reregistration was complex, particularly when transitioning between these systems. This change simplifies the process, improving usability and supporting key business workflows related to PEPPOL compliance.
Original PR description
#### [IMP] l10n_fr_pdp: fix visibility for peppol (non-PDP) #### [IMP] account_peppol,l10n_fr_pdp: reregister This commit adds a button so that users can reregister more easily. This is i.e. useful to switch from Peppol to PDP for French users. #### meta task-6265603 Forward-Port-Of: odoo/odoo#268699 Forward-Port-Of: odoo/odoo#267948
This update implements webhooks for exchanging Peppol documents in the French (l10n_fr_pdp) module. This was previously missing in the 18.0 release and is now essential for compliant data exchange with Peppol, ensuring accurate financial reporting. The change was implemented to address a gap identified during the recent system migration.
Original PR description
We did not have webhooks in 18.0 for Peppol and we did not have time to implement / test it during the FW-porting. This commit adds the route on community side that is called from IAP. task-None IAP PR: https://github.com/odoo/iap-apps/pull/1639 Forward-Port-Of: odoo/odoo#268674 Forward-Port-Of: odoo/odoo#268472
Resolved issues and error corrections
This update fixes a previous issue where the system incorrectly identified SIREN numbers by simply using the first 9 digits of the company ID. Now, a validation helper method is used to ensure accurate SIREN identification, particularly for users on IAP who may not have provided a SIREN. This improves the accuracy of KYC processes.
Original PR description
Currently we just take the first 9 numbers of the `company_id` and say it is the SIREN. On IAP we have some people who just seem to have put their company name. After this commit we use a helper method that does some simple validation at least. task-None Forward-Port-Of: odoo/odoo#268621 Forward-Port-Of: odoo/odoo#268202
This update resolves a bug where shift allocations incorrectly showed 0% when created on weekends, preventing accurate time calculations. Additionally, a test was adjusted to avoid running during demo data installations, ensuring a smoother user experience. These changes improve the reliability and usability of the planning module.
Original PR description
## [FIX] planning_field_service: avoid division by 0 Before this commit, when the shift is created during the weekend, the allocated_percentage will be 0 percent because the resource assigned is not…
## [FIX] planning_field_service: avoid division by 0 Before this commit, when the shift is created during the weekend, the allocated_percentage will be 0 percent because the resource assigned is not supposed to work at that day and so a division by zero occured in the onchange of break_time field in planning.slot model. This commit checks if allocated_percentage is not equal to 0 before computing the new allocated hours when the user alters break_time field on a planning.slot. ## [FIX] planning_field_service: don't start test with onboarding tour with demo Before this commit, the planning_field_service_tour tour does not work when there is demo data because the tour will select the first slot in the gantt view which will be an open shift instead of a shift assigned to the current user because of that, the sign in button is not displayed as expected. This commit makes sure the test running the planning_field_service_tour tour is skipped when demo data are installed. runbot-error-242483 Forward-Port-Of: odoo/enterprise#119032