Daily updates from Odoo
Saturday, January 24, 2026
45 changes
19 changes
Enhancements to existing features
This update enhances the testing process for paying invoices with bank statement lines within the Odoo accounting module. The change introduces a reusable test helper, streamlining testing and improving the reliability of invoice payment scenarios. This ensures accurate and consistent invoice payment processing.
Original PR description
Forward-Port-Of: odoo/odoo#244377 Forward-Port-Of: odoo/odoo#244281
Resolved issues and error corrections
This update corrects a bug that prevented users from adding inputs to payslips. The fix ensures that the correct salary input domains are applied across all relevant models, allowing for accurate payslip creation. This resolves an issue where only employee-specific salary inputs were displayed.
Original PR description
When trying to add Inputs for a payslips none appear as the domain was incorrect and only showed salary inputs for use in the employee. This is fixed in this commit by adding to the domain en each specific model. task-5486091 Forward-Port-Of: odoo/enterprise#103986
This update addresses a technical adjustment to the checksum within the l10n_eu_iot_scale_cert module. This change was necessary due to a recent code update to resolve a bug. Updating the checksum ensures the integrity of the module's data and maintains system stability.
Original PR description
Checksum needs to be updated as the code of the scale changed for a bugfix Cummunity PR: https://github.com/odoo/odoo/pull/245048
This update corrects a technical issue within the l10n_tr_nilvera_einvoice module. The previous method calls ('get_param' and 'set_param') were removed, and this change ensures they are replaced with the correct, specific types as defined in the Odoo codebase. This ensures the module functions correctly and avoids potential errors.
Original PR description
The methods don't exist anymore. They should be replaced by the specific types. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update fixes a visual issue in the VoIP demo mode, ensuring a helpful tooltip is displayed when hovering over the 'Demo Mode' indicator. Previously, the tooltip wasn't correctly shown, causing confusion for users. This change clarifies the demo mode functionality and improves the user experience.
Original PR description
## Context There are two modes in VoIP: _Production Mode_ and _Demo Mode_. Demo Mode enables you to simulate a call in the UI without actually calling someone. This is useful for showing customers…
## Context There are two modes in VoIP: _Production Mode_ and _Demo Mode_. Demo Mode enables you to simulate a call in the UI without actually calling someone. This is useful for showing customers the features and for developers to test the UI 💡 Though useful, this feature can be confusing. Users may not realize they aren't in Production Mode, and developers may forget to switch back to Demo Mode when testing the UI. 535a7aef3e410d997baa093cc111527814c29253 improved the situation by displaying "Demo Mode" in the Softphone header when Demo Mode is enabled. It was intended to include a tooltip explaining how to configure Production Mode when hovering over it. However, although the tooltip text is present in the code, it was not correctly mapped to the "demo indicator" ¯\\\_(ツ)\_/¯ ## In this PR After this commit, - the tooltip text is correctly provided to the "demo indicator", enabling it to be displayed on hover; - the tooltip text is slightly reworded in the hope of making it clearer. [Task-5804537](https://www.odoo.com/odoo/project/5778/tasks/5804537) Fix https://github.com/odoo/enterprise/pull/95742
This update fixes an issue where VAT import taxes were incorrectly mapping to accounts in the Odoo system. The change in a key account number required updating the default account used for taxes like purchase import VAT. This ensures accurate journal entries and proper financial reporting for VAT transactions.
Original PR description
Due to the change of account 33312 from liability to payable, the journal entries generated when creating bills with VAT import taxes were incorrect. This fix updates the default account on the following taxes: - tax_purchase_import_10 - tax_purchase_import_8 - tax_purchase_import_5 task-5695253 Forward-Port-Of: odoo/odoo#245082 Forward-Port-Of: odoo/odoo#244434
This update resolves a potential infinite loop issue that could occur when generating product attribute combinations, specifically with multi-checkbox attributes. The fix prevents redundant calculations by excluding lines with no values, ensuring stable and reliable product configuration.
Original PR description
Before this commit, having a `product.template.attribute.line` with zero `product.template.attribute.value` records might cause an infinite loop if this **multi-checkbox** attribute wasn't in the end…
Before this commit, having a `product.template.attribute.line` with zero `product.template.attribute.value` records might cause an infinite loop if this **multi-checkbox** attribute wasn't in the end of the list.
Suppose the order was arbitrary and we are generating combinations for two lines (the order here is important):
- Line (A) -> [] (multi checkbox type)
- Line (B) -> [attr_1, attr_2]
- The possible combinations are {(attr_1), (attr_2)}.
After generating the second combination the following 2 procedures happen.
- The value_index_per_line[1] will be resetted to -1,
- The line_index will decrement from 1 to 0.
Now, since the first line doesn't have any values, it will be skipped and the line_index will be incremented to 1.
This results in the redundant generation of the same combination, triggering an infinite loop.
Since this method yields a recordset of `product.template.attribute.value` model and the **multi-checkbox** attribute doesn't have a value being passed to the method anyways, we can exclude the lines that doesn't have values for the algorthim not to be stuck in an infinite loop.
opw-5267179
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#241557This update corrects a technical issue preventing invoices (specifically credit notes) from being properly validated for export to the Danish tax system (Nemhandel). The previous system incorrectly assumed the 'PrepaidAmount' field was always empty, leading to validation failures. Now, the system only removes this field when its value is actually zero, ensuring accurate invoice export.
Original PR description
To reproduce: create an invoice that is reconciled (typically a credit note) before Send&Print. Check the validity of the xml with a schematron => it fails due to the value of the PrepaidAmount The node PrepaidAmount gets removed because it was wrongly thought to be always empty. We now only remove it if the value is at 0. 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#242497 Forward-Port-Of: odoo/odoo#242008
This update corrects a display issue where the inventory count badge in the Barcode app incorrectly showed a request count for one company even when no count existed for another. The fix ensures the badge accurately reflects the current inventory count for the company the user is currently operating within, improving data accuracy and reporting.
Original PR description
Steps to reproduce: - Create two companies (A and B) - Create a storable product "P1" - Log in with company A - Update the on-hand quantity of P1 in company A only - From Physical Inventory, request an inventory count for P1 - Switch to company B - Open the Barcode application Problem: The inventory count badge in the Barcode main menu displays a request count created for company A, even though no inventory count exists for company B. The badge incorrectly shows "1" instead of "0". opw-[5472031](https://www.odoo.com/web#id=5472031&view_type=form&model=project.task) Forward-Port-Of: odoo/enterprise#104065
This update resolves a technical issue preventing grouping within the planning module's slot templates. The fix ensures parameters are passed to the correct order during data processing, enabling proper grouping functionality. This improves the reliability and usability of the planning feature.
Original PR description
Before this commit, it was impossible to group by on any field in `planning.slot.template` model, because the parameters given to the parent method of `formatted_read_group` method were not given into the right order. This commit makes sure the order is respected. Forward-Port-Of: odoo/enterprise#105211
This update removes the Sign menu item from Odoo's Discuss channels. Previously, this menu was incorrectly displayed, which was confusing for users. This change ensures Discuss channels function as intended, focusing on mail threads instead of offering the Sign feature.
Original PR description
Currently, the Sign menu item is displayed in discuss channels, which is not making sense. This was due to an incomplete check in the isDisplayed method of the SignRequestCogMenu component. To fix this, we enhance the condition to ensure that the menu item is not displayed when the current model is 'discuss.channel'. Discuss channels inherently support mail threads, but should not have the Sign menu item. task-5494751 Forward-Port-Of: odoo/enterprise#105201
This update resolves an issue where the l10n_cl_edi module was incorrectly creating duplicate vendor bills when receiving identical XML invoices via the incoming mail server. The fix prevents these duplicates from being generated, ensuring accurate billing records and avoiding potential accounting errors. This was triggered by a configuration setting within the Vendor Bills journal.
Original PR description
Steps to reproduce: - With a CL Company setup - Configure an incoming mail server with DTE server option enabled - In Vendor Bills journal, enable 'Use Documents?' - Receive the same XML twice via the incoming mail server - Check created vendor bills Issue: There will be duplicated bills. Each duplicate will show the message 'E-invoice already exist: nnnnn' However, the system should avoid duplicates from being created. opw-5362664 opw-5409700 Forward-Port-Of: odoo/enterprise#103211
This update fixes a potential issue in the Swiss payroll reporting process. Previously, a snapshot was always created, even if one already existed, leading to unnecessary data duplication. This change ensures snapshots are only created when needed, improving efficiency and accuracy of reporting.
Original PR description
Forward-Port-Of: odoo/enterprise#105258 Forward-Port-Of: odoo/enterprise#105135
This update resolves a problem where a test tour incorrectly failed when using the US tax report. The fix ensures the tour doesn't rely on outdated date assumptions and handles different localization configurations correctly, particularly when the 'Tax Report' localization isn't installed. This ensures consistent test results across various Odoo environments.
Original PR description
- The tour shouldn't run if a localization with 'Tax Report' for the country is not installed (i.e. l10n_us_account) - Dynamic Javascript dates calculation don't mix well with Python's freeze_time running in the "No future" 2026 preparation build, so I froze the time in the Python test but resorted to hardcode the Javascript dates. - No need to check the position of the column "Column 1". In debug mode for the tour, there will be the "Debug" column where the info about the computations are shown, so it won't be the last. We just need to see that it shows, after all. Runbot error [link](https://runbot.odoo.com/odoo/error/234624) runbot-234624 Forward-Port-Of: odoo/enterprise#101689
This update resolves an issue where the 'Pending' button in manufacturing orders incorrectly stopped productivity records for all employees involved, instead of just the current one. The fix ensures that only the productivity record associated with the currently logged-in employee is stopped when the 'Pending' button is clicked, improving order management accuracy.
Original PR description
Steps to reproduce the bug:
- Create a storable product P1 with the following BoM:
- Create a new operation OP1
- Create a manufacturing order to produce one unit of P1
- Confirm the manufacturing order
- Log in as Mitchel (admin) and start OP1
- Log in as Marc (demo) and also start OP1
- Click on Pending
Problem:
Both “mrp.workcenter.productivity” records are stopped, instead of stopping only the one linked to
The `button_pending` method was stopping productivity records for all employees linked to the work order.
opw-5453752
Forward-Port-Of: odoo/enterprise#105238
Forward-Port-Of: odoo/enterprise#103553This update allows users to modify fields within the 'stock.quant' view through Odoo's Studio interface, even if those fields weren't initially configured with an XML ID. Previously, this wasn't possible, but now Studio-generated or customized fields are correctly recognized and permitted.
Original PR description
In versions prior to 18.3, the “stock.quant” view did not have an “xml_id”, which prevented it from being modified through Studio. However, starting from version 18.3 and specifically since this commit: https://github.com/odoo/enterprise/commit/f4a4d54d45392c2ba46a123d4951f8b4468c5cba it is now possible to modify views through Studio even if they don't have an xml_id. But in the 'stock.quant' view, we perform a check at creation time to ensure that the field is among the allowed fields. Fields coming from Studio or from a customized view should, however, be ignored by this check and allowed. opw-5107591 Forward-Port-Of: odoo/odoo#230126
This update removes a restriction that previously limited the use of journal accounts for reconciliation. Previously, certain accounts couldn't be used as default debit or credit accounts within journals. This change provides greater flexibility for users to manage their accounting data, simplifying reconciliation processes.
Original PR description
Previously, a constraint prevented accounts from being non-reconcilable if they were used as default debit/credit accounts involved in journals. This behavior is too restrictive. This commit removes the constraint. task-5254202 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#245508 Forward-Port-Of: odoo/odoo#244398
This update resolves a customer complaint regarding test data containing the name "Deco Addict". The system has been updated to consistently use "Acme Corporation" in demo and test environments, preventing user confusion. This ensures a cleaner and more accurate demonstration of our software.
Original PR description
A company that happens to be named "Deco Addict" has complained some of our users thought they had business with them due to test and demo data containing that name. It will now be named Acme Corporation. task-5865502 Forward-Port-Of: odoo/odoo#245658 Forward-Port-Of: odoo/odoo#245205
This update resolves a customer complaint regarding test data. The name "Deco Addict" has been replaced with "Acme Corporation" in demo and test environments to ensure accurate representation and avoid confusion for users. This change improves the user experience and data integrity.
Original PR description
A company that happens to be named "Deco Addict" has complained some of our users thought they had business with them due to test and demo data containing that name. It will now be named Acme Corporation. task-5865502 Forward-Port-Of: odoo/enterprise#105446 Forward-Port-Of: odoo/enterprise#105151
1 change
Resolved issues and error corrections
This pull request resolves a customer complaint regarding demo data. The name "Deco Addict" was replaced with "Acme Corporation" to prevent users from mistakenly believing they had a business relationship with this company. This ensures a cleaner and more accurate demo experience.
Original PR description
A company that happens to be named "Deco Addict" has complained some of our users thought they had business with them due to test and demo data containing that name. It will now be named Acme Corporation. task-5865502 Forward-Port-Of: odoo/enterprise#105440 Forward-Port-Of: odoo/enterprise#105151
4 changes
Enhancements to existing features
This update removes unnecessary fields from CRM email templates, streamlining data collection and ensuring more information is captured in chatter. This enhancement avoids duplicate entries and allows for data gathering without requiring users to upgrade their systems. It’s a small improvement that boosts the efficiency of our CRM processes.
Original PR description
- Remove newly added fields that can be replaced by existing keys present in `iap_mail.enrich_company` template to ensure we get more data in chatter without upgrade and avoid duplicate entries IAP PR: https://github.com/odoo/iap-apps/pull/1390 Forward-Port-Of: odoo/odoo#245068
Resolved issues and error corrections
This update fixes issues related to error handling when processing HR tax documents, particularly those formatted as UBL invoices. It ensures compatibility with a related UBL tax extension module and provides clearer warnings for import issues instead of silently skipping documents.
Original PR description
- Improving error handling for various requests - Adjusting XML generation to not conflict with `account_edi_ubl_cii_tax_extension` if it is installed - Adding a separate test for HR:E category taxes - Replacing skipping import of not successfully fiscalized document with warnings displayed on the moves after import task-none --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#245028
This update resolves a customer complaint regarding test data using the name "Deco Addict". All instances of "Deco Addict" have been replaced with "Acme Corporation" across various Odoo modules to ensure accurate demo and test environments. This improves the user experience and avoids potential confusion.
Original PR description
A company that happens to be named "Deco Addict" has complained some of our users thought they had business with them due to test and demo data containing that name. It will now be named Acme Corporation. task-5865502 Forward-Port-Of: odoo/odoo#245623 Forward-Port-Of: odoo/odoo#245205
This pull request resolves a customer complaint regarding demo data. The name "Deco Addict" was replaced with "Acme Corporation" to avoid confusion among users. This ensures a cleaner and more accurate demo experience.
Original PR description
A company that happens to be named "Deco Addict" has complained some of our users thought they had business with them due to test and demo data containing that name. It will now be named Acme Corporation. task-5865502 Forward-Port-Of: odoo/enterprise#105421 Forward-Port-Of: odoo/enterprise#105151
2 changes
Resolved issues and error corrections
This pull request resolves a customer complaint regarding test data. The name "Deco Addict" was replaced with "Acme Corporation" in demo and test environments to avoid confusion and ensure a better user experience. This change improves data clarity and aligns with our standards for demo data.
Original PR description
A company that happens to be named "Deco Addict" has complained some of our users thought they had business with them due to test and demo data containing that name. It will now be named Acme Corporation. task-5865502 Forward-Port-Of: odoo/enterprise#105330 Forward-Port-Of: odoo/enterprise#105151
This update resolves a bug that occurred when generating reports for German-speaking customers. Specifically, a division-by-zero error was triggered when currency exchange differences (where the amount was zero) were present on move lines. The fix ensures these lines are now handled correctly, preventing report generation issues.
Original PR description
On move lines with zero `amount_currency` ( ex. currency exchange difference ), `_get_product_base_line_currency_rate` returns 0 currency rate which causes a division by zero error. Ignore the rate for lines with zero `amount_currency` opt-5358954 Forward-Port-Of: odoo/enterprise#105360
13 changes
New functionality added to Odoo
This update enhances the display of property values within list views in Odoo. It automatically creates new columns to show property data, making it easier for users to see relevant information. However, sorting and editing of these columns are currently not supported.
Original PR description
Adds columns in the list view for properties. Dynamically create 'fields' for list views that copy the characteristics of their 'properties' field. Allows for seamless display of property values in the list view. ## Notes These columns cannot be sorted (requires python ORM modifications) These columns cannot be edited (not easily achievable) task #2980121 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Enhancements to existing features
This update changes how binary data is stored in the Odoo database. Previously, data was encoded in base64, which used more space. Now, binary data is stored directly as bytes, optimizing storage and preparing for future cache changes. This improves database efficiency.
Original PR description
Since we are going to move to a raw bytes representation in the cache, let's store binary fields that are not attachments as raw bytes in the database instead of storing them in base64-encoded raw bytes (which just use more space). task-4251301 https://github.com/odoo/upgrade/pull/8995 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update simplifies the naming of a key view within the Sale CRM module. Specifically, the external ID '123' has been removed from the inherited view. This change improves the organization and clarity of the Odoo codebase, without impacting any user-facing functionality.
Original PR description
Before this commit, the inherited view is not named in a good way. After this commit, 123 will be removed from the external id of the inherited view. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update enhances email confirmation messages sent after resource bookings. Now, multiple confirmation emails are sent for bookings involving multiple resources, and the final email includes a note linking it to the other related emails. This improves clarity and reduces confusion for users.
Original PR description
A change in the data structure to represent resource bookings requires we update the mail template that uses them. As bookings for multiple resources will now send multiple confirmations we add a note in the last email to specify the other emails are linked. task-338900
Resolved issues and error corrections
This update resolves a technical issue that was causing tests to fail due to dynamic date usage. The test now utilizes a freeze-time mechanism, ensuring consistent and reliable test results. This change improves the stability and reliability of the employee version timeline feature.
Original PR description
As runbot faketimes test fail because the usage of dynamic dates now the test uses freeze_time Task#5717031 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#244540
This update fixes an issue where clicking links within the Odoo chat window on mobile devices caused the chat window to remain open and block the new page from appearing. The change now automatically folds the chat window after a link click, ensuring users can easily view the linked page. This enhances usability and prevents frustration for mobile users.
Original PR description
Clicking on an odoo link in the chat window will take the user to the related page in odoo. However, in mobile view, the chat window remains unfolded and covers the entire page, so the user can't see the newly opened page below the chat window unless they fold the chat window. This change fixes this by folding the chat window in mobile view when clicking an odoo link inside the chat window. task-4762503 Forward-Port-Of: odoo/odoo#244905 Forward-Port-Of: odoo/odoo#208440
This update fixes an issue where employee names were being incorrectly formatted in payroll reports (specifically, last name before first name). The code has been corrected to ensure names are consistently displayed as 'FirstName LastName,' aligning with Swiss regulations and improving report accuracy. Test data has also been updated to reflect this change.
Original PR description
* Fix _compute_l10n_ch_legal_name method to correctly assign first_name and last_name from employee name (was previously reversed) * Update all SwissDEC test data to use correct "FirstName LastName" format instead of "LastName FirstName" to match the corrected computation logic task-5102851 Forward-Port-Of: odoo/enterprise#105044 Forward-Port-Of: odoo/enterprise#95252
This update strengthens Odoo's database safety by ensuring that queries against PostgreSQL always use the correct schema. This prevents potential errors and data corruption that could occur when multiple schemas are used simultaneously, addressing a previously reported issue. It's a proactive measure to maintain data integrity and stability.
Original PR description
Safety measure to prevent hidden bugs and data corruption which can happen when multiple schema are used in PostgreSQL. Description of the issue/feature this PR addresses: Related to: - PR #243833 - OPW [opw-5495025](https://www.odoo.com/my/tasks/5495025) - issue reported earlier: #97891 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#243967
This update fixes a display issue in the spreadsheet filter side panel. Field matching is now only shown after a model and field have been selected, aligning with other filter types. This ensures a more intuitive and consistent user experience for configuring spreadsheet filters.
Original PR description
## Description Before this commit: - In the selection global filter side panel, field matching was shown immediately, even when the model and field were not selected. - Without a model, field matching cannot be configured correctly, so showing it early had no meaning. - This behavior was inconsistent with relational global filters. After this commit: - Field matching is displayed only after the user selects both model and field. - Once configured, users can set up field matching as expected, similar to the relational global filter side panel. Task: [5477251](https://www.odoo.com/odoo/project/2328/tasks/5477251) Forward-Port-Of: odoo/enterprise#104545
This update resolves an issue where tables inserted into the To-Do editor appeared after the existing text instead of before it. The fix streamlined the table insertion process, ensuring tables are now correctly placed at the beginning of the block where the user intended. This improves the overall user experience and consistency within the editor.
Original PR description
### Steps to Reproduce : - Open To-Do and type some text. - Place the cursor at the start of the block. - Insert a table. (e.g.: /table) - The table appears after the text instead of before it. ### Purpose of this PR: - Table insertion logic was previously duplicated inside TablePlugin, where it tried to manually split text and inline nodes before inserting the table. However, this responsibility is now correctly handled by `DomPlugin.insert()`, which already: - deletes the current selection if needed. - splits text and inline nodes safely. - handles block boundaries and unsplittable elements. - normalizes the DOM after insertion. - places the cursor at a valid position. task-5480759 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#244689 Forward-Port-Of: odoo/odoo#243242
This update corrects a test failure related to how dates and times are displayed in Chrome. A recent change introduced a regular space instead of a non-breaking space, causing compatibility issues. This fix ensures consistent date and time formatting across different Chrome versions.
Original PR description
Apparently somewhere in the datetime patterns the space between time and A/P mark has been updated from a narrow non-breaking space to a regular space. Make the code cross-version compatible. Forward-Port-Of: odoo/odoo#244961
Features or functions removed from Odoo
This update streamlines the Odoo Enterprise codebase by removing a set of tests specifically for rental wishlists and comparisons. With the rental functionality now integrated into the main website sale module, these separate tests are no longer needed, simplifying the development process and reducing maintenance overhead.
Code cleanup and technical improvements
This update streamlines the handling of manual measurements related to Adam scales by moving the `manual_measurement` field to a dedicated module, `pos_iot_adam_scale`. This improves organization and reduces complexity within the core IoT system.
Original PR description
As the `manual_measurement` field is only specific to adam scales, we moved it to the `pos_iot_adam_scale` module. see odoo/upgrade#9210
2 changes
Resolved issues and error corrections
This update resolves a problem with a test tour for tax reports. The tour previously failed when a specific US localization wasn't installed, due to mismatched date calculations. The fix ensures the tour runs correctly regardless of the installed localization, improving test reliability.
Original PR description
- The tour shouldn't run if a localization with 'Tax Report' for the country is not installed (i.e. l10n_us_account) - Dynamic Javascript dates calculation don't mix well with Python's freeze_time running in the "No future" 2026 preparation build, so I froze the time in the Python test but resorted to hardcode the Javascript dates. - No need to check the position of the column "Column 1". In debug mode for the tour, there will be the "Debug" column where the info about the computations are shown, so it won't be the last. We just need to see that it shows, after all. Runbot error [link](https://runbot.odoo.com/odoo/error/234624) runbot-234624 Forward-Port-Of: odoo/enterprise#101689
This pull request resolves a customer complaint regarding demo data. The name "Deco Addict" was replaced with "Acme Corporation" to avoid confusion with actual business transactions. This ensures a cleaner and more accurate demo experience for our users.
Original PR description
A company that happens to be named "Deco Addict" has complained some of our users thought they had business with them due to test and demo data containing that name. It will now be named Acme Corporation. task-5865502 Forward-Port-Of: odoo/enterprise#105445 Forward-Port-Of: odoo/enterprise#105151
4 changes
Resolved issues and error corrections
This update resolves a bug that occurred when generating reports for German-speaking customers. Specifically, a division-by-zero error was triggered when currency exchange differences (zero amount_currency) were present on move lines. The fix ensures these lines are now handled correctly, preventing report generation issues.
Original PR description
On move lines with zero `amount_currency` ( ex. currency exchange difference ), `_get_product_base_line_currency_rate` returns 0 currency rate which causes a division by zero error. Ignore the rate for lines with zero `amount_currency` opt-5358954
This update fixes an issue where the tax code (9) was missing from Datev exports for expense journal entries using 19%I tax. The problem occurred due to how payment amounts were aggregated during the export process. This ensures accurate tax reporting to Datev, aligning with accounting regulations.
Original PR description
Currently, when using 19%I tax in vendor bills, the tax code (9) is shown correctly in the BU-Schlüssel section of the datev export. This however is not the case for expense journal entries. Steps to reproduce: - With DE Company setup - Create an Expense as follows: - Included taxes: 19% I - Paid by: Company - Create report > Submit to Manager > Approve > Post Journal entries - Open General Ledger and export Datev Data Issue: Tax code will be missing from the exported entry. This occurs because, when processing payment move lines, amounts and accounts are aggregated, losing track of the source tax. opw-5388791 Forward-Port-Of: odoo/enterprise#102548
This update simplifies CRM mail templates to capture more information in chatter, particularly without requiring users to upgrade. By removing redundant fields and leveraging existing data sources, we ensure consistent and complete data collection for our CRM processes. This change was driven by a need to optimize data capture and avoid duplicate entries.
Original PR description
- Remove newly added fields that can be replaced by existing keys present in `iap_mail.enrich_company` template to ensure we get more data in chatter without upgrade and avoid duplicate entries IAP PR: https://github.com/odoo/iap-apps/pull/1390 Forward-Port-Of: odoo/odoo#245068
This update adjusts how product prices are stored within Odoo, ensuring greater data accuracy and consistency. The change involves setting a minimum precision for product prices, which helps prevent rounding errors and improves financial reporting. This update is a technical fix related to a previous issue.
Original PR description
Fix tests, related to https://github.com/odoo/odoo/pull/243987 task-4895014