Daily updates from Odoo
Wednesday, January 14, 2026
33 changes
3 changes
Enhancements to existing features
This update adds three new fields to invoices generated with the l10n_fr_facturx_chorus_pro module: Buyer Reference, Contract Reference, and Purchase Order Reference. These fields are required for Chorus Pro compliance, ensuring invoices meet the necessary documentation standards for accurate financial reporting.
Original PR description
This commit: - Add three reference fields to invoice PDF for Chorus Pro compliance: Buyer Reference, Contract Reference, and Purchase Order Reference. These fields appear in the invoice header when set on the invoice. task-5410836 Forward-Port-Of: odoo/odoo#240494
This update simplifies product pricing management by consolidating all pricing configurations – Sales, Rentals, and Subscriptions – into a single, easy-to-use interface. This improves efficiency for users and ensures consistent pricing across the Odoo ecosystem, particularly for eCommerce and rental products.
Original PR description
The primary goal of this PR is to unify product pricing management across the Odoo ecosystem by centralizing configurations for Sales, Rental, and Subscription applications within the core pricelist…
The primary goal of this PR is to unify product pricing management across the Odoo ecosystem by centralizing configurations for Sales, Rental, and Subscription applications within the core pricelist engine. This consolidation introduces a single "Prices" tab on the product template form, effectively replacing fragmented, app-specific views with a unified interface. To improve daily efficiency, the PR enables users to quickly manage fixed-price rules through an inline editable interface directly on the product form, while still providing access to the full pricelist engine for more complex configurations. On a technical level, the pricelist engine has been evolved to support the temporal and contextual needs of dependent applications; this includes dissociating the date used for rule application from the date used for currency conversion, as well as propagating request contexts during eCommerce price computations. task-5375343 See also: - https://github.com/odoo/enterprise/pull/102625 - https://github.com/odoo/upgrade/pull/9172 --- To accelerate this PR, it was decided to rebase the work on an ongoing PR [^1][^2] refactoring and greatly facilitating the interactions backend-frontend of the eCommerce/Rental applications. Thx Louis 😉 (and Victor for thinking about it) [^1]: https://github.com/odoo/odoo/pull/234405 [^2]: https://github.com/odoo/enterprise/pull/98161
This update allows system administrators to customize the main Odoo Enterprise home menu with a targeted message. Administrators can set a message via a database configuration, such as a maintenance notification, which will then be displayed to all users. This provides a flexible way to communicate important information directly to users.
Original PR description
Display a message on home menu based on an ir.config_parameter that can be added directly in the database by the system administrator.
The ir.config_parameter is sysadmin.message and should be a json loadable. The format shoud be something like this:
{
"type": "warning",
"replace": false,
"warning_type": "user",
"message": "`<span>A maintenance operation is planned on your server on <strong>2026-01-15</strong> between 14h and 15h</span>`"
}
Forward-Port-Of: odoo/enterprise#103831
Forward-Port-Of: odoo/enterprise#1022392 changes
Enhancements to existing features
This update adds three new fields to invoices generated within the Chorus Pro system: Buyer Reference, Contract Reference, and Purchase Order Reference. These fields ensure invoices comply with Chorus Pro requirements, improving data accuracy and facilitating seamless integration with the Chorus Pro platform.
Original PR description
This commit: - Add three reference fields to invoice PDF for Chorus Pro compliance: Buyer Reference, Contract Reference, and Purchase Order Reference. These fields appear in the invoice header when set on the invoice. task-5410836 Forward-Port-Of: odoo/odoo#240494
This update allows system administrators to customize the main Odoo Enterprise home menu with a targeted message. Administrators can set a message via a database configuration, such as a maintenance notice, which will then be displayed to all users. This provides a flexible way to communicate important information directly to users within the system.
Original PR description
Display a message on home menu based on an ir.config_parameter that can be added directly in the database by the system administrator.
The ir.config_parameter is sysadmin.message and should be a json loadable. The format shoud be something like this:
{
"type": "warning",
"replace": false,
"warning_type": "user",
"message": "`<span>A maintenance operation is planned on your server on <strong>2026-01-15</strong> between 14h and 15h</span>`"
}
Forward-Port-Of: odoo/enterprise#103831
Forward-Port-Of: odoo/enterprise#1022394 changes
Enhancements to existing features
This update allows branch companies within Odoo to participate in the Peppol network. Users can register their branch as a sender for the parent company or create a new registration, providing greater flexibility for international trade and compliance. This change simplifies the process for businesses operating across multiple locations.
Original PR description
This commit implements the functionality to allow all branch company to use Peppol. With this commit, the user can register a branch company in the peppol network in two ways: - By setting the same EAS/Endpoint than the one set on the parent company, the branch will be registered as a sender for the parent company. - By setting another EAS/Endpoint than the one set on the parent company, the branch will do a new registration. task-4852830 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#240081
This update adds three new fields to invoices generated for Chorus Pro compliance – Buyer Reference, Contract Reference, and Purchase Order Reference. These fields appear in the invoice header, allowing for accurate documentation required by Chorus Pro and improving data tracking for financial reporting.
Original PR description
This commit: - Add three reference fields to invoice PDF for Chorus Pro compliance: Buyer Reference, Contract Reference, and Purchase Order Reference. These fields appear in the invoice header when set on the invoice. task-5410836 Forward-Port-Of: odoo/odoo#240494
This update allows system administrators to customize the main Odoo Enterprise home menu with a targeted message. Administrators can set a message via a configuration parameter, visible to all users. This enables timely communication about planned maintenance or important updates directly within the application.
Original PR description
Display a message on home menu based on an ir.config_parameter that can be added directly in the database by the system administrator.
The ir.config_parameter is sysadmin.message and should be a json loadable. The format shoud be something like this:
{
"type": "warning",
"replace": false,
"warning_type": "user",
"message": "`<span>A maintenance operation is planned on your server on <strong>2026-01-15</strong> between 14h and 15h</span>`"
}
Forward-Port-Of: odoo/enterprise#103831
Forward-Port-Of: odoo/enterprise#102239This update adds a 'Reload Data' button to error dialogs in the Point of Sale system, providing users with a simple way to resolve common issues. Previously, users only had an 'Ok' button, making it difficult to recover from errors. This change reduces downtime and improves the overall user experience for POS operations, particularly for Restaurant orders.
Original PR description
Purpose: ------------ - On Error dialogs, users only had "Ok" or could close the dialog, with no guidance on what to do next. - Many blocking issues are resolved simply by reloading POS data. Before this commit: ----------- - Error dialogs only had an "Ok" button. After this commit: ------------------ - Added a "Reload Data" button for quick recovery of common blocking issues. - Added a warning message in the reload data popup - For POS Restaurant, orders will attempt to sync before reloading data, reducing the risk of data loss. Task-5353590
3 changes
Enhancements to existing features
This update adds three new fields to Odoo invoice PDFs – Buyer Reference, Contract Reference, and Purchase Order Reference – to ensure compliance with Chorus Pro requirements. These fields allow users to accurately document key purchase information directly on the invoice, simplifying the invoicing process for Chorus Pro clients.
Original PR description
This commit: - Add three reference fields to invoice PDF for Chorus Pro compliance: Buyer Reference, Contract Reference, and Purchase Order Reference. These fields appear in the invoice header when set on the invoice. task-5410836 Forward-Port-Of: odoo/odoo#240494
This update adds two new Unit of Measure codes – Minute (MIN) and Kilowatt hour (KWH) – to Odoo, aligning with UNECE Recommendation No.20 for Peppol. Previously, Odoo defaulted to a generic 'Units' code, which wasn't suitable for UBL/CII electronic invoices. This change ensures proper support for these key units, particularly benefiting localization modules like those for Chile and Turkey.
Original PR description
**Issue:** 2 UoM that is in the UNECE Recommendation No.20 for Peppol don't exist in Odoo: - MIN: Minute - KWH: Kilowatt hour Even if they are created manually, they are not used in the UBL/CII electronic invoices. Instead, the default code (i.e. "C62" for "Units" is used). Some localization modules create the "Kilowatt hour" UoM as they need it. (l10n_cl and l10n_tr_nilvera) So it's better to have a "generic" one available for every module. opw-5269119 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#243333 Forward-Port-Of: odoo/odoo#238342
This update enables public users to register for document sharing without needing a traditional Odoo user account. Previously, a public user invited via link would be forced to create a user, which wasn't ideal. Now, the system intelligently creates a linked user for the partner, streamlining the document sharing process.
Original PR description
Purpose ======= We can share a document to a partner without a user, and with `access_via_link == 'none'`. In that situation, the partner is forced to create a user, but if he clicks on signup, then the new user won't be linked to the partner set on the `documents.access` (a new partner will be created). Now, when inviting a member, if he doesn't have a user, we invite him to create a user. If the partner has a user, then we just redirect him to the login page. Task-5242208 Forward-Port-Of: odoo/enterprise#100628
12 changes
Enhancements to existing features
This update streamlines the process of canceling NFC-e receipts generated from Point of Sale orders. Previously, users had to manually handle cancellations through the SEFAZ portal, which was time-consuming. Now, a new button within the back-end allows for direct cancellation, improving efficiency and reducing manual effort.
Original PR description
With this **PR**, NFC-e generated from PoS orders can now be canceled directly from the back-end. Previously, users were required to manually perform the cancellation through the SEFAZ portal, which was cumbersome. A new button is added on the PoS order form to trigger the NFC-e cancellation. Upon successful cancellation, the related XML is saved and attached to the chatter. If an error occurs, a user-friendly message is displayed showing the relevant error code and description returned by SEFAZ/Avalara. **task**-5254905
This update ensures that withholding taxes are correctly reflected when uploading vendor bills from electronic invoices in Colombia. Previously, the system didn't recognize withholding taxes in XML files, leading to inaccurate bill uploads. Now, the XML parser accurately captures and includes these taxes, improving data accuracy for Colombian accounting.
Original PR description
Purpose: For Colombia, it is possible to upload vendor bills by drag and dropping the electronic invoice XML into the purchase journal. The XML file is parsed through for relevant information to create the vendor bill. Since vendor bills in Colombia will typically include withholding taxes, the parser should handle this case for a more accurate bill upload. Current Behavior: When uploading XML files that includes withholding taxes, the withholding taxes are not reflected on the uploaded vendor bill. Expected Behavior: When uploading XML files that includes withholding taxes, the withholding taxes are reflected on the uploaded vendor bill. task-5255094
This update enhances our document generation to meet the stricter PDF/A-3A standard, ensuring compatibility with a wider range of PDF viewers and archiving systems. The changes address previous validation failures and incorporate new requirements for PDF/A-3A compliance, improving document accessibility and long-term preservation.
Original PR description
This commit upgrades our PDF/A compliance from 3B to 3A, and fixes a few issues previously undetected due to the different PyPDF libraries we're currently supporting that made the previous PDF fails…
This commit upgrades our PDF/A compliance from 3B to 3A, and fixes a few issues previously undetected due to the different PyPDF libraries we're currently supporting that made the previous PDF fails even the 3B validation. Improvement 1: PDFA validators were previously detecting our file as 3B. Hence we update the metadata content `conformance` to `A`. Issue 2: When using `._pypdf` library, we failed the 6.1.2-2 and 6.8-1 rule even though we have implemented them on the previous version. It seems that this is caused by the `if SUBMOD...` check only ensuring it's not equal to `_pypdf2_2` (which makes it trigger for the new `_pypdf`). Hence, we reclarify the comments and fix the IF check. Issue 3: After implementing issue 2, it seems that a traceback occurs every time we're using `._pypdf` and calling the pdf write method. This is because the added characters on the header can't be decoded with `UTF-8`. Hence we change it to other greater-than-127-bytes characters that can still be decoded with `UTF-8`. (The actual character used here doesn't matter). Improvement 4: To be compliant with the new 3A rules (additional rules not there in 3B when we first implemented them), we add a minimal mark info dictionary and document structure on the PDF catalog object (`_root_object`). task-None Forward-Port-Of: odoo/odoo#243171 Forward-Port-Of: odoo/odoo#234960
This update makes the HR Applicant data available for use in other Odoo modules. Previously, this data was isolated. This change improves data flow and allows for more integrated HR processes within the system.
Original PR description
Export HrApplicant model so that it can be used in other modules Task-[5461729](https://www.odoo.com/odoo/5778/tasks/5461729) Enterprise PR odoo/enterprise#103402 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#243317
This update adds three new fields to Odoo invoice PDFs – Buyer Reference, Contract Reference, and Purchase Order Reference – to comply with Chorus Pro requirements. These fields allow users to accurately document key purchase information directly on the invoice, streamlining the accounting process for Chorus Pro transactions.
Original PR description
This commit: - Add three reference fields to invoice PDF for Chorus Pro compliance: Buyer Reference, Contract Reference, and Purchase Order Reference. These fields appear in the invoice header when set on the invoice. task-5410836 Forward-Port-Of: odoo/odoo#240494
This update enhances the offline experience by visually disabling unavailable menus, view switchers, and records within kanban and list views. The system now intelligently uses IndexedDB to track visited items, ensuring a more responsive and user-friendly offline experience. This prepares for a future offline search bar feature.
Original PR description
With this commit, when being offline, menus, view switchers and records (in kanban and list views) that aren't available are disabled (i.e. displayed with opacity and not-allowed cursor). Those disabled elements are still clickable though, but it's highly unlikely that clicking on them would lead to anything but an empty screen (due to the lack of connection). All such items aren't disabled though: we store in indexeddb the list of visited items (actions, view types, records), s.t. we know what is available in cache, and what is then accessible offline. This commit also prepares the ground for the next task, which is to have an offline search bar, allowing to select among previously enabled filters, in kanban and list views. Task~5424765
This update improves the Odoo Enterprise application's performance when operating offline. Specifically, the home menu now intelligently disables unavailable menus, preventing users from attempting to access features that aren't supported in offline mode. This enhances the user experience and reduces potential errors.
Original PR description
This commit is the counterpart of https://github.com/odoo/odoo/pull/242494. When being offline, we disable menus that aren't available offline in the home menu. Task~5424765
This commit updates the o_spreadsheet component with new styling options for pivot tables, enhancing their visual appearance and functionality. The changes allow for more flexible and dynamic styling of pivot tables directly within formulas, improving the user experience for data analysis. This improves the presentation and usability of pivot tables.
Original PR description
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/e5cbf1807 [REL] 19.2.0-alpha.3 [Task: 0](https://www.odoo.com/odoo/2328/tasks/0)…
### Contains the following commits:
https://github.com/odoo/o-spreadsheet/commit/e5cbf1807 [REL] 19.2.0-alpha.3 [Task: 0](https://www.odoo.com/odoo/2328/tasks/0)
https://github.com/odoo/o-spreadsheet/commit/c206f46b4 [FIX] Pivots: Recompute measure on indirect dependency update [Task: 5349782](https://www.odoo.com/odoo/2328/tasks/5349782)
https://github.com/odoo/o-spreadsheet/commit/c1c00f4d9 [IMP] pivots: implement pivot table styles [Task: 4552232](https://www.odoo.com/odoo/2328/tasks/4552232)
https://github.com/odoo/o-spreadsheet/commit/fcdef4757 [IMP] renderer: draw cell background over grid lines [Task: 4552232](https://www.odoo.com/odoo/2328/tasks/4552232)
https://github.com/odoo/o-spreadsheet/commit/a865dbf2c [IMP] style: add `skipCellGridLines` style option [Task: 4552232](https://www.odoo.com/odoo/2328/tasks/4552232)
https://github.com/odoo/o-spreadsheet/commit/86856abfd [REF] table style: add `bold` to table style presets [Task: 4552232](https://www.odoo.com/odoo/2328/tasks/4552232)
https://github.com/odoo/o-spreadsheet/commit/351919f8f [REF] subtotal: extract SUBTOTAL tracking to generic plugin [Task: 4552232](https://www.odoo.com/odoo/2328/tasks/4552232)
https://github.com/odoo/o-spreadsheet/commit/4dee81dbe [IMP] Added some shortcuts [Task: 5231802](https://www.odoo.com/odoo/2328/tasks/5231802)
https://github.com/odoo/o-spreadsheet/commit/c7180d1f7 [FIX] tests: fix useless shortcuts tests [](https://www.odoo.com/odoo/2328/tasks/)
https://github.com/odoo/o-spreadsheet/commit/a30272f1f [IMP] Autocompletion of curly brackets {} [](https://www.odoo.com/odoo/2328/tasks/)
https://github.com/odoo/o-spreadsheet/commit/21e3d6155 [FIX] f&r: the searched range should follow the active sheet [Task: 5423885](https://www.odoo.com/odoo/2328/tasks/5423885)
https://github.com/odoo/o-spreadsheet/commit/20ee28aac [IMP] figure: add data-type attribute to figure carousel tabs [Task: 5447027](https://www.odoo.com/odoo/2328/tasks/5447027)
https://github.com/odoo/o-spreadsheet/commit/abb24152c [FIX] Style: UPDATE_CELL overwrites the cell style [Task: 5441149](https://www.odoo.com/odoo/2328/tasks/5441149)
https://github.com/odoo/o-spreadsheet/commit/a4792e26f [FIX] tests: fix network serialization in mock [Task: 5441149](https://www.odoo.com/odoo/2328/tasks/5441149)
https://github.com/odoo/o-spreadsheet/commit/ea607f07d [IMP] formulas: add spilled range operator [Task: 5365642](https://www.odoo.com/odoo/2328/tasks/5365642)
https://github.com/odoo/o-spreadsheet/commit/3b6e45921 [IMP] style: check if default but faster [Task: 5431688](https://www.odoo.com/odoo/2328/tasks/5431688)
https://github.com/odoo/o-spreadsheet/commit/abeea3e5d [FIX] Composer: Capture the correct selection on `F2` [Task: 5462713](https://www.odoo.com/odoo/2328/tasks/5462713)
https://github.com/odoo/o-spreadsheet/commit/7c556a916 [REF] lint: enforce braces for all control statements [Task: 0](https://www.odoo.com/odoo/2328/tasks/0)
Co-authored-by: Florian Damhaut (flda) <flda@odoo.com>
Co-authored-by: Anthony Hendrickx (anhe) <anhe@odoo.com>
Co-authored-by: Alexis Lacroix (laa) <laa@odoo.com>
Co-authored-by: Lucas Lefèvre (lul) <lul@odoo.com>
Co-authored-by: Adrien Minne (adrm) <adrm@odoo.com>
Co-authored-by: Ronak Mukeshbhai Bharadiya (rmbh) <rmbh@odoo.com>
Co-authored-by: Dhrutik Patel (dhrp) <dhrp@odoo.com>
Co-authored-by: Rémi Rahir (rar) <rar@odoo.com>
Co-authored-by: Pierre Rousseau (pro) <pro@odoo.com>
Co-authored-by: Vincent Schippefilt (vsc) <vsc@odoo.com>
Co-authored-by: Marceline Thomas (matho) <matho@odoo.com>This update simplifies pivot table styling within the Odoo Enterprise spreadsheet tool. Users no longer need to manually create tables to apply styles; new styles are directly linked to the pivot, offering greater flexibility and control over formatting and presentation.
Original PR description
With this commit, we don't need to manually create a dynamic table to a pivot to have a style applied. Instead we can add a style in the pivot definition, and dynamic tables will automatically be created on the dynamic pivot formulas. Those new pivot styles are better than traditional tables styles because: - they are directly linked to the pivot, taking into account the number of headers, the presence of totals, etc. - they are automatically added on `=PIVOT()` formulas, without the need to create a dynamic table first. - they are more powerful than the old table styles, they can have a style for the sub-headers, the measure headers, etc. Task: 4552232
This update reflects a recent change in the daily UMA (Wage Contribution) value mandated by INEGI for Mexico, effective February 1st, 2026. The new value of 117.31 MXN has been incorporated into the payroll calculations for Mexican employees, ensuring compliance with current regulations. This change impacts payroll processing for the 19.0 release.
Original PR description
As per the INEGI press release (published on January 8, 2026), the daily UMA value has been updated for 2026. New value: 117.31 MXN Effective date: February 1st, 2026. This commit adds this new parameter value to "Mexico: Daily UMA". Reference: https://www.inegi.org.mx/app/saladeprensa/noticia/10533 target: 19.0 task-5488243 Forward-Port-Of: odoo/enterprise#104064
This update enhances the visual appearance of Odoo’s onboarding samples across several modules, including loyalty and point-of-sale. By aligning the layout, colors, and icons with Odoo’s established UI standards, this change improves the overall user experience and ensures a more polished look for new users. This work addresses previous inconsistencies and strengthens brand consistency.
Original PR description
*: survey, point_of_sale, pos_restaurant - requires : https://github.com/odoo/enterprise/pull/98400 - extracted from: https://github.com/odoo/odoo/pull/228308 Before this commit, some onboarding suggestions were not fully aligned with Odoo’s UI standards. This commit readjusts the layout, colors, icons to ensure better visual consistency with others onboarding suggestions samples. task-5089102 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update enhances the visual appeal of the Odoo onboarding experience by aligning colors with Odoo’s design standards. The changes focus on improving the overall look and feel, ensuring a more polished and professional first impression for new users. This improves brand consistency and user experience.
Original PR description
*: marketing_automation_website_sale, marketing_automation_crm, appointment - requires : https://github.com/odoo/odoo/pull/233666 - extracted from : https://github.com/odoo/enterprise/pull/95384 Before this commit, some onboarding suggestions were not fully aligned with Odoo’s UI standards. This commit adjusts colors to ensure better visual consistency. task-5089102
5 changes
Enhancements to existing features
This update adds key reference fields – Buyer Reference, Contract Reference, and Purchase Order Reference – to the invoice PDF generated by the l10n_fr_facturx_chorus_pro module. These fields are required for Chorus Pro compliance, ensuring invoices meet the necessary documentation standards.
Original PR description
This commit: - Add three reference fields to invoice PDF for Chorus Pro compliance: Buyer Reference, Contract Reference, and Purchase Order Reference. These fields appear in the invoice header when set on the invoice. task-5410836 Forward-Port-Of: odoo/odoo#240494
This update allows system administrators to customize the main Odoo home menu with a targeted message. Administrators can set a message through a database configuration, such as a planned server maintenance notification. This provides a flexible way to communicate important information directly to users.
Original PR description
Display a message on home menu based on an ir.config_parameter that can be added directly in the database by the system administrator.
The ir.config_parameter is sysadmin.message and should be a json loadable. The format shoud be something like this:
{
"type": "warning",
"replace": false,
"warning_type": "user",
"message": "`<span>A maintenance operation is planned on your server on <strong>2026-01-15</strong> between 14h and 15h</span>`"
}
Forward-Port-Of: odoo/enterprise#103831
Forward-Port-Of: odoo/enterprise#102239This update improves how combo products are displayed during order preparation. Previously, the POS system split combo items into separate orderlines due to price differences. Now, the preparation display will combine these orderlines for the same product, streamlining the process and making it easier to manage orders.
Original PR description
When ordering a combo product, the POS will split the included products from the extra products in different orderlines. This is done because of the extra products have a different price/unit than the extra items. But for the preparation display we don't care about different prices, so this PR will make the different orderlines of the same combo be merged in the preparation display if they target the same product. Task-[5473387](https://www.odoo.com/odoo/project/1737/tasks/5473387) Enterprise PR-[#104188](https://github.com/odoo/enterprise/pull/104188) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update clarifies the certificate scope field in the Spanish EDI SII localization module. It now only displays this field when the company is located in Spain, preventing confusion for users working with other Odoo localizations. This ensures accurate reporting and simplifies the certificate management process for Spanish businesses.
Original PR description
Will make it visible the scope fiel only if the company country is ES. The field will remain invisible as defined in the certificate module for other cases. This way we avoid to show this field on certificates that use other localizations that can confuse to the user. 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
This update enhances error tracking within the Stripe expense module by providing full traceback logs when errors occur during webhook events. Additionally, a fix was implemented to prevent unnecessary communication with Stripe when a card is being destroyed, streamlining the process and improving efficiency.
Original PR description
## [IMP] hr_expense_stripe: full traceback logging When a pyhon error is raised during a webhook event we only get the error main line, not the full traceback. This adds the full traceback message to the log ## [FIX] hr_expense_stripe: Fix returned card error When a card is returned to the factory for destruction, when Stripe sends us the information, we sent a payload to stripe. This makes no sense as the card has been updated by Stripe into a state that doesn't allow further changes
4 changes
Enhancements to existing features
This update adds three new fields to Odoo invoice PDFs – Buyer Reference, Contract Reference, and Purchase Order Reference – to ensure compliance with Chorus Pro requirements. These fields allow users to accurately document key purchase information directly on the invoice, streamlining the Chorus Pro process. This change improves data accuracy and reporting.
Original PR description
This commit: - Add three reference fields to invoice PDF for Chorus Pro compliance: Buyer Reference, Contract Reference, and Purchase Order Reference. These fields appear in the invoice header when set on the invoice. task-5410836 Forward-Port-Of: odoo/odoo#240494
This update optimizes the process of determining user permissions for documents, resulting in faster performance. This change enhances the overall responsiveness of the Enterprise application when working with documents. It's a performance improvement focused on the Documents module.
Original PR description
This commit is a backport of the improvement introduced in the following commit 706ee0c68c774f01b76802fe513aec52df16678c.
This update enables public users to directly access documents without needing to create a user account. When a public user shares a document with a partner, the system now allows the partner to register and create a user account linked to that partner, streamlining the document sharing process. This improves usability for partners who don't want to create a full Odoo user.
Original PR description
Purpose ======= We can share a document to a partner without a user, and with `access_via_link == 'none'`. In that situation, the partner is forced to create a user, but if he clicks on signup, then the new user won't be linked to the partner set on the `documents.access` (a new partner will be created). Now, when inviting a member, if he doesn't have a user, we invite him to create a user. If the partner has a user, then we just redirect him to the login page. Task-5242208
This update simplifies the process of generating UBL invoices for Colombia and Mexico by refactoring internal code and automating the customer/supplier swap for vendor bills. This change enhances the flexibility and maintainability of the UBL export functionality, ensuring compliance with local tax regulations.
Original PR description
For the Self-billing backport, we made two modifications which entail a small change in the l10n_co_dian and l10n_mx_edi code: - `_check_move_constrains` has been refactored to call a new `_get_move_constraints` method, which is more easily extensible. We perform the same modification in l10n_mx_edi. Note `_check_move_constrains` is still there, so any overrides will still work. - The customer and supplier are now swapped by default when exporting a vendor bill UBL, so it's no longer needed to do this specifically for the DIAN UBL. Community PR: https://github.com/odoo/odoo/pull/232548 Backport of https://github.com/odoo/enterprise/pull/92205 task-5153851