Tuesday, February 10, 2026
32 changes · saas-19.1
New functionality added to Odoo
This update adds Thai translations for key chart of accounts elements (COA, taxes, and asset models) within the Odoo accounting module for Thailand. This ensures accurate reporting and financial data management for Thai businesses using Odoo. The changes were made to comply with Thai tax regulations and provide a better user experience for Thai-speaking users.
Original PR description
The following files are updated with the respective Thai translations: - COA: name, description - Taxes: name - Tax Group: name - Asset model: name Task-5875167 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#247116
Enhancements to existing features
This update addresses issues with the Belarusian Chart of Accounts (COA) in Odoo, specifically removing duplicate accounts and correcting inappropriate account types. This ensures accurate financial reporting and aligns with Belarusian accounting standards, improving data integrity.
Original PR description
- Currently, l10n_id COA has unacceptable account types for some accounts - There are also duplicate accounts since data for such accounts exists in chart template, but Odoo also creates for them Task-[5360134](https://www.odoo.com/odoo/project.task/5360134?debug=assets) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#246247
Resolved issues and error corrections
This update fixes an issue where TDS report amounts were incorrectly displayed as negative values in version 19.1. The fix adds a necessary negative sign prefix to the report formulas, ensuring TDS amounts are shown accurately as positive values, aligning with previous versions.
Original PR description
**Steps to reproduce:** * Install the **l10n_in** module. * Create vendor bills with applicable **TDS taxes** (e.g. Section **194C**, **194A**, **195**). * Post the bills. * Go to **Accounting → Reporting → TDS Report**. **Observed behavior:** * TDS amounts are displayed as **negative values** across all sections (192, 193, 194A–Q, 195, etc.). * This differs from versions up to **18.3**, where TDS amounts were shown as positive. **Cause:** * In v19, the automatic **+/− sign handling** was removed from the tax grid logic. [REF](https://github.com/odoo/odoo/commit/17a6117ed88c29b5bc4db0c872bcdbc109a7d98b) * TDS report formulas were missing an explicit **negative sign prefix**, causing amounts to appear inverted. **Fix:** * Add the required **negative sign prefix** to all TDS section formulas in `account_tax_report_tds_data.xml`. * Ensures TDS amounts are displayed as **positive values**. * Applies to all TDS sections. opw-5502385 Forward-Port-Of: odoo/odoo#247123
This update enhances the bank reconciliation feature by prioritizing key information like date, label, and balance at the top of the list view. It also optimizes scrolling within the table, ensuring a smoother and more user-friendly experience for managing bank statements.
Original PR description
1. The bank statement line info (date, label and balance) are moved to the top now. 2. Scrolling only applies to the table rows (other elements are fixed). task-5212851 Forward-Port-Of: odoo/enterprise#103709
This update resolves an issue preventing users with restricted company access from successfully reloading translations. The fix bypasses a privilege check on static data retrieval, allowing the translation reload process to continue. This ensures a smoother experience for all users, regardless of their company access permissions.
Original PR description
When a user doesn't have access to all companies, he couldn't reload the translation terms. However, the exception occurs in the call to _get_chart_template_data, which doesn't especially require privileges, because it is static data. With this commit, we bypass the lack of company access to retrieve this data, and let the user continue the language reloading process. Task-id: [5916490](https://www.odoo.com/odoo/project.task/5916490) Forward-Port-Of: odoo/odoo#247602 Forward-Port-Of: odoo/odoo#247540
This update resolves an error that occurred when disabling a module (like 'Snailmail') and sending an invoice. The issue stemmed from how Odoo stores company-dependent selection values in its database. The fix ensures accurate comparisons during module removal, preventing the error and allowing invoices to be sent correctly.
Original PR description
Currently, an error occurs when a company-dependent selection field (e.g. invoice sending method) keeps a value after the related module is uninstalled. **Steps to Reproduce:** 1. Install the…
Currently, an error occurs when a company-dependent selection field (e.g. invoice sending method) keeps a value after the related module is uninstalled. **Steps to Reproduce:** 1. Install the Accounting app. 2. Disable 'Snailmail' from settings. 3. Send any invoice, make sure wizard Print & Send has selected "by Post" option. 4. Click on the Send button. **Error:** `AssertionError` **Cause:** Fields defined with `company_dependent=True` are stored as property fields rather than regular values. In PostgreSQL, these fields are stored as **JSONB** values keyed by company id. When a selection value is removed (e.g. during module uninstallation), it attempts to compare the JSONB column directly with a string value, resulting in an invalid comparison and triggering the error. - [1] **Fix:** Update the SQL query to extract the value for the active company using JSON operators (->>), ensuring correct comparison with the expected selection value. [1] - https://github.com/odoo/odoo/blob/92a9f6b19670685dfe9fb1714bf01449768e5f62/odoo/addons/base/models/ir_model.py#L1812-L1815 sentry-6970900918 Forward-Port-Of: odoo/odoo#246671 Forward-Port-Of: odoo/odoo#241248
This update resolves a technical issue preventing the correct Open Graph description from being generated for card campaigns when previewing or sharing. The fix ensures that campaign details are properly displayed on social media platforms, improving campaign visibility and user experience. The problem stemmed from a discrepancy in how campaign data was passed to the template.
Original PR description
**Current Behavior:** description is not available for the Crowler <img width="1159" height="802" alt="image" src="https://github.com/user-attachments/assets/2979f413-6487-4f44-993c-b9a806e0d0ef" />…
**Current Behavior:** description is not available for the Crowler <img width="1159" height="802" alt="image" src="https://github.com/user-attachments/assets/2979f413-6487-4f44-993c-b9a806e0d0ef" /> **Steps to reproduce:** 1. Install `marketing_card` 2. Create a card campaign 3. Set Recipient, Post Link and Post Suggestion 4. Save and Preview 5. Copy the URL and replace `preview` with `redirect` 6. To reproduce in locale, in the `contoller` make the marketing_card.card_campaign_crawler template the only return 7. Now paste that URL in the browser **Issue** - The `<meta property="og:description">` tag is empty in inspect. It does not contain any content **Cause:** - The controller `card_campaign_redirect` passes the campaign's suggestion text to the view using the key `post_text`. However, the template `card_campaign_crawler` attempts to access `post_suggestion`, which is not present in the rendering context. **Solution:** - Update the controller to pass `post_suggestion` opw-5351041 Forward-Port-Of: odoo/odoo#238534
This update resolves a technical problem with the invoice report's HTML generation, specifically related to how payment terms were displayed. The fix ensures the report renders correctly and avoids potential errors. A new structure was also added to allow for future customization of the invoice terms.
Original PR description
This commit fixes an issue from report_invoice_document. In the “show_payment_term_details” t-if, there was a single td containing the `invoice_payment_term_id`. In another module,…
This commit fixes an issue from report_invoice_document. In the “show_payment_term_details” t-if, there was a single td containing the `invoice_payment_term_id`. In another module, `l10n_gcc_invoice`, we use this td in the following xpath: ```xml <xpath expr="//div[@id='total_payment_term_details_table']//td" position="before"> ``` The problem is that a td cannot be used outside of a table, which will cause incorrect HTML to be generated and therefore prevent Studio from working on it. One solution would be to replace the incorrect td with div, add a class `early_payment_discount` to it, and create a new customization that would target this time ```xml <xpath expr="//div[@id='total_payment_term_details_table']//div[@id='early_payment_discount']" position="before"> ``` In order not to break the current customization targeting the old incorrect td, we keep it but this time in a correct `table/tbody/tr/` and we do not display it in the final report. This will be removed in master. A new `oe_structure` has also been added below the Terms to allow people who want to add a field below to do so, as this is currently not possible. The only way to do this is to add a modification to the terms, which will only be displayed if this field is not empty because it is in a t-if. opw-5248145 opw-5879285 opw-5410727 opw-5476981 opw-5381578 opw-5369618 opw-5485437 opw-5498946 opw-5331519 Forward-Port-Of: odoo/odoo#235969
This update resolves security issues related to copying spreadsheets and dashboards. It simplifies the process by removing unnecessary security checks, allowing users to copy documents without requiring excessive permissions. This enhances usability and reduces potential security risks.
Original PR description
In order to be able to copy a spreadsheet or a dashboard on which the user has access to, without requiring a bunch of extra security rights, this fix removes the need to - when copying a dashboard, the copy of the field 'main_data_model_ids' that is only used on standard dashboards, would require the read right on ir_model for no good reasons - when copying any spreadsheety document (spreadsheet, dashboard, etc.) the remove the field spreadsheet_revision_ids from the data sent by the client, so the field security won't be triggered on an empty field 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#236542
This update fixes unreliable tests related to generating invoices for Malaysian and Taiwanese EDI systems. By explicitly defining tax calculations during invoice creation, the system now produces consistent and accurate invoices, resolving previous test failures.
Original PR description
[FIX] l10n_my_edi: more precise tests Improve reliability of Malaysian EDI module which work with xml files and bills by ensuring that we precise the tax we expect to see in the file when creating the invoice. issue-[237946](https://runbot.odoo.com/odoo/runbot.build.error/237946) related-odoo/odoo#227111 --- [FIX] l10n_tw_edi_ecpay: flaky tests not applying default taxes Improve reliability of Taiwanese EDI module by explicitly declaring taxes on invoice creation. We do this instead of relying on the default taxes to apply as they've caused flaky tests to fail. issue-[238485](https://runbot.odoo.com/odoo/runbot.build.error/238485) related-odoo/odoo#227111 --- runbot-[437842](https://runbot.odoo.com/runbot/bundle/master-l10n-my-edi-fix-tax-tests-437842) Forward-Port-Of: odoo/odoo#247716
This update corrects a visual issue with the mega menu on the website, specifically the alignment of toggle elements in desktop views. The fix ensures the mega menu appears correctly when using the 'Hamburger' template, resolving a misalignment that was present in mobile views. This improves the overall user experience for website visitors.
Original PR description
The PR [1] updated the templates for many headers to adapt the nav-item positions in desktop/mobile views. However, the hamburger menu was not updated correctly. In the desktop view, the mega menu toggle elements were not aligned properly (unlike in the mobile view). This commit fixes the PR by adding the necessary <xpath>. Steps to reproduce the issue: - Go to Website - Add a Mega Menu (edit menu) - Click on the header - Set the template to "Hamburger" - Set the text alignment to center for the desktop view => The mega menu toggle is not centered. task-5416632 --------------------------------------------- [1]: https://github.com/odoo/odoo/pull/225672 Forward-Port-Of: odoo/odoo#242475
This update resolves a display issue in the Point of Sale (PoS) system where users entering tip amounts with a comma as a decimal separator would see 'NaN' instead of the correct value. The fix ensures consistent handling of decimal separators during input and display, improving the user experience across different locales.
Original PR description
Steps to reproduce: 1. Set the decimal separator to ',' in Settings. 2. Open PoS, click Add Tip, and type a number followed by a comma. 3. Observe the input field displays NaN.00. Cause: A mismatch exists in how the tip value is handled between display and confirmation: - Display: NumberBuffer provides a localized string (e.g., '0,'). PaymentScreen passes this raw string directly to formatCurrency, which expects a standard numeric value. The internal cast fails on the localized separator, resulting in NaN. - Confirmation: onNewTip correctly uses Odoo's localized parseFloat utility, which handles the separator properly. Solution: Update the formatDisplayedValue callback in PaymentScreen to parse the buffer string using the localized parseFloat before passing it to formatCurrency. opw-5895622
This update simplifies the sales order reporting experience for subscription customers. The 'remaining hours' field, which could be misleading due to recurring delivery cycles, has been hidden when a sales order is linked to a subscription. This ensures a cleaner, more intuitive interface for our subscribers.
Original PR description
This change hides the remaining_hours_so field when the sales order line is linked to a subscription. Unlike standard service or time-based sales orders, where this field reflects the difference…
This change hides the remaining_hours_so field when the sales order line is linked to a subscription. Unlike standard service or time-based sales orders, where this field reflects the difference between the quantity ordered and the quantity delivered, the concept does not translate well to subscription logic. In the context of a subscription, the service is delivered on a recurring period (monthly, yearly, etc.). Delivery quantities continuously accumulate over time, and because the subscription renews indefinitely until cancellation, the “remaining hours” calculation quickly becomes misleading. In many cases it can drift into negative values, giving the impression of an error or over-consumption when, in reality, the subscription is simply following its recurring delivery cycle. To avoid confusing end-users and to maintain a clean, intuitive interface, we hide this field whenever the line is part of a subscription. opw-5246238 Forward-Port-Of: odoo/odoo#247694 Forward-Port-Of: odoo/odoo#241099
This update fixes an issue where the color picker for custom links in Email Marketing was hidden behind the link popover. The change adjusts a sequence number to ensure the color picker always appears above other overlays, allowing users to easily customize link colors. This improves the user experience for creating email campaigns.
Original PR description
Problem: In Email Marketing, the color picker for custom links is hidden under the link popover, making it unusable. Cause: Overlays added in mass mailing use a default sequence of 1050, while the color picker uses the default sequence (50). As a result, the link popover overlays the color picker. Solution: Force the color picker sequence to 1051 (mass mailing default + 1) so it always appears above other overlays, including the link popover. Steps to reproduce: - Open Email Marketing. - Add a link. - Change its type to custom to enable text and fill color options. - Open the color picker to change the text color. - Observe that the color picker is hidden by the link popover. opw-5866997 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#246080
This update allows users to switch between Invoice and Credit Note types on already processed accounting documents without needing to export and re-import. Previously, this process was blocked, requiring a cumbersome workaround. This change streamlines the accounting workflow and reduces user frustration.
Original PR description
Previously, switching an Invoice to a Credit Note (or vice versa) on a posted in_()/out_() move raised a blocking error. This forced users to export, delete, and re-import the document with the correct move type. This **PR** relaxes the restriction for posted moves whose sequence has been manually cleared, allowing the `Switch Invoice/Credit Note` action to proceed in that specific case. **task**-5905206 Forward-Port-Of: odoo/odoo#247729 Forward-Port-Of: odoo/odoo#247349
This update fixes a logging issue within the account_edi_ubl_cii module, ensuring that account numbers are now correctly recorded instead of attempting to recreate them. This enhancement improves data accuracy and traceability for financial transactions processed through UBL invoices, contributing to better financial reporting.
Original PR description
--- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#247693
This update resolves a minor calculation error in the Spanish tax (l10n_es) module related to 'Mod 390'. Specifically, it adjusts how balances from certain accounts are incorporated into the tax calculation, ensuring accurate reporting for Spanish businesses. This change was part of a larger effort to improve tax compliance.
Original PR description
In this commit: Fixing 390 computation: - Add balance from 27, 29, 649 and 31 to casilla 33. - Add balance from 28, 30, 650 and 32 to casilla 34. Related PR : https://github.com/odoo/enterprise/pull/105597 task-5732679 Forward-Port-Of: odoo/odoo#247823 Forward-Port-Of: odoo/odoo#245828
This update resolves an issue where users with the 'account_manager' group were encountering an Access Error when confirming invoices with auto-post enabled. The fix aligns access controls within the system, ensuring these users can properly manage invoice auto-posting functionality. This improves usability for a key user group.
Original PR description
When a user with `group_account_manager` only tries to confirm an invoice with auto post set, he gets an Access Error Steps: - Install only account - Create an invoice, set auto post to 'monthly' for example - Confirm -> AccessError Fix: In the `_check_user_access` method, we align with what we do in the `write` method to set the `is_user_able_to_review` variable opw-5886542
This update resolves an issue where clicking on a URL field in a form view unexpectedly opened a modal window. The fix ensures that clicking on the URL itself opens the link directly, without the unwanted modal display. This improves the user experience and prevents unnecessary distractions.
Original PR description
This commit fixes the obtrusive opening of the record's modal when middle clicking on a x2many's url field, in a form view. It applies the same logic as the one used for regular click (letting the url be opened, but not the modal). Note: originally spotted in the Runbot build error's form view (Builds page or Error content...). _Note to reviewers : doesn't look to apply to small screens, but not sure why... Feedback requested :pray:_ Forward-Port-Of: odoo/odoo#247815
This update resolves an issue where page options were incorrectly overwritten with default values when website elements (like headers or footers) weren't initially visible on the page. The fix ensures that page options are only saved when the related element is present in the website's display, maintaining user customizations. This prevents unexpected behavior and ensures consistent website designs.
Original PR description
### Issue: When saving a page while elements that use page options are not present in the DOM, the related page options are still saved. This ends up overriding the previously saved values with…
### Issue: When saving a page while elements that use page options are not present in the DOM, the related page options are still saved. This ends up overriding the previously saved values with defaults. ### Steps to reproduce (for the header): 1. Open any website page and enter edit mode. 2. Make sure both the header and footer are visible. 3. Set the header position to 'Hidden'. 4. From the 'Theme' tab, hide the header using the 'Show Header' option under 'Advanced'. 5. Select the footer and hide it using the 'Page Visibility' option. 6. Click on 'Save'. 7. Show the header again from the 'Theme' tab. A similar issue can be reproduced when the breadcrumb is not present on the page. ### Reason: When the relevant element is not present in the DOM, the `getVisibilityItem` method falls back to 'regular'. This fallback value overrides the previously saved option, even though the element was not available to compute its real state. ### Fix: Only compute and save page options related to an element when that element exists in the DOM. task-[5135925](https://www.odoo.com/odoo/action-4043/5135925) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#240065
This update resolves an issue where images linked within flex containers (like carousels) would shift left. The fix ensures that image alignment classes are correctly applied to linked images, maintaining their intended positioning. This improves the visual consistency of pages using flex layouts.
Original PR description
Steps to reproduce: - Add an image to a page and align it center or right via options. - Use the link option to wrap the image in a link. - In a flex container (e.g., carousel), the image alignment is lost. Before this commit, the alignment classes stayed on the image while the link wrapper was missing them, so linked images in flex layouts shifted left. After this commit, the link mirrors the image alignment classes when linking or changing alignment, keeping linked images positioned correctly. task-5187840 Forward-Port-Of: odoo/odoo#241721
This update resolves an error that prevented non-employee users from creating expenses from documents. The issue stemmed from a required field (employee_id) not being properly populated when the user wasn't linked to an employee record. The fix now displays a user-friendly error message instead of crashing the system.
Original PR description
Currently an exception is generated when the non-employee user tries
to generate expenses from the documents.
Steps to produce an error:
- Install the `documents_hr_expense` module without demo data
- Delete employee `Administrator`
- Upload any PDF/image file inside the company's `Internal` folder
- Click on the uploaded document and click on the `Create an Expense` button
Error: `ValueError: NotNullViolation('null value in column "employee_id" of ...`
This error occurs because `employee_id` is required when creating an
expense. Since the current user is not linked to an employee record,
`employee_id is` set to false, which causes the issue.
This commit resolves the issue by raising a `UserError` when the current
user is not linked to an employee.
sentry-7192984733
Forward-Port-Of: odoo/enterprise#106649
Forward-Port-Of: odoo/enterprise#104762This update resolves a test failure caused by a recent change to the _is_downpayment method. The commit simply adds the necessary update to the test suite to account for this new method extension, ensuring the system continues to function correctly.
Original PR description
The PR odoo/odoo#244443 introduces a new extension to the method _is_downpayment hence the test fails since it is not patched. This commit adds the new extension to the patched list. task-5135918 Forward-Port-Of: odoo/enterprise#106618 Forward-Port-Of: odoo/enterprise#105165
This update corrects a bug in the salary configurator where the fuel card benefit would incorrectly appear enabled if no company car was chosen. The fix ensures the field is properly initialized and remains disabled until a car is selected, preventing inconsistencies and ensuring accurate reporting.
Original PR description
On first load of the salary configurator, the fuel-card benefit could appear enabled even when no company car was selected. The dependency logic reacted to in-page changes but did not initialize the field correctly on page load. Initialize the fuel-card field from the current car selection and keep it non-selectable until a car is chosen to prevent inconsistent packages. task-5156562 Forward-Port-Of: odoo/enterprise#105037
This update adjusts the taxonomy used for Dutch tax reports to align with the latest NT20 standard. This change ensures continued compliance with Dutch tax regulations and maintains compatibility with older versions of the reporting system. No new functionality was added.
Original PR description
The taxonomy for the Dutch tax reports was updated from NT19 to NT20. There were only changes in the namespaces. Olders versions of the XBRL template are kept for backwards compatibility. task-4568359 Forward-Port-Of: odoo/enterprise#106732
This update simplifies the sales order reporting for subscription customers. The 'remaining hours' field, which could be misleading due to the recurring nature of subscriptions, has been hidden when a line is linked to a subscription. This ensures a cleaner, more intuitive experience for our customers.
Original PR description
This change hides the `remaining_hours_so` field when the sales order line is linked to a subscription. Unlike standard service or time-based sales orders, where this field reflects the difference…
This change hides the `remaining_hours_so` field when the sales order line is linked to a subscription. Unlike standard service or time-based sales orders, where this field reflects the difference between the quantity ordered and the quantity delivered, the concept does not translate well to subscription logic. In the context of a subscription, the service is delivered on a recurring period (monthly, yearly, etc.). Delivery quantities continuously accumulate over time, and because the subscription renews indefinitely until cancellation, the “remaining hours” calculation quickly becomes misleading. In many cases it can drift into negative values, giving the impression of an error or over-consumption when, in reality, the subscription is simply following its recurring delivery cycle. To avoid confusing end-users and to maintain a clean, intuitive interface, we hide this field whenever the line is part of a subscription. opw-5246238 Forward-Port-Of: odoo/enterprise#106807 Forward-Port-Of: odoo/enterprise#99813
This update resolves an issue where invoices with note or section lines at the top would cause export errors. The fix filters out these lines during currency rate calculations, ensuring invoices are correctly generated and sent for export. This prevents disruptions in invoice processing and reporting.
Original PR description
Before this commit: Steps 1) Create an invoice with a section or note line as the first line 2) Try to send or download the invoice => A traceback error is raised with the message: File "/home/odoo/src/enterprise/17.0/l10n_cl_edi_exports/models/account_move.py", line 68, in _get_inverse_currency_rate return float_round(abs(self.line_ids[0].balance / self.line_ids[0].amount_currency), 2) ZeroDivisionError: float division by zero This occurs because the `_get_inverse_currency_rate()` method is dividing over self.line_ids[0].amount_currency which is always equal to 0 in case of section or note line is added as a first line in the invoice. After this commit: Filtering out section and note lines in _get_inverse_currency_rate() to correctly calculation the inverse currency rate opw-5488417 Forward-Port-Of: odoo/enterprise#105774
This update fixes a reporting issue related to withholding taxes for Spanish businesses (l10n_es_reports). It ensures that specific tax types (347) are correctly handled in accounting moves, improving the accuracy of financial reports. This change addresses a technical detail impacting Spanish tax compliance.
Original PR description
- Moves that use withholding taxes should have the `type for 347` unselected and left blank. Related PR : https://github.com/odoo/odoo/pull/245828 task-5732679 Forward-Port-Of: odoo/enterprise#106889 Forward-Port-Of: odoo/enterprise#105597
This update resolves a potential instability issue in the document search functionality. The team corrected a programming error that could have resulted in missing context information, leading to errors. This change ensures a more reliable search experience.
Original PR description
**Before this commit** We were accessing the context on the `DocumentsSearchModel` object by using `_context`. This is incorrect because this property is private, and we can't guarantee its structure. In some cases, `_context` can be `null`, causing later issues when we try to access properties from the context. This was likely just a programming error, rather than intentional. **After this commit** We'll use the public API to get the context by accessing `context` on the `DocumentsSearchModel` object. The internals of that getter method can speak for themselves, but they are useful because they will give us a non-`null` context to work with. opw-5903535 Forward-Port-Of: odoo/enterprise#106751
This update simplifies the salary configuration process by hiding temporary offers created by the salary simulator from the user interface. These offers are automatically removed after a month by a scheduled task, so this change only improves clarity and prevents user confusion.
Original PR description
The salary simulator creates temporary offers to compute salary configurations. These offers must still exist for backend computations, as the configurator relies on them when updating results. Simulation offers are already cleaned up by a cron job after one month, so this change simply hides them from the list view to avoid user confusion. task: 5498873 Forward-Port-Of: odoo/enterprise#104493
This update fixes an issue where the system incorrectly calculated employee expenses when both a private and company car were declared as part of the same occupation. The change ensures accurate expense reporting by properly accounting for both vehicle types, improving payroll accuracy and compliance.
Original PR description
…occupation Forward-Port-Of: odoo/enterprise#106865
This update ensures that screenshots taken during the trial mode of Odoo Enterprise capture the correct end-result data. Previously, the system lacked the database URL needed to fetch this data. Now, the database URL is forwarded, allowing for accurate and complete trial mode screenshots.
Original PR description
During the trial flow, we don't know the db url when making the ws request. To still be able to take screenshots of the end result in trial mode, we forward the db_url when getting the result back.