Daily updates from Odoo
Navigate
Branch
Friday, August 26, 2022
18 changes
New functionality added to Odoo
A new accounting import guide centralizes setup steps and country-specific options, making it easier for businesses to bring accounting data into Odoo. It also improves importing chart of accounts and journal item data, while moving specialized Winbooks and FEC options into the guided flow.
Original PR description
- Add a new `account_base_import` module - a unified Accounting Import Guide to make the setup process easier - The new module also fixes the import of `account.move.line` and `account.account` - Remove Winbooks and FEC menuitems from the Accounting dropdown menu - they should be linked in the import guide - Country-specific guidelines are added: FEC appears for FR, LU, Winbooks for BE task-2888243
Enhancements to existing features
Marketing users can now insert dynamic placeholders while creating email and SMS templates by typing # and selecting a field. This makes it faster to personalize campaign content with customer or record information and optional fallback values.
Original PR description
Introduce a new Dynamic Placeholder Generator in mailing and SMS template creation. Using a specific character (#) in subject or body will trigger the opening of the field selector popup, which can be use to select the wanted field and enter a default value. on validation the dynamic placeholder will be inserted in the corresponding input/editable. task-2154624
The bank reconciliation screen now includes due date information, making it easier for accounting users to identify and match outstanding items. This improves day-to-day reconciliation accuracy and helps teams prioritize payments or receivables without leaving the workflow.
Spreadsheet users who choose “See records” from a pivot cell now land in a fuller record view that includes both list and form options. This makes it easier to review details and open individual records without extra navigation.
Original PR description
… view With this commit, `See records` action on pivot cell now redirects to an action with both list and form view. Task-id 2941453
Activity creation and completion have been optimized so large batches are processed more efficiently. This should make work queues, documents, payroll leave activities, and VoIP call-related activities faster and more reliable, especially when many activities are created or closed at once.
Original PR description
PURPOSE
Improve performance of activities creation and management. Improve overall
code.
SPECIFICATIONS
Main code changes are
* classify activities by model, to browse related records in batch per model
instead of one by one;
* rewrite create and _action_done main methods to be done in batch;
skip useless computation (use categories before browsing records, avoid
* useless ref / direct xml ID check, ...);
* globally batch when possible;
See sub commits for more details.
LINKS
Task-2884301 (Voip synchronization simplification)
Task-2883589 (Activity creation performancThe appraisal module’s confirmation checkbox has been updated to use Odoo’s newer interface technology. This keeps the appraisal experience consistent with the modern platform and helps maintain reliability for future updates.
Original PR description
Convert the boolean confirm field widget to Owl. task-2928190
The predictive billing feature now avoids suggesting account types that do not fit the new bill being entered. This prevents old or incorrect database entries from causing confusing suggestions on future bills.
Original PR description
Sometimes there are existing errors in the database, but we don't want it to make noise for future entries.
Resolved issues and error corrections
This update restores missing styling for the accounting reconciliation screen and fixes issues that caused manual reconciliation line amounts to appear as zero or be hidden. This helps accounting users review and reconcile transactions accurately after recent changes to the bank reconciliation widget.
Original PR description
The commit https://github.com/odoo/enterprise/commit/0063d7d6a09c16716dcd9125c291a1041f9ed255
forgot to include the corresponding scss file.
Changes brought by the refactoring of the new bank reconciliation
widget and accounting v16 (yeeeeaah) introduced 2 bugs in the manual
reconciliation widget:
- the lines amounts were always set to 0 and invisible
- some originally inherited method were put in the same class as
their child method, leading to duplicated method signatures.Fixed an issue where invoice information shown during bank reconciliation could change after validation, helping users keep consistent and reliable reconciliation records. The update also prevents errors when expanding lines without extra notes and corrects navigation from the bank reconciliation widget.
Original PR description
- Create a statement line - Create an invoice - Match the statement line with the invoice in the widget without saving => The name of the invoice is displayed - Validate => The name has changed Explanation: After the validation, the bank reco widget line is no longer a 'new_aml' but an 'aml' meaning its 'source_aml_id' that was an invoice is now the bank statement line journal entry itself. So 'source_aml_move_id' must not be a related field but a computed field looking to the reconciliation when the bank reco widget line is 'aml'. task: 2942314
This fixes cases where customers using SEPA Direct Debit were sent too early to a confirmation page that had no payment details to show. Customers now remain on the payment processing page until the payment reaches a clear final status, reducing confusion and failed-looking checkout experiences.
Original PR description
Before this commit, customers never waited on the payment
post-processing page, leading to some cases where they were redirected
to a confirmation page with no data to confirm, only displaying a red
bar.
Now, customers will remain on the payment post-processing page until
their transaction status is updated to a final state ('authorized',
'done', 'error'). The `processPolledData` method is overridden in
`payment_transfer` and in `payment_sepa_direct_debit` so customers
don't have to wait for the merchant to receive their payment.
Fix fbf1af17bb7855f972bd292b3947d206088869c5
See also:
- https://github.com/odoo/odoo/pull/95933
task-2908493The Helpdesk timesheet timer has been repositioned so it appears correctly in the ticket view. This restores the expected layout after a recent interface structure change and helps users track time without visual confusion.
Original PR description
This commit fixes the position of the timer in the helpdesk module. The timer is no longer correctly placed since the introduction of a div wrapper around legacy fields. This commit simply realign the timer correctly. Before: <img width="287" alt="image" src="https://user-images.githubusercontent.com/35101914/186584520-4347d6a1-5f5d-4601-a9d8-72b6d8307fc5.png"> After: <img width="272" alt="image" src="https://user-images.githubusercontent.com/35101914/186584450-979bdd28-9072-40b9-991a-38ba4bbb8092.png">
Code cleanup and technical improvements
This update simplifies styling for enterprise form views as part of a broader visual cleanup. It improves consistency in editable note fields and helps keep the interface easier to maintain, with minimal direct impact on day-to-day users.
Original PR description
Part of the overall v16 SCSS optimization/restyle, task-2704984 Requires: - https://github.com/odoo/odoo/pull/98101 task-2918464
The PLM notification button has been modernized without changing its intended business function. This helps keep the manufacturing product lifecycle interface maintainable and aligned with the current platform framework.
Original PR description
Updates the plm_toaster_button widget into OWL. Task-2885757
The PLM module has been adapted to work with the renamed and redesigned BoM Overview report. This keeps product version and engineering change order details available in the updated manufacturing overview while removing old report-specific code.
Original PR description
Related to odoo/odoo#93194 Adapt the overrides for plm (addition of versions/ecos) to match the changes done in the new BoM Overview. Task-2628323
Miscellaneous changes
For Bill/2022/08/002 (id:liaison_bill_1), the due date wasn't visible either from the bills list view or the journal items due date. This was due to a wrong field name. Used the task as an opportunity to remove useless lines. task-2930512 Forward-Port-Of: odoo/enterprise#30258
Original PR description
For Bill/2022/08/002 (id:liaison_bill_1), the due date wasn't visible either from the bills list view or the journal items due date. This was due to a wrong field name. Used the task as an opportunity to remove useless lines. task-2930512 Forward-Port-Of: odoo/enterprise#30258
onlinesync.odoo.com domain name was never meant to be used for localisation. Replace it with a correct domain name. Forward-Port-Of: odoo/enterprise#30731 Forward-Port-Of: odoo/enterprise#30720
Original PR description
onlinesync.odoo.com domain name was never meant to be used for localisation. Replace it with a correct domain name. Forward-Port-Of: odoo/enterprise#30731 Forward-Port-Of: odoo/enterprise#30720
The issue: When validating the invoice, the Sunat checks that the `PriceAmount` of the xml is equal to the division of `InvoicedQuantity / LineExtensionAmount` This verification sometimes fails for invoices with unit price of more than 2 decimal places, because we are forcing to use 2 decimal places For example, take the following situation: - Decimal Accuracy for Product Price is 4 - Create a invoice with Quantity = 2000, Price = 0.0575, Taxes = 18% - The PriceAmount in the Xml is 0.0
Original PR description
The issue: When validating the invoice, the Sunat checks that the `PriceAmount` of the xml is equal to the division of `InvoicedQuantity / LineExtensionAmount` This verification sometimes fails for invoices with unit price of more than 2 decimal places, because we are forcing to use 2 decimal places For example, take the following situation: - Decimal Accuracy for Product Price is 4 - Create a invoice with Quantity = 2000, Price = 0.0575, Taxes = 18% - The PriceAmount in the Xml is 0.06, but it should be 0.0575 - When we multiply 0.06 * 2000 = 120 and 0.0575 * 2000 = 115. The difference is 5, so the check fails. The solution: - Round the unit_amount to the decimal accuracy of Product Price Latam Ticket: https://latam-localizations.odoo.com/web#id=864&cids=1&model=project.task&view_type=form Forward-Port-Of: odoo/enterprise#30454 Forward-Port-Of: odoo/enterprise#30194
Compute book value and value_residual on negative asset Steps: - Create an asset model AM - On AM.account_depreciation_id, set create_asset to 'draft' and asset_model to AM - Create a Vendor bill credit note CN, with invoice_date today - 1 month With invoice_line_ids: "account_id": AM.account_depreciation_id, "price_unit": 500 - Confirm CN, go to related asset newly created and validate it - book_value and value_residual should be 500 - Post the first asset's depreciation m
Original PR description
Compute book value and value_residual on negative asset
Steps:
- Create an asset model AM
- On AM.account_depreciation_id, set create_asset to 'draft'
and asset_model to AM
- Create a Vendor bill credit note CN, with invoice_date today - 1 month
With invoice_line_ids:
"account_id": AM.account_depreciation_id, "price_unit": 500
- Confirm CN, go to related asset newly created and validate it
- book_value and value_residual should be 500
- Post the first asset's depreciation move
-> book_value and value_residual are still 500, they should be 400
Compute the field debit/credit in _get_depreciation() regarding the
type of the original move.
opw-2848330
opw-2882049
Forward-Port-Of: odoo/enterprise#30707
Forward-Port-Of: odoo/enterprise#28373