The Mexican tax tariff fraction catalog has been updated to reflect the latest official classifications from April 2024. This ensures that product tariff codes used for Mexican electronic invoicing remain accurate and compliant with current government regulations.

The tariff fraction catalog has been updated
on April 2024:

https://www.snice.gob.mx/cs/avi/snice/ligie.info22.mod24.html

opw-3921546

Forward-Port-Of: odoo/enterprise#62638

This update fixes how test dates are handled in Mexico's electronic invoicing (EDI) system. Previously, test files contained hardcoded dates that could become outdated. Now the system uses dynamic dates that update automatically, and test validations properly ignore date variations to ensure tests remain reliable over time.

Custom and anytime appointment types are now unpublished by default so they don't appear on your website unless you explicitly make them visible. This prevents accidental public visibility of appointment types that aren't ready to be shared. Appointment types created directly from your website pages will still be published automatically since that action implies you want them public.

Since custom and anytime appointment types aren't visible on website pages, it makes sense to set their is_published field to False by default. The only exception when appointment types should be created with published flag is when it is being done from website page, since creating appointment from there implies their public visibility.

task-3944831

Corrected the description used in Mexican electronic invoicing (CFDI) when processing discount refunds. Previously, the system incorrectly labeled discounts as "merchandise returns" when they should be identified as discounts or bonifications. This ensures accurate tax documentation for Mexican customers receiving discounts instead of actual product returns.

- Create a credit note
- Add a product as a "Discount" and add the proper information
- Process it under the use "devoluciones, descuentos o bonificaciones" (G02)
- Check the generated XML

Issue: Under description, we report "devolucion de mercancias" which wrong, as the user is not returning anything, they´re only getting a discount.

opw-3902858

This update fixes an error message that appears when Amazon sales order picking synchronization fails. The improvement ensures users receive clearer, more accurate feedback when issues occur during the order fulfillment process with Amazon integration, helping teams quickly identify and resolve synchronization problems.

See also: https://github.com/odoo/odoo/pull/167738

This fix resolves an issue where demo data failed to load properly when installing localized payroll and HR modules in Odoo's SaaS environment. The problem affected multiple country-specific modules including Belgium, Kenya, Lithuania, Luxembourg, Morocco, Mexico, Netherlands, Poland, Romania, Slovakia, Australia, Switzerland, and the United States. Users can now successfully install these modules and have their demo data load without errors.

Steps:
- Create a database on SaaS
- Activate debug mode
- Load demo data if not enabled
- Install l10n_be_hr_contract_salary

Actual result:
- Module l10n_be_hr_contract_salary installed
- Demo data not loaded properly, traceback

Expected result
- Module l10n_be_hr_contract_salary installed
- Demo data loaded

opw-3930487

Forward-Port-Of: odoo/enterprise#63433
Forward-Port-Of: odoo/enterprise#63328

The Planning app's view menu order has been reorganized to prioritize the most commonly used views. Gantt, Pivot, and Graph views are now positioned after Kanban and List views, improving the user experience by making frequently accessed views more prominent.

Previously, Gantt, Pivot, and Graph views were listed before Kanban and List views.
In this commit, we've reordered based on priority.

Upgrade script:
No upgrade script is required as we've updated records added in this version

task-3902382

Forward-Port-Of: odoo/enterprise#61834

This fix resolves a technical error that occurred when updating bank statement records belonging to multiple companies with different countries. The issue prevented users from processing multiple company records simultaneously. The fix ensures all records are properly handled without errors.

When the `write` method is called with multiple lines belonging to multiple companies that have different countries, we get a `singleton error`.

We should instead loop on all line records in self.

Bug introduced in https://github.com/odoo/enterprise/pull/63356

runbot-66564

Fixed an issue where users could accidentally submit the appointment confirmation form multiple times by clicking the button repeatedly. The button now shows a loading state and becomes disabled after the first click, preventing duplicate submissions and the confusing error messages that resulted from them.

Purpose
=======
Prevent multiple submits of the attendee form when the user spam clicks on the "Confirm Appointment" button.

Specifications
==============
Spam clicking the submit button is submitting multiple times the form which redirects the user to the "Date & Time" step with a red banner indicating that another user already has reserved this time slot a few seconds ago.

Adding a loading effect on the confirmation button to disable it after a single click and inform the user that the form submission is correctly being processed.

Backport of: odoo/enterprise#58865

Task-3945177

This update corrects how debit note document types are assigned in the accounting system. Previously, the system was automatically setting a default document type for all debit notes, but this should only happen for companies operating in Peru. This fix ensures the correct behavior based on the company's location, preventing incorrect document type assignments in other regions.

Before this change we were always setting document type for the debit note by default, but this should only apply if from Peru

LATAM 1198

Forward-Port-Of: odoo/enterprise#63099

This fix resolves an issue where text entered in a many-to-one field would be lost when creating a new related record through Studio. The problem occurred when adding many-to-one fields to custom models created in Studio. By properly configuring the name field option, user input is now preserved when creating and editing related records.

Steps to reproduce
==================

- Create a new model with studio
- Go to the contaxt form view
- Add a new many2one field linked to the newly created model
- Exit studio
- Create a new contact
- Type something in the many2one field
- Click on Create an Edit

=> The name should be kept

Cause of the issue
==================

Studio models uses x_name as the _rec_name

opw-3919262

Forward-Port-Of: odoo/enterprise#63362
Forward-Port-Of: odoo/enterprise#62424

This fix corrects an issue with the eco voucher file exported through the Monizze integration in the Belgian payroll system. A required column was missing from the export file, which has now been restored to ensure proper processing of eco voucher data.

This will fix the file exported for the eco voucher with Monizze.

Task: 3895296

This update fixes error message handling in the Amazon sales integration when synchronizing picking operations. The improvement ensures that error messages are properly managed during the picking sync process, reducing confusion and improving the reliability of Amazon order fulfillment in Odoo.

This update removes an unnecessary work location column from the employee list view when the homeworking module is active. Since remote workers don't have a single physical work location, this column is now hidden to reduce clutter and improve the clarity of employee information displays.

Removed a work location column in the employee list view that is not relevant when the homeworking module is installed.

Task-3933447

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

This fix resolves a critical error that occurred when a livechat visitor without an account attempted to escalate from a chatbot to a human operator. Previously, the system would crash with an attribute error. After this fix, the fallback to a human operator now works smoothly, ensuring visitors can always reach support when needed.

Description of the issue/feature this PR addresses:
Livechat is set up with a Chatbot with a fallback to an operator.
When a visitor visits a website with the Livechat and the visitor is not connected to an account, when falling back to the operator, an error occurs :
`AttributeError: 'discuss.channel' object has no attribute 'livechat_visitor_id'`

Current behavior before PR:
When a visitor visits a website with the Livechat and the visitor is not connected to an account, when falling back to the operator, an error occurs :
`AttributeError: 'discuss.channel' object has no attribute 'livechat_visitor_id'`

Desired behavior after PR is merged:
The chatbot falls back to the human operator.

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