Daily updates from Odoo
Friday, October 18, 2024
7 changes
6 changes
Enhancements to existing features
Brazilian electronic invoicing now shows the CFOP fiscal code calculated for each invoice line before submission. This helps users spot configuration issues earlier and avoid correcting or reversing electronic invoices after they have been issued.
Original PR description
Avatax determines the CFOP [1] of each invoice line during tax calculation. It bases it on the chosen operation type, product, contact and company configuration. The CFOP values are submitted during electronic invoicing. Displaying them to the user before electronic invoicing gives the user a chance to detect misconfiguration earlier, and correct it without having to deal with reversing an electronic invoice. This commit updates the translations to include these new terms, and also cleans them up so they match the code again [2]. [1] Código Fiscal de Operações e de Prestações: a fiscal code defined by the Brazilian authorities to describe the type of business transaction. [2] Went out of sync due to 402326b64c14faf1658fc1c42ca19218df4c401d not updating the translations. task-4250764
Document requests now better reflect who asked for the file by showing the requester as the owner, making follow-up responsibilities clearer. Users can also reply to request emails with an attachment to submit the requested document, and teams can send reminder emails for overdue requests.
Documents now keeps the selected workspace, categories, and filters in the page URL. This lets users share a link that opens directly to the same Documents workspace and view, reducing navigation time and confusion.
Original PR description
The documents view will now track the current workspace in the url, making it possible to directly share a specific workspace with a colleague. Instead of the link landing on the last workspace/the first workspace available. TaskId-3128953
Odoo now avoids labeling all internal RPC errors with a misleading success-like code. This makes error reporting clearer for integrations and support teams, reducing confusion when diagnosing issues across accounting, reports, mobile, and Studio features.
Original PR description
The JSONRPC specification specifies what "code" should be used with what kind of errors. Odoo never cared to implement those errors correctly and frankly 200 is the single worst value to pick. Use 0 instead. It doesn't respect the specification either but at least it is not 200. task-4257153
GSTR-1 reports now use the original invoice amount when reporting credit and debit notes, improving accuracy for Indian GST filings. If a credit note is missing its linked invoice, the report warns users and the credit note form now provides a field to select the original invoice.
Original PR description
Previously, in the GSTR-1 report, credit and debit notes were reported based on their own amounts. With this PR, the reporting will now check the amount of the original invoice. Additionally, if a credit note is created without an associated invoice, the user will receive a warning in the report, and a field will be displayed in credit notes to select the original invoice. task-4175690
This update improves how social media feeds load across supported platforms, reducing waiting time for users managing social content in Odoo. It should make day-to-day monitoring of Facebook, Instagram, LinkedIn, X/Twitter, and YouTube streams feel more responsive.
Original PR description
Task-4146092
1 change
Enhancements to existing features
This update adds a new XLSX export option for Colombian companies that provides a detailed trial balance report broken down by both accounts and business partners. Previously, the trial balance only grouped data by accounts. This enhancement makes it easier for Colombian businesses to analyze their financial data with partner-level detail, improving financial reporting and analysis capabilities.
Original PR description
… partners This enhancement introduces an XLSX export variant for the trial balance, specifically tailored for Colombian companies under the report name "BALANCE DE PRUEBA POR TERCERO." The requirement is to provide a detailed breakdown per partner for each account. The initial trial balance lines are primarily derived from the general ledger report, which originally focused on grouping by accounts. Inspired by the structure of the general ledger accounts, this implementation now extends the grouping to include both accounts and partners. While initially designed for the Colombian localization, the code is flexible and can be easily adapted for use in other localizations as needed. Co-authored-by: Brice Bartoletti <bib@odoo.com> task-3594546 Forward-Port-Of: odoo/enterprise#70110