Tuesday, February 4, 2025
8 changes · saas-18.1
Resolved issues and error corrections
This fix restores a missing internal step in the eLearning activity feature. It helps ensure course-related activity behavior remains consistent and avoids errors caused by skipping shared processing.
This fix prevents online course tests from accidentally using demo course data when validating a learner journey. It makes the test results more reliable by ensuring the intended test course and its comments are checked consistently.
Original PR description
The slide course member tour tests use a channel called `Basics of Gardening - Test`. When the course is completed, clicking on `End course` will redirect the user to the courses home page. Since there is already a course (from demo data) called `Basics of Gardening`, the selector in the tour test actually selects this as the first match not the test course and the tour continues with the wrong course. It doesn't crash because both demo and test courses are public, so it's possible for demo and portal users to access them anyway and add/update a comment is done on the demo course. By this commit: - Demo data is removed in the tests to ensure that there is no collision between demo data and test data. - Since there are no predefined messages in the test data (the tour flow relied on the demo data messages before), the `update` does not happen in the tour without demo data. Some extra steps are also added to check the update message .
This update fixes a failing automated check in the Point of Sale area. It helps keep the release validation process reliable, reducing the chance of delays caused by test errors.
Original PR description
Fix error runbot. Error runbot: 111976
Messages that contain only attachments now show the seen indicator, so users can tell when recipients have viewed them. This fixes a gap where read status was missing because there was no message text area to display it.
Original PR description
Before this PR, messages with only attachments did not show the seen message indicator. It is shown on the message body, which is missing in this case. This PR shows the message seen indicator inside the attachment list if it's the only content of the message.
This fixes an issue in the WinBooks import wizard where the default account was passed in the wrong format. The change helps prevent import setup errors and keeps the accounting import flow working as expected.
Original PR description
Since this [commit](https://github.com/odoo/enterprise/commit/a067f8421e3058507f3e25088d94e33122ecdd1e#diff-0e37484af3f832073947594d460e7a6039698cbee82232e2c9b35c0aff3a59b3), the `default_account_id` is set as an `account.account` record, instead of its `id`. no-task
This fix removes a duplicate currency reference from the Belgian Intrastat report logic. The change reduces unnecessary internal complexity without changing the report's intended business output.
Original PR description
"currency_id_of_value_currency" is redundant with "invoice_currency_id"
Service invoices in Brazil no longer show a warning about a product origin field that only applies to goods. This avoids confusing users with irrelevant compliance prompts for service products, where the field is hidden and not required.
Original PR description
Don't warn if products used on service invoices have an empty l10n_br_source_origin field. It's only needed for goods, and is in fact hidden on service products. opw-4536842
This change prevents an error when viewing cost analysis for manufactured products with work orders. It ensures the report uses the correct manufacturing order information, so users can open cost analysis reliably after validating production.
Original PR description
Steps to reproduce the bug: - Create a storable product “P1” - Component: C1 - Operation: OP1 - Create a manufacturing order to produce one unit of P1 - Confirm the MO and validate it - Go to the product P1 -> Cost analysis Problem: a traceback Is triggered: self._obj.execute(query, params) psycopg2.errors.UndefinedColumn: column wo.product_id does not exist LINE 2: wo.product_id, ^ HINT: Perhaps you meant to reference the column "wo.production_id". The field `product_id` in `mrp_workorder` is a related field (`related='production_id.product_id'`), meaning it does not exist as a physical column in the database. The SQL query was directly referencing `wo.product_id`, which caused the error. Solution: Instead of `wo.product_id`, the query now retrieves `product_id` from `mrp_production` opw-4525278