Wednesday, June 19, 2024
7 changes
5 changes
Enhancements to existing features
This update simplifies how WhatsApp discussion sidebar tests identify elements by removing an unnecessary page structure dependency. It is a minor maintenance improvement that makes tests less fragile without changing user-facing behavior.
Original PR description
The title itself is precise enough to not depend of the tag. Community PR: https://github.com/odoo/odoo/pull/169751
The Chilean electronic invoicing and electronic receipt capabilities are now consolidated into one module. This simplifies maintenance and reduces dependency issues between features that already relied on each other.
Original PR description
This commit merges the 2 modules of l10n_cl_edi with l10n_cl_edi_boletas. The functionalities of the 2 modules were merged into a single module: l10n_cl_edi. These modules l10n_cl_edi and l10n_cl_edi_boletas were developed separately in different stages. It was needed to merge them since they depend on one another. task-3214230
Web Studio now shows clearer names for selected page elements in the sidebar and deletion dialogs, making complex layouts easier to understand. The update also reorganizes internal editor logic so each view type handles structure changes more cleanly, helping future improvements be easier to maintain.
The Gantt view now includes improved controls for choosing the visible date range. This helps users quickly adjust planning timelines and review schedules at the right level of detail.
Spreadsheet users can now choose whether month and quarter options are available for fixed-period date filters. This gives businesses more control over reporting choices and helps keep filter options aligned with how teams analyze data.
Original PR description
This commit adds the possibility to disable the month or quarter granularity (or both) for fixedPeriod date filters. Task: [3887844](https://www.odoo.com/web#id=3887844&cids=1&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form)
2 changes
Enhancements to existing features
Users can now select which bank journal to use when importing bank statements through Document Actions. This improvement makes it easier for users importing CSV files, as the system previously only worked optimally with CODA files. If no journal is selected, the import defaults to the first available journal.
Original PR description
[IMP] documents_account: Add selection of journal in Document Action 'import bank statement' Backport of: https://github.com/odoo/enterprise/pull/46482/commits/d2a95d7ffa3ef2976172ed17eaf93056ea0f8c6c For now we didn't chose the bank journal because we assume that only coda file where push like this, and in the coda file we can find in which journal to send it. But Coda is limited to BE and lot of user import CSV file for bank. Add the selection of the journal (not mandatory) for Document action, and inject CSV in the journal selected. If no journal selected inject the CSV in the first one of the list. If it's a coda file, keep as now and don't take care of the journal selected. Task-3932055
The GST return report generation has been significantly optimized to handle large volumes of transaction data much faster. By improving how the system retrieves and processes accounting and point-of-sale records, the report now completes in approximately 10% of the previous time—reducing processing time from 2800 seconds to 300 seconds for typical datasets. This improvement directly benefits users who need to generate GST compliance reports without experiencing long system delays.
Original PR description
Issue --> With a large number of `account.move.line` and `pos.order.line` records, methods `_get_tax_details`, `_get_gstr1_hsn_json` and `_set_details_pos_lines` do not perform well. Solution --> In…
Issue --> With a large number of `account.move.line` and `pos.order.line` records, methods `_get_tax_details`, `_get_gstr1_hsn_json` and `_set_details_pos_lines` do not perform well. Solution --> In `_get_tax_details` --> Replace the journal items recordset with a set of ids to do deletions. Move the fetch to when it is actually needed. In `_get_gstr_hsn_json` --> Prefetch the l10n_in_code values on `uom.uom` records that are used in the for loop. This optimization prevents additional hits to the backend. In `_set_details_pos_lines` --> Fetch `product.product` records and all the `uom.uom` records before the for loop to prevent additional hits to the backend when trying to fetch `product_id.type`, `product_id.l10n_in_hsn_code` and `product_uom_id.l10n_in_code` Benchmark --> For about 110k journal items and 95k pos order lines, the current implementation takes about 2800 seconds to finish computation. After the fix, the process takes about 300 seconds to finish. opw-3895401