Daily updates from Odoo
Sunday, November 9, 2025
4 changes
1 change
Resolved issues and error corrections
This update reclassifies Romanian customer advance accounts so they are treated as liabilities instead of assets. As a result, these accounts can now be used correctly for customer down payments on invoices, improving accounting accuracy and invoice handling.
Original PR description
Before this PR: - Accounts 419000, 419100, and 419200 were set as Current Assets, even though they represent customer advances (liabilities). After this PR: - These accounts are reclassified as Current Liabilities, allowing them to be properly used as downpayment accounts on customer invoices. Task-5188142 Forward-Port-Of: odoo/odoo#233572
1 change
Resolved issues and error corrections
This update reclassifies certain Romanian accounts used for customer advance payments from current assets to current liabilities. As a result, they can now be used correctly as down payment accounts on customer invoices, improving accounting accuracy.
Original PR description
Before this PR: - Accounts 419000, 419100, and 419200 were set as Current Assets, even though they represent customer advances (liabilities). After this PR: - These accounts are reclassified as Current Liabilities, allowing them to be properly used as downpayment accounts on customer invoices. Task-5188142 Forward-Port-Of: odoo/odoo#233572
2 changes
Resolved issues and error corrections
The messaging menu no longer crashes when a user has a large number of chats. This fix removes an inefficient internal dependency that could trigger repeated recalculations and overwhelm the app, improving stability when opening the chat tab.
Original PR description
Accessing the chat tab in the messaging menu with many chats causes a max call stack error. Threads in the messaging menu rely on the `menuThreads` store field, which depends on `thread.displayName`. - Thread display name is a getter which accesses `correspondent.name`, a computed field. - Accessing `thread.displayName` in a loop repeatedly triggers recomputation of `menuThreads`, eventually reaching max call stack size. - Additionally, `menuThreads` computation is inefficient due to sorting and reactive proxy access. To solve this issue: - Update `menuThreads` to use the inverse relation instead of a complex compute. - Debounce the array sort so it executes only once when the relation is fully filled. task-4794325 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#234702
This update reclassifies Romanian customer advance payment accounts as current liabilities instead of current assets. This ensures downpayments on customer invoices are recorded in the correct accounting category and improves financial reporting accuracy.
Original PR description
Before this PR: - Accounts 419000, 419100, and 419200 were set as Current Assets, even though they represent customer advances (liabilities). After this PR: - These accounts are reclassified as Current Liabilities, allowing them to be properly used as downpayment accounts on customer invoices. Task-5188142 Forward-Port-Of: odoo/odoo#233572