Odoo Changelog — 2025-07-21

Monday, July 21, 2025

3 changes · saas-18.1

Bug Fixes(3)

Resolved issues and error corrections

[FIX] l10n_vn_edi_viettel: no need buyer district, correct buyercity

PR #219368

Coresaas-18.1l10n_vn_edi_viettelMedium

Vietnamese Viettel e-invoices are updated to match recent administrative changes that remove district-level address requirements. The buyer city field can now use either the city or state information, reducing rejected or incorrect invoice submissions when customer address data is incomplete.

Original PR description

* Problem: Since what has been described in https://github.com/odoo/odoo/pull/214134 and
https://thuvienphapluat.vn/chinh-sach-phap-luat-moi/vn/ho-tro-phap-luat/chinh-sach-moi/82581/tu-ngay-01-7-2025-ca-nuoc-se-khong-con-quan-huyen Vietnam no longer have district and city in city no more (Before in Vietnam we will have Thu Duc City belong to Ho Chi Minh State or Thuy Nguyen City belong to Hai Phong), Therefore we need to update Sinvoice data for this to.

* This commit remove BuyerDistrict parameter , beside using state in the district is totally wrong and for 'buyerCityName' accept city or state field because odoo user might leave the city empty and just input state

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




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

Forward-Port-Of: odoo/odoo#218984

#Vietnam#e-invoicing#Viettel#address

[FIX] mail: message related to deleted record doesn't break discuss

PR #219782

Coresaas-18.1mailMedium

Inbox and history views now keep loading even when a message points to a record that has already been deleted. This prevents users from seeing a generic fetch error and helps preserve access to their message history.

Original PR description

Before this commit, when a message notification from inbox or history has its related record deleted, the user couldn't load inbox or history. Steps to reproduce: - Have mitchell admin receive…

Before this commit, when a message notification from inbox or history has its related record deleted, the user couldn't load inbox or history.

Steps to reproduce:
- Have mitchell admin receive notification in Odoo
- Install `mail_group`
- Wait a few seconds to receive following user_notification from mail group:
```
on My Company News
Hello,
You have messages to moderate, please go for the proceedings.
```
- Go to related record then delete it
- Go back to inbox or history

=> One of them show `An error occurred while fetching messages.`

This happens because the related record is not a `mail.thread`, but still creates some `mail.message` to send user notifications.

`mail.thread` cascade delete the messages in message list, but threadless records do not. Because the related record is deleted, these messages are attempted to be displayed in mailbox, but due to related record having no `display_name` by non-existing, the fetch data of inbox/history crashes with:
```
MissingError: Record does not exist or has been deleted
```

This commit fixes the issue by doing its best to show message even when the related record has been deleted.

opw-4546920

[FIX] account_edi_ubl_cii: fix FacturX validation issues

PR #219799

Coresaas-18.1account_edi_ubl_ciiMedium

FacturX e-invoices now include the expected XML namespaces and correctly identify SEPA Direct Debit as the payment method. This helps invoices pass external validation checks and reduces issues when customers or partners process compliant electronic invoices.

Original PR description

### Issue:
There are several issues with the XML of FacturX.

### Steps to reproduce:
- Create a partner with a direct debit mandate
- In the Accounting tab of the partner select "FacturX" as eInvoice format
- Create an invoice with this partner, pay with SDD, confirm
- Send to FacturX
- Verify the PDF with https://www.portinvoice.com/
	1 Missing namespaces
3. In the XML the code for the payment means does not adapt to the payment method: 42 (Payment to bank account) and not 59 (SDD)

### Cause:
1. The namespaces are not there ([doc](https://fnfe-mpe.org/factur-x/factur-x_en/)).
3. We always input "42" as payment mean

### Solution:
1. Added namespaces `xmlns:qdt="urn:un:unece:uncefact:data:standard:QualifiedDataType:100"` and `xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"`
3. Added the code "59" for SDD, a lot of codes could be added but this commit only handles this one

Ticket [link](https://www.odoo.com/odoo/project/967/tasks/4907827)
opw-4907827

Forward-Port-Of: odoo/odoo#218686
Forward-Port-Of: odoo/odoo#217763

* Problem: Since what has been described in https://github.com/odoo/odoo/pull/214134 and https://thuvienphapluat.vn/chinh-sach-phap-luat-moi/vn/ho-tro-phap-luat/chinh-sach-moi/82581/tu-ngay-01-7-2025-ca-nuoc-se-khong-con-quan-huyen Vietnam no longer have district and city in city no more (Before in Vietnam we will have Thu Duc City belong to Ho Chi Minh State or Thuy Nguyen City belong to Hai Phong), Therefore we need to update Sinvoice data for this to. * This commit remove BuyerDistrict parameter , beside using state in the district is totally wrong and for 'buyerCityName' accept city or state field because odoo user might leave the city empty and just input state Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#218984

Before this commit, when a message notification from inbox or history has its related record deleted, the user couldn't load inbox or history. Steps to reproduce: - Have mitchell admin receive notification in Odoo - Install `mail_group` - Wait a few seconds to receive following user_notification from mail group: ``` on My Company News Hello, You have messages to moderate, please go for the proceedings. ``` - Go to related record then delete it - Go back to inbox or history => One of them show `An error occurred while fetching messages.` This happens because the related record is not a `mail.thread`, but still creates some `mail.message` to send user notifications. `mail.thread` cascade delete the messages in message list, but threadless records do not. Because the related record is deleted, these messages are attempted to be displayed in mailbox, but due to related record having no `display_name` by non-existing, the fetch data of inbox/history crashes with: ``` MissingError: Record does not exist or has been deleted ``` This commit fixes the issue by doing its best to show message even when the related record has been deleted. opw-4546920

### Issue: There are several issues with the XML of FacturX. ### Steps to reproduce: - Create a partner with a direct debit mandate - In the Accounting tab of the partner select "FacturX" as eInvoice format - Create an invoice with this partner, pay with SDD, confirm - Send to FacturX - Verify the PDF with https://www.portinvoice.com/ 1 Missing namespaces 3. In the XML the code for the payment means does not adapt to the payment method: 42 (Payment to bank account) and not 59 (SDD) ### Cause: 1. The namespaces are not there ([doc](https://fnfe-mpe.org/factur-x/factur-x_en/)). 3. We always input "42" as payment mean ### Solution: 1. Added namespaces `xmlns:qdt="urn:un:unece:uncefact:data:standard:QualifiedDataType:100"` and `xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"` 3. Added the code "59" for SDD, a lot of codes could be added but this commit only handles this one Ticket [link](https://www.odoo.com/odoo/project/967/tasks/4907827) opw-4907827 Forward-Port-Of: odoo/odoo#218686 Forward-Port-Of: odoo/odoo#217763