Friday, March 14, 2025
4 changes · saas-18.2
Resolved issues and error corrections
Accounting demo data now checks whether related demo records are available before using them. This prevents test and installation failures in cases where demo data is being installed selectively, without changing the normal demo-data installation experience.
Original PR description
Check if demo data is present instead of referencing it directly, this allows to test installing demo data while not relying on demo data being installed. No changes for regular installation with demo data, while no demo installation will have very minimal new records when loading account demo data. Runbot Error 134673
Point of Sale now creates all required local data tables before reading stored data, preventing errors during local or offline access. It also skips unnecessary empty data updates, improving reliability without changing the user workflow.
Original PR description
Previously, tables defined in DataServiceOptions but missing from relations were not created, causing failures when reading local data via `getLocalDataFromIndexedDB`. Additionally, empty delete or add operations triggered unnecessary transactions. This fix addresses these issues by: - Ensuring all missing tables are correctly created. - Avoiding unnecessary transactions caused by empty delete/add operations.
This fixes the layout of Colombian DIAN-related journal settings so required localization fields appear in the right place and remain readable. Users configuring sales or purchase journals in South American localizations can now see the relevant fields below the Reload DIAN Configuration button as intended.
Original PR description
For the Reload DIAN Configuration button, a newly added class modifies the `colspan` of the surrounding `<div>`, forcing it to `colspan="1"` and causing the fields to be positioned next to the button incorrectly. **To Reproduce:** 1. Install the Accounting app and the `l10n_co_dian` module. 2. Navigate to Accounting > Configuration > Journals. 3. Open a Sales or Purchase Journal. 4. Observe that some localization fields are missing, misplaced, or unreadable. Community PR: odoo/odoo#201227 Ticket [link](https://www.odoo.com/odoo/project/967/tasks/4601714) opw-4601714
The VoIP app was updated to stop relying on an outdated mobile phone field in contact records. This helps avoid incorrect or missing caller and contact details when using VoIP features.
Original PR description
backport of #78996