Odoo Changelog — 2025-04-24

Thursday, April 24, 2025

3 changes · saas-18.1

Bug Fixes(3)

Resolved issues and error corrections

[FIX] l10n_in_withholding: fixed wrong validation on TDS apply

PR #204366

Coresaas-18.1l10n_in_withholdingMedium

Users can now apply TDS through the TDS Entry wizard even when the sender email is not configured. The system still records the chatter message for visibility, but it no longer requires email notifications to complete the TDS process.

Original PR description

Before this PR:
When applying TDS through the TDS Entry wizard, the system would attempt to send
a notification email when message is posted in chatter. If the sender's email
address was not configured in the system, it would raise a blocking error.
This prevented users from applying TDS without proper email configuration.

After this PR:
The TDS application process now works regardless of email configuration.
The chatter message is still created and visible in the UI, but the
email is no longer required for TDS application. This ensures that
TDS application is not blocked by email configuration.

Task-4680364

#TDS#withholding#email configuration#India localization

[FIX] point_of_sale: account for local timezone in orders report

PR #206827

Coresaas-18.1point_of_saleMedium

Point of Sale order reports now show the correct local date for orders made near midnight in non-UTC time zones. This prevents recent orders from being mislabeled as "Today" when they actually belong to the previous local day, improving reporting accuracy for stores operating across time zones.

Original PR description

Steps:
-----
1. Make an order from a time zone such that does not have the same local date as UTC. For instance, from Mexico at 23h.

The next day, the order date will say "Today" instead of yesterday's date.

Reason:
-------
We were not taking into consideration the current timezone when checking if the UTC date corresponds to the local today's date.

Fix:
----
Convert the UTC date to a local date before proceeding with our conditional checks.

opw-4699263

#point of sale#orders#timezone#reporting

[FIX] l10n_mx_edi: Fixing the complementos injector.

PR #83772

Enterprisesaas-18.1l10n_mx_ediMedium

This fix restores the automatic inclusion of Mexican invoice complements that could be skipped after a recent permission-related change. It helps ensure invoices generated in the Mexican localization remain complete and compliant when users send or print them.

Original PR description

In [PR 191823](https://github.com/odoo/odoo/pull/191823) in the comunity repo, a new functionality was added to allow a user with salesman permissions to send and print the invoice. However this change had unexpected effects in the mexican localization, precisely in the _clean_cfdi_values function which now removes all values from the dictionary that are not plain text. 

The complemento's injector was using the addenda value from the dictionary which was a recordset of the l10n_mx_edi.addenda model, with these changes, this recordset was removed from the dictionary, causing the complemento to never be added. 

To fix it, the values relevant to the complemento have been marked as unsudo, thus preventing them from being removed in the clean_cfdi_values function.

#mexico#invoicing#localization#compliance

Before this PR: When applying TDS through the TDS Entry wizard, the system would attempt to send a notification email when message is posted in chatter. If the sender's email address was not configured in the system, it would raise a blocking error. This prevented users from applying TDS without proper email configuration. After this PR: The TDS application process now works regardless of email configuration. The chatter message is still created and visible in the UI, but the email is no longer required for TDS application. This ensures that TDS application is not blocked by email configuration. Task-4680364

Steps: ----- 1. Make an order from a time zone such that does not have the same local date as UTC. For instance, from Mexico at 23h. The next day, the order date will say "Today" instead of yesterday's date. Reason: ------- We were not taking into consideration the current timezone when checking if the UTC date corresponds to the local today's date. Fix: ---- Convert the UTC date to a local date before proceeding with our conditional checks. opw-4699263

In [PR 191823](https://github.com/odoo/odoo/pull/191823) in the comunity repo, a new functionality was added to allow a user with salesman permissions to send and print the invoice. However this change had unexpected effects in the mexican localization, precisely in the _clean_cfdi_values function which now removes all values from the dictionary that are not plain text. The complemento's injector was using the addenda value from the dictionary which was a recordset of the l10n_mx_edi.addenda model, with these changes, this recordset was removed from the dictionary, causing the complemento to never be added. To fix it, the values relevant to the complemento have been marked as unsudo, thus preventing them from being removed in the clean_cfdi_values function.