Wednesday, May 21, 2025
8 changes · saas-18.3
Resolved issues and error corrections
The live chat bot now avoids adding the same restart message twice when events arrive in a different order. This prevents silent failures in automated checks and improves reliability of chatbot restart flows.
Original PR description
Before this commit, an error would occur if the "/chatbot/restart" rpc came after the bus notification related to the restart message. It occurs because the chat bot model pushes the restart message into the channel's message without checking if it was already done by the new message notification handler. Since the thread template sets the message id as a `t-key`, we cannot have the same message twice. This would lead to the chat bot flow tour failing silently on runbot when this happens. This commit ensures the restart message will only be added to the thread's message once. fixes runbot-181545 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
This fixes a compatibility issue that could prevent the Calendar app from installing correctly after recent changes to activity scheduling in Mail. It makes the Calendar setup more reliable for databases updated in stages, reducing installation errors for users.
Original PR description
Scheduler view in mail has been updated recently, trigerring an update of calendar view. However this may break installing new calendar override on old mail view. This happens if you have installed mail before the update, and install calendar after pulling updated code. We therefore update the xpath of override in calendar to be more resilient. Followup of odoo/odoo#210043
Importing product records that include sales or purchase tax fields now works correctly. This prevents users from encountering an error when re-importing exported product data with tax values.
Original PR description
Currently an error occurs when the user import the product record. Steps to Reproduce (to avoid step just try to import this…
Currently an error occurs when the user import the product record. Steps to Reproduce (to avoid step just try to import this [File](https://github.com/user-attachments/files/20360727/Product.product.template.1.xlsx)) : - Install the `account` module. - Go to Products > switch to `List View`, select a `product`, and click `Export` under the Actions. - In the Available Fields, search for `Sales Taxes` or `Purchase Taxes`, select either one, and then click `Export`. - In the Products, click Actions > Import Records, and upload the file that was recently exported. - Click import. `TypeError: Domain() invalid argument type for domain: None` This error occurs when a user imports a product template record and the system calls name_search to resolve tax_id values. When no domain is passed, it defaults to None, causing a TypeError. This commit ensures that when the system calls name_search to resolve tax_id values without a domain, an empty domain ([(1, '=', 1)]) is used instead to prevent the error. sentry-6616172972 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The CRM quick create form no longer shows recurring revenue fields when the recurring revenue option is not enabled. This prevents sales users from seeing irrelevant fields and keeps lead creation aligned with the company’s configuration.
Original PR description
Fix the recurring revenue fields that were visible in the quick create form even though the recurring revenue option wasn't activated. The group was missing after a quick create form improvement. related: odoo/odoo#206314 Task-4796880 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix updates automated checks for Avatax sales tax calculations after changes to how down payments and global discounts are rounded per line. It helps ensure tax-related sales workflows remain reliable and prevents false test failures in future releases.
Original PR description
…t with round per line opw-4685953
Appointment pages with no available staff or resources now show the unavailable slot message only once. This keeps the booking page clearer for visitors and avoids confusion when no appointments can be scheduled.
Original PR description
Reproduce: Check the front page of an appointment type with no resources or staff users. This commit avoids duplicating the ‘No slot’ message on the front page of appointment types for which there is no slot available. related: odoo/enterprise@36da382fceba76f3de69306e24c9c6fa018cde9f Task-4750234
Pinning messages in Discuss now works even when the message has no linked thread available. This prevents a user-facing error and makes the message pinning action more reliable.
Original PR description
**Before this PR:** Pinning a message would throw an error if the associated thread was not present on the message. **After this PR:** This commit ensures that pinning a message works properly. **Task**-4805076
The IoT box setup flow no longer asks users to configure a Point of Sale when no active Point of Sale is available. This removes a confusing popup that could not be completed and makes the pairing process smoother for businesses without Point of Sale configurations.
Original PR description
Before this commit, if you paired an IoT box with no Points of Sale configured, you would still get the popup prompting you to autoconfigure your IoT box with a PoS. However, since you have no PoS you cannot fill in the required field and have to dismiss the popup. After this commit, we only open the autoconfigure popup if there is at least one active PoS available. task-4797331