Friday, May 9, 2025
8 changes
3 changes
Resolved issues and error corrections
The bank reconciliation screen now refreshes related chatter information more reliably when users add, edit, or delete activities or attachments. Loading of reconciliation records is also streamlined so the page can update more efficiently and avoid errors during these interactions.
Original PR description
[IMP] account_accountant: Optimize bank reco service reloadRecords The aim of this commit is using a Promise.all to do all loads requests in one promise. no task id [IMP] account_accountant: Using Chatter's props instead of custom loading The aim of this commit is using hasParentReloadOnAttachmentsChanged and hasParentReloadOnActivityChanged props with an override of reloadParentView to reload the statement line when the user adds/edits/deletes an activity or when an attachment is attached to the chatter. no task id
The bank reconciliation screen now restores a search view that was accidentally removed. This helps users find reconciled bank lines again, reducing friction in accounting review workflows.
Original PR description
In this commit we put back the search view of the reconciled lines that we removed wrongly during this commit: https://github.com/odoo/enterprise/pull/80787/commits/04a304d58a56c7d2eeb70429340eb048fa9f2be6 Upgrade PR: https://github.com/odoo/upgrade/pull/7662 no task id
This fixes a crash that could happen when receiving Peppol invoices through the Documents app. Businesses can now process incoming electronic invoices reliably without a silent failure interrupting document reception.
Original PR description
When receiving Peppol invoices through the Documents App, a silent error is raised. This comes from previous change [1] of the method return type. We changed it from boolean to `account.move` and did not changed it in the documents override causing an append of `account.move` with boolean which crashes. [1]: https://github.com/odoo/odoo/pull/197233 task-no (PMAX testing)
5 changes
Resolved issues and error corrections
This fix prevents embedded items, such as files in Knowledge templates, from disappearing when an editable page is opened. It also keeps older or demo embedded file links working when they rely on a direct URL rather than a file identifier.
Original PR description
Prior to this commit, if an inline embedded component block was put as a direct child of the editable, it was removed during `initElementForEdition`, because `isVisible` returned false. However at…
Prior to this commit, if an inline embedded component block was put as a direct child of the editable, it was removed during `initElementForEdition`, because `isVisible` returned false. However at that point, the `embedded_component_plugin` did not yet have the opportunity to fill that embedded component. Therefore, as a prevention measure, all elements with `data-embedded` attribute will always be considered `visible`, as their removal should be at the discretion of the `embedded_component_plugin`. If they happen to have an `inline` style and they are direct children of the editable, they should be wrapped in a baseContainer `div` or `p`, but never removed. Issues of the type were observed when loading a Knowledge template containing a `div` with `data-embedded="file"` since embedded files have since been refactored to use an `inline-block` display style which made them eligible to be removed by `initElementForEdition` prior to the changes introduced in this commit. task-4745902
Invoices in foreign currencies now recalculate accounting amounts correctly when both the invoice date currency rate and line price are changed. This prevents journal entries from using an outdated price with a new exchange rate, improving financial accuracy.
Original PR description
**Steps to reproduce:** - Install account - Activate a foreign currency (e.g. EUR) - Set at least 2 different currency rates for date1 and date2 - Create an invoice: * Customer: [any] * Invoice Date:…
**Steps to reproduce:** - Install account - Activate a foreign currency (e.g. EUR) - Set at least 2 different currency rates for date1 and date2 - Create an invoice: * Customer: [any] * Invoice Date: date1 * Currency: EUR * Invoice line: [any] - Save the invoice - Check debit and credit amounts in "Journal Items" tab - Change the price of the product and set "Invoice Date" to date2 - Save the invoice - Check debit and credit amounts in "Journal Items" tab **Issue:** The debit and credit amounts have been recomputed with the new currency rate, but the conversion has been applied on the old price. **Cause:** In "_sync_invoice" method, when the currency rate has changed, balance (and subsequently debit/credit) is recomputed from amount_currency. However, in this case, balance should be recomputed completely because the line subtotal has changed and amount_currency is not up-to-date with it. **Solution:** Do not recompute balance based on amount_currency when price_subtotal of a line has changed. In that case, it will be recomputed anyway. opw-4658156 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Batch inventory adjustments no longer risk creating duplicate accounting journal entries. This helps keep inventory valuation and accounting records accurate when multiple stock adjustments are applied together.
Original PR description
Issue ----- Batch applying quantity adjustments creates duplicated journal entries. Steps to reproduce ----- - Create two products with automated valuation and 10 on hand quantity - Go to Inventory > Operations > Physical inventory and create an inventory adjustment for the two products (one positive, one negative) - Select both lines and click on "Adjust All" - Go to accounting > Accounting > Journal items -> Duplicated entries with one using the inventory valuation account and stock input and the other using the valuation account with stock output account Fix ----- This issue has been fixed by commit ce5d303 so just adding a small test to round things up. ----- Tickets: opw-4672011 opw-4677147 opw-4670069
The Employee dashboard has been corrected so it only includes employees from the user's company. This prevents figures from other companies from appearing in dashboard results, keeping reporting aligned with company access rules.
Original PR description
Commit odoo/odoo@abd909498e4fd relaxed the multi-company rule for hr.employee (more records are visible). Instead the action domains were updated to include the restricted company rules (see only from your company) The domains in the Employee dashboard was not updated though. It means the dashboard takes into account employees from other companies (as allowed by the ir.rule) opw-4777122
Fixes an issue where accounting dashboard information could disappear for bank journals connected to online accounts, especially in branch/parent company setups. The update reuses the correct dashboard indicator and ensures credit journals also show the expected synchronization actions.
Original PR description
A previous commit 9b133b2cd03a726d330c87a1227903fc925b0ed5 restricted the view and actions we had on the accounting dashboard for a bank journal from a branch company, if the journal belongs to the parent company. In Odoo 17 the fix made sense, but in Odoo 18, the dashboard data added conflicts with another one, resulting in no data being displayed at all when the journal is connected to an online account. This PR adapts the initial fix to use the existing data (deprecate `show_bank_connect` in favor of `display_connect_bank_in_dashboard`) and adds the 'credit' type journal in the condition for `show_sync_action` to be used by the dashboard data.