Odoo Changelog — 2025-07-04

Friday, July 4, 2025

2 changes · 18.0

Improvements(2)

Enhancements to existing features

Update res_partner.py

Core18.0baseMedium

This change adds checks to make sure customer phone numbers, email addresses, and website links are properly formatted before they are saved. It helps keep contact records cleaner and reduces problems caused by incorrect customer information.

Original PR description

Added validation for phone, email, and website fields on res.partner

Added validation logic to ensure only properly formatted phone numbers, emails, and website URLs are accepted when creating or updating a customer/contact.

Description of the issue/feature this PR addresses:

Customers could be created with invalid phone, email, or website values.
Current behavior before PR:

No validation exists for the format of phone, email, or website fields on res.partner.
Desired behavior after PR is merged:

Validation is enforced for phone, email, and website fields, preventing the creation or update of a customer/contact with invalid values.

I confirm I have signed the CLA and read the PR guidelines at [www.odoo.com/submit-pr]

#contacts#validation#data quality

[IMP] l10n_sa_edi: generating serial number on journal and fixing the…

PR #217120

Core18.0l10n_sa_ediMedium

Saudi e-invoicing journal onboarding now creates unique identifiers using each journal's code, name, company, and internal ID. This reduces duplicate setup issues and alerts existing users to re-onboard affected journals where prior identifiers may not have been unique.

Original PR description

… common name to be unique per journal

Previously, the company name was used as the common name when onboarding the journal. However, the common name has to be unique.
The fix changes the common name to use the journal's short code, journal name, and company name to ensure uniquness.

Additionally, an improvement is applied to the serial number on journals. Previously, users inputted this field manually.
Now, the system uses the journal's id as the serial number to ensure uniqueness.

A post-migration script was added to notify users that they need to re-onboard their journals.
This is done in case users previously onboarded journals with non-unique serial numbers.

task-4797124

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#216135
Forward-Port-Of: odoo/odoo#215012

#saudi-arabia#e-invoicing#journal-onboarding#localization

Added validation for phone, email, and website fields on res.partner Added validation logic to ensure only properly formatted phone numbers, emails, and website URLs are accepted when creating or updating a customer/contact. Description of the issue/feature this PR addresses: Customers could be created with invalid phone, email, or website values. Current behavior before PR: No validation exists for the format of phone, email, or website fields on res.partner. Desired behavior after PR is merged: Validation is enforced for phone, email, and website fields, preventing the creation or update of a customer/contact with invalid values. I confirm I have signed the CLA and read the PR guidelines at [www.odoo.com/submit-pr]

… common name to be unique per journal Previously, the company name was used as the common name when onboarding the journal. However, the common name has to be unique. The fix changes the common name to use the journal's short code, journal name, and company name to ensure uniquness. Additionally, an improvement is applied to the serial number on journals. Previously, users inputted this field manually. Now, the system uses the journal's id as the serial number to ensure uniqueness. A post-migration script was added to notify users that they need to re-onboard their journals. This is done in case users previously onboarded journals with non-unique serial numbers. task-4797124 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#216135 Forward-Port-Of: odoo/odoo#215012