Friday, December 27, 2024
35 changes · saas-18.1
Enhancements to existing features
This update standardizes how internal Odoo models are declared by requiring each one to explicitly state its model name or inheritance. It improves code consistency and maintainability across many apps without changing day-to-day user workflows.
Original PR description
This is a request following the revert of the use of class names (concerning the python inheritance and typing project) see: https://github.com/odoo/odoo/pull/178200 see: https://github.com/odoo/odoo/pull/186906
This update standardizes how internal business app components are declared across multiple Odoo modules. It reduces ambiguity for future development and maintenance, with no expected direct change to daily user workflows.
Original PR description
This is a request following the revert of the use of class names (concerning the python inheritance and typing project) see: https://github.com/odoo/odoo/pull/178200 see: https://github.com/odoo/odoo/pull/186906
Resolved issues and error corrections
The E-waybill creation button is no longer shown on journal entries, where creating an E-waybill is not applicable. This reduces confusion and prevents users from attempting an action that cannot be completed.
Original PR description
Before this commit: Whenever user posted a journal entry, `Create E-waybill` button is visible but practically it's not possible to have E-waybill for a journal entry In this commit: We hide the E-waybill button whenever a move type is an entry --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
Looks like the rebase in #191457 introduce a small mistake making the field exist check not working properly. This commit should fix the issue. Forward-Port-Of: odoo/odoo#191868
Original PR description
Looks like the rebase in #191457 introduce a small mistake making the field exist check not working properly. This commit should fix the issue. Forward-Port-Of: odoo/odoo#191868
The Point of Sale product barcode field no longer references a missing scanner component. This prevents unnecessary configuration issues and helps keep the product form behavior consistent.
Original PR description
Before this commit: === - The `productScanner` widget was assigned to the barcode field in the point_of_sale module, but this widget is not defined in the module. After this commit: === - The `productScanner` widget has been removed from the barcode field. Related: https://github.com/odoo/enterprise/pull/76250
The payment terminal provider selector in Point of Sale payment method settings now uses the available form space instead of being squeezed into a narrow column. This makes provider options legible and easier to configure for stores using payment terminals or online payments.
Original PR description
Payment terminal providers for a payment method, were displayed in a grid, whose width was blocked to the width of the label in the form wiew, making them illegible. Before:  After: 
Fixed a display issue in Point of Sale where payment provider cards did not use the full width of their container. This keeps the payment setup screen looking consistent and easier to read after a recent layout change.
Original PR description
Payment provider card didn't take the full with of the parent container, that was due to a recent change of o_cell_custom. Adding a CSS rules in point_of_sale to override this change.
The product barcode field now uses the scanner-friendly input in the normalized product form view. This helps point-of-sale users scan or enter product barcodes more reliably and consistently.
Original PR description
In this commit: === - The `productScanner` widget has been added to the barcode field in the normalized form view for better functionality. Related: https://github.com/odoo/odoo/pull/191897
Before this commit, the link popover contained three button styles, default, fill, and flat, which were visually identical. Here’s a summary of each: default: Based on the website module and influenced by the theme. fill: Not affected by theme choice. flat: Specific to the website module. After this commit, the redundant default and flat styles have been removed, as they are only relevant within the website module. The code has been cleaned up to improve maintainability, and tests have b
Original PR description
Before this commit, the link popover contained three button styles, default, fill, and flat, which were visually identical. Here’s a summary of each: default: Based on the website module and influenced by the theme. fill: Not affected by theme choice. flat: Specific to the website module. After this commit, the redundant default and flat styles have been removed, as they are only relevant within the website module. The code has been cleaned up to improve maintainability, and tests have been updated to reflect these changes. task-4240795 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#187237
**Current behavior before PR:** In some url, opening link preview displays special characters as string instead of parsed characters inside description of link preview popover. **Desired behavior after PR is merged:** Now special characters are getting parsed before displaying on popover. task-4345237 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#188576
Original PR description
**Current behavior before PR:** In some url, opening link preview displays special characters as string instead of parsed characters inside description of link preview popover. **Desired behavior after PR is merged:** Now special characters are getting parsed before displaying on popover. task-4345237 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#188576
Description of the issue this PR addresses: Current behavior before PR: Previously, typing after selecting all text using Ctrl+A would reset the font style of the anchorNode of the selection. Desired behavior after PR is merged: Typing after selecting all text using Ctrl+A keeps the font style of the anchorNode of the selection. task-4426710 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#191500
Original PR description
Description of the issue this PR addresses: Current behavior before PR: Previously, typing after selecting all text using Ctrl+A would reset the font style of the anchorNode of the selection. Desired behavior after PR is merged: Typing after selecting all text using Ctrl+A keeps the font style of the anchorNode of the selection. task-4426710 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#191500
**Current behavior before PR:** When transforming an image, if we click on transform button again, it resets the transformation of that image but transform button remain active. **Desired behavior after PR is merged:** Now, If transformation container is open and user clicks on transform button then image gets reset and button gets inactive as there is no transformation. task-4251662 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr For
Original PR description
**Current behavior before PR:** When transforming an image, if we click on transform button again, it resets the transformation of that image but transform button remain active. **Desired behavior after PR is merged:** Now, If transformation container is open and user clicks on transform button then image gets reset and button gets inactive as there is no transformation. task-4251662 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#190556 Forward-Port-Of: odoo/odoo#189588
Add individual CLA for Dorin Hongu This commit adds the Individual Contributor License Agreement (CLA) for Dorin Hongu. It includes their signature, authorization statement, and contact information as per standard requirements. 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#191862
Original PR description
Add individual CLA for Dorin Hongu This commit adds the Individual Contributor License Agreement (CLA) for Dorin Hongu. It includes their signature, authorization statement, and contact information as per standard requirements. 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#191862
The informations displayed on journal dashboard on sale/purchase journals should include both invoices/bills and credit notes/refunds, as well as the moves shown in the list view when coming from the journal card hyperlinks. opw-4328137 Forward-Port-Of: odoo/odoo#188819 Forward-Port-Of: odoo/odoo#187692
Original PR description
The informations displayed on journal dashboard on sale/purchase journals should include both invoices/bills and credit notes/refunds, as well as the moves shown in the list view when coming from the journal card hyperlinks. opw-4328137 Forward-Port-Of: odoo/odoo#188819 Forward-Port-Of: odoo/odoo#187692
**Issue:** No tooltips are displayed on hovering CRM leads stages in Kanban view. **Expected:** As for versions up to 17.4, on hovering the stage, if requirements are set, a tooltip box should appear. **Steps to reproduce:** - Activate CRM app; - Open a CRM leads pipeline in Kanban view; - Edit a stage by adding a requirement text and save; - Place the mouse over the stage and wait. **Cause:** The tooltip box display has been removed for over simplification. **Fix:** Add a to
Original PR description
**Issue:** No tooltips are displayed on hovering CRM leads stages in Kanban view. **Expected:** As for versions up to 17.4, on hovering the stage, if requirements are set, a tooltip box should appear. **Steps to reproduce:** - Activate CRM app; - Open a CRM leads pipeline in Kanban view; - Edit a stage by adding a requirement text and save; - Place the mouse over the stage and wait. **Cause:** The tooltip box display has been removed for over simplification. **Fix:** Add a tooltip box display based on stage title hover and reverting 1 line of https://github.com/odoo-dev/odoo/commit/232c218d87a94e1d77fc69afdbfd77e340504cad#diff-62eff7f830df5fbafad68abd5de0373654a620f6685cbcf3a4b8c20db64f0b7cL540. opw-4359292 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#189275
Description of the issue this PR addresses: I. Removing formatting on text with a background color inside a fully selected table triggers an infinite loop in `removeAllColor`. This happened because applying background color to selected table cells filtered out child nodes in each `<td>` to apply background color directly to the cell. However, this filtering should be skipped when there is no color to apply, such as when removing background color. II. This PR fixes an issue where the backgr
Original PR description
Description of the issue this PR addresses: I. Removing formatting on text with a background color inside a fully selected table triggers an infinite loop in `removeAllColor`. This happened because applying background color to selected table cells filtered out child nodes in each `<td>` to apply background color directly to the cell. However, this filtering should be skipped when there is no color to apply, such as when removing background color. II. This PR fixes an issue where the background color of a table cell could not be removed when clearing formatting. task-4333327 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#187355
Description of the issue this PR addresses: Current behavior before PR: When opening the chatGPT Translate dialog or Alternatives dialog without any selected text it used to provide incorrect output. Desired behavior after PR is merged: Ensure that both dialogs display an error message if no text is selected. task-4325385 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#189645 Forward-Port-Of: odoo/odoo#186868
Original PR description
Description of the issue this PR addresses: Current behavior before PR: When opening the chatGPT Translate dialog or Alternatives dialog without any selected text it used to provide incorrect output. Desired behavior after PR is merged: Ensure that both dialogs display an error message if no text is selected. task-4325385 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#189645 Forward-Port-Of: odoo/odoo#186868
Some modules may have python packages with hyphen in the external_dependies (google-auth-oauthlib, ...) Those module cannot be installed anymore. Fixing the regex to allow hyphen in external dependencies when packaging is not installed. Forward-Port-Of: odoo/odoo#191334
Original PR description
Some modules may have python packages with hyphen in the external_dependies (google-auth-oauthlib, ...) Those module cannot be installed anymore. Fixing the regex to allow hyphen in external dependencies when packaging is not installed. Forward-Port-Of: odoo/odoo#191334
A new account template got the id pcg_468. The issue is that it is the same as a previous group. When you reload the CoA, it will try to access the data behind each xmlid of account template. It will then access a group template thinking it's an account, resulting in a bad field access and a traceback. Appeared due to a bad fw-port of https://github.com/odoo/odoo/commit/0ebf80b613d229ef5fb07ea97d406496f9df6254 (also fixed the typo in the code) --- I confirm I have signed the CL
Original PR description
A new account template got the id pcg_468. The issue is that it is the same as a previous group. When you reload the CoA, it will try to access the data behind each xmlid of account template. It will then access a group template thinking it's an account, resulting in a bad field access and a traceback. Appeared due to a bad fw-port of https://github.com/odoo/odoo/commit/0ebf80b613d229ef5fb07ea97d406496f9df6254 (also fixed the typo in the code) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#191827
Steps to reproduce the bug: - Enable “Subcontracting” and “Expiration Date” in MRP settings. - Create a storable product “P1” with the following configurations: - tracked by: LOT - Expiration date: True - BoM: - BoM type: subcontracting - subcontractor: Azure interior - Create a lot “L1” with an expiration date set to 01-01-2026. - Expiration date: 01-01-2026 - Configure the operation type:: - Receipt: - use existing SN: True - Crea
Original PR description
Steps to reproduce the bug: - Enable “Subcontracting” and “Expiration Date” in MRP settings. - Create a storable product “P1” with the following configurations: - tracked by: LOT - Expiration date:…
Steps to reproduce the bug:
- Enable “Subcontracting” and “Expiration Date” in MRP settings.
- Create a storable product “P1” with the following configurations:
- tracked by: LOT
- Expiration date: True
- BoM:
- BoM type: subcontracting
- subcontractor: Azure interior
- Create a lot “L1” with an expiration date set to 01-01-2026.
- Expiration date: 01-01-2026
- Configure the operation type::
- Receipt:
- use existing SN: True
- Create a receipt:
- Receive from: Azure interior
- Product: one unit of P1
- Mark it as todo
- Open the detailed operation:
- Set the “L1”
- Record production
- Reopen the detailed operation
Problem:
The expiration date in the stock.move.line is set to today’s date instead of the lot’s expiration date.
Cause:
When marking the receipt as “To Do,” the SML is created. Since no lot_id is initially set, today’s date is assigned, thanks to the _compute_expiration_date method:
https://github.com/odoo/odoo/blob/9f1d555ac2d9b6e9d3d0d723d4f042eb44cf30b7/addons/product_expiry/models/stock_move_line.py#L37-L40
But When the lot_id is later set, the compute method is triggered again. However, since the SML already contains a date, the expiration date is not updated to match the lot’s expiration date.
opw-4394662
Forward-Port-Of: odoo/odoo#190747The active CSS class was not applied to parent items of the mega menu or their child items, resulting in the corresponding menu item not being highlighted in the navigation bar. This commit ensures that the active class is correctly applied to mega menu items, providing consistent highlighting behavior similar to regular pages. Steps to reproduce: - Open the Website Editor. - Navigate to Site > Menu Editor. - Add a Mega Menu and save the changes. - Edit the page. - Open the Mega Men
Original PR description
The active CSS class was not applied to parent items of the mega menu or their child items, resulting in the corresponding menu item not being highlighted in the navigation bar. This commit ensures that the active class is correctly applied to mega menu items, providing consistent highlighting behavior similar to regular pages. Steps to reproduce: - Open the Website Editor. - Navigate to Site > Menu Editor. - Add a Mega Menu and save the changes. - Edit the page. - Open the Mega Menu. - Change any link to /contactus-thank-you. - Save the changes. - Visit /contactus-thank-you. - Observe that the Mega Menu title does not appear as active opw-4383641 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#190321
Fix blank screen when going on receipt screen. That was due to the creation of a new order on websocket messages. Forward-Port-Of: odoo/odoo#191696 Forward-Port-Of: odoo/odoo#191526
Original PR description
Fix blank screen when going on receipt screen. That was due to the creation of a new order on websocket messages. Forward-Port-Of: odoo/odoo#191696 Forward-Port-Of: odoo/odoo#191526
Chilean users cannot succesfully create the credit note (with document type 61) of a Vendori bill (type 46) because of a conflict on the document number input method - Open Vendor Bills journal and enable 'Use Documents?' - Create a Bill with document type '(46) Factura de Compra Electrónica' - Create the credit note - In the Wizard: select 'Full Refund', Document Type 61, Confirm Issue: The system blocks the action because the new move is missing the document number opw-4268371 For
Original PR description
Chilean users cannot succesfully create the credit note (with document type 61) of a Vendori bill (type 46) because of a conflict on the document number input method - Open Vendor Bills journal and enable 'Use Documents?' - Create a Bill with document type '(46) Factura de Compra Electrónica' - Create the credit note - In the Wizard: select 'Full Refund', Document Type 61, Confirm Issue: The system blocks the action because the new move is missing the document number opw-4268371 Forward-Port-Of: odoo/odoo#188481
Before this commit: 1. Install pos_stripe & pos_restaurant 2. Create a PoS payment method wish Stripe Terminal setup with dummy (wrong) value. ! Purposfully DON'T set up the Stripe account (so let it as deactivate) 3. Add the payment method to the bar PoS 4. Open the bar PoS, make an order and try to pay by the stripe payment method => JS error ```js undefined undefined OwlError: Invalid props for component 'AlertDialog': 'body' is not a string Error: Invalid props for comp
Original PR description
Before this commit: 1. Install pos_stripe & pos_restaurant 2. Create a PoS payment method wish Stripe Terminal setup with dummy (wrong) value. ! Purposfully DON'T set up the Stripe account (so let it…
Before this commit:
1. Install pos_stripe & pos_restaurant
2. Create a PoS payment method wish Stripe Terminal setup with dummy (wrong) value. ! Purposfully DON'T set up the Stripe account (so let it as deactivate)
3. Add the payment method to the bar PoS
4. Open the bar PoS, make an order and try to pay by the stripe payment method
=> JS error
```js
undefined
undefined
OwlError: Invalid props for component 'AlertDialog': 'body' is not a string
Error: Invalid props for component 'AlertDialog': 'body' is not a string
at Object.validateProps (http://127.0.0.1:8069/web/assets/debug/point_of_sale.assets_prod.js:11392:19) (/web/static/lib/owl/owl.js:3160)
at DialogWrapper.template (eval at compile (http://127.0.0.1:8069/web/assets/debug/point_of_sale.assets_prod.js:13846:20), <anonymous>:10:13) (/web/static/lib/owl/owl.js:5614)
at Fiber._render (http://127.0.0.1:8069/web/assets/debug/point_of_sale.assets_prod.js:9961:38) (/web/static/lib/owl/owl.js:1729)
at Fiber.render (http://127.0.0.1:8069/web/assets/debug/point_of_sale.assets_prod.js:9953:18) (/web/static/lib/owl/owl.js:1721)
at ComponentNode.initiateRender (http://127.0.0.1:8069/web/assets/debug/point_of_sale.assets_prod.js:10633:23) (/web/static/lib/owl/owl.js:2401)
```
This error hide the real error as the error dialog expect to receive a string while it receive an Error object
After this commit:
The (real) error is logged to the console:
```js
payment_stripe.js:272 SyntaxError: "undefined" is not valid JSON
at JSON.parse (<anonymous>)
at Proxy.connectReader (payment_stripe.js:87:1)
at Proxy.checkReader (payment_stripe.js:79:1)
at Proxy.send_payment_request (payment_stripe.js:268:1)
at async Proxy.pay (pos_payment.js:74:1)
at async PaymentScreen.sendPaymentRequest (payment_screen.js:545:1)
```
and the error dialog shows with the string of the error, here: `SyntaxError: "undefined" is not valid JSON`
We will not have the traceback in the client message as I didn't find a way to do so except letting the error propagate. But this might have side effects so I didn't used this option.
opw-4375876
Forward-Port-Of: odoo/odoo#191356Steps to reproduce the bug: - Go to the website edit mode. - Drag and drop a "Text - Image" block onto the page. - Drag and drop a "Media List" block at the bottom of the page. - Drag and drop a "Text" block at the bottom of the page. - Click on the "Text" block. - In the "Text" block options, click the "Create a link to target this section" button. - Click on the "Button" inside the "Text - Image" block. - In the options, paste the "link" to the anchor copied to the clipboard into the
Original PR description
Steps to reproduce the bug: - Go to the website edit mode. - Drag and drop a "Text - Image" block onto the page. - Drag and drop a "Media List" block at the bottom of the page. - Drag and drop a…
Steps to reproduce the bug: - Go to the website edit mode. - Drag and drop a "Text - Image" block onto the page. - Drag and drop a "Media List" block at the bottom of the page. - Drag and drop a "Text" block at the bottom of the page. - Click on the "Text" block. - In the "Text" block options, click the "Create a link to target this section" button. - Click on the "Button" inside the "Text - Image" block. - In the options, paste the "link" to the anchor copied to the clipboard into the URL input of the button. - In the "Column" options, add an "On Scroll" animation to the column. - Save the page. - Click the "Text - Image" button. - Bug: the page doesn't scroll to the "Text" block. This bug was introduced by commit [1], where the "overflow-x: hidden" CSS rule, used to prevent a horizontal scrollbar during animations caused by overflowing content on the right side of the page, was moved from the HTML element to the body element. The bug appeared because when the code triggering the scroll animation to the anchor runs after clicking the button, it checks which element is scrollable. At that moment, the body has "overflow-x: hidden," which causes its "overflow-y" to become "auto" instead of "visible" (browser behavior, see https://developer.mozilla.org/en-US/docs/Web/CSS/overflow). The body element is then considered scrollable, even though it isn't. This is why the scroll animation doesn't work. To fix this, we replace "overflow-x: hidden" with "overflow-x: clip". This is more appropriate in this context and prevents "overflow-y" from becoming "auto". We also add "display: flow-root;" in combination with "overflow: clip" because without it, "overflow: clip" alone may not be sufficient to prevent elements inside "body" from overflowing, particularly animated elements in Firefox. This creates a new formatting context, preventing unexpected overflow behavior across different browsers. [1]: https://github.com/odoo/odoo/commit/fece9cb85761e6cb3fe3642f947661464402363b opw-4393527 Forward-Port-Of: odoo/odoo#191481
This commit adds the parameter `sanitize_overridable=True` to the `description` field of `website_slides` slides. It means that the description can now be properly edited as an user with enough rights. The issue is that the `slide.description` field is sanitized after saving a `slide/*` page, which removes `<button>` elements. This is not easily testable in version 16.0 because no blocks contain `<button>` elements. However, starting from version 18.0, new blocks like the `accordion` block in
Original PR description
This commit adds the parameter `sanitize_overridable=True` to the `description` field of `website_slides` slides. It means that the description can now be properly edited as an user with enough rights. The issue is that the `slide.description` field is sanitized after saving a `slide/*` page, which removes `<button>` elements. This is not easily testable in version 16.0 because no blocks contain `<button>` elements. However, starting from version 18.0, new blocks like the `accordion` block include buttons, and these are removed after saving a `slide/*` page when they are dropped into it. opw-4273436 Forward-Port-Of: odoo/odoo#190620
This commit prevents dropping an "inner content" block into an image field. Steps to reproduce: - Go to the "/shop" page. - Click on one of the products to go to its product page. - Enter edit mode. - Bug: It is possible to drop any "inner content" block into the "product" image field. This commit also fixes the following bug: - Go to the homepage in edit mode. - Drag and drop a "text-image" block onto the page. - Drag and drop a "badge" (or any other "inner content" block) un
Original PR description
This commit prevents dropping an "inner content" block into an image field. Steps to reproduce: - Go to the "/shop" page. - Click on one of the products to go to its product page. - Enter edit mode. - Bug: It is possible to drop any "inner content" block into the "product" image field. This commit also fixes the following bug: - Go to the homepage in edit mode. - Drag and drop a "text-image" block onto the page. - Drag and drop a "badge" (or any other "inner content" block) under the image. This is possible, and it's the intended behavior. - Click on the image and add a link to it. - Bug: Try dragging and dropping a "badge" under the image again, it is no longer possible. [opw-4273436](https://www.odoo.com/web#id=4273436&cids=1&menu_id=4720&action=333&active_id=1695&model=project.task&view_type=form) Forward-Port-Of: odoo/odoo#191285 Forward-Port-Of: odoo/odoo#190732
In this commit: =============== - Display a warning alert on the homepage when no HTTPS certificate is linked or there's an issue with the certificate, and the technical tab is inactive. - The alert notifies the user that their IoT Box subscription is not linked and advises contacting the account manager to unlock full potential. - On opening the technical tab, show a detailed error code retrieved from the IoT Box to assist in diagnosing HTTPS certificate issues. Task-4364406
Original PR description
In this commit: =============== - Display a warning alert on the homepage when no HTTPS certificate is linked or there's an issue with the certificate, and the technical tab is inactive. - The alert notifies the user that their IoT Box subscription is not linked and advises contacting the account manager to unlock full potential. - On opening the technical tab, show a detailed error code retrieved from the IoT Box to assist in diagnosing HTTPS certificate issues. Task-4364406 Related enterprise PR-https://github.com/odoo/enterprise/pull/74949  Forward-Port-Of: odoo/odoo#189263
In this commit: - Updated the error message for retrieving the Bearer Token during Viva Wallet payment requests. - The new message clearly states: `Unable to retrieve Viva Wallet Bearer Token: Please verify that the Client ID and Client Secret are correct` - This improvement provides more explicit guidance to users, making it easier to identify and resolve configuration issues. task- 4383616 Forward-Port-Of: odoo/odoo#191765
Original PR description
In this commit: - Updated the error message for retrieving the Bearer Token during Viva Wallet payment requests. - The new message clearly states: `Unable to retrieve Viva Wallet Bearer Token: Please verify that the Client ID and Client Secret are correct` - This improvement provides more explicit guidance to users, making it easier to identify and resolve configuration issues. task- 4383616 Forward-Port-Of: odoo/odoo#191765
**Before this PR:** In studio, in some report, trying to add a video using video commnad throws traceback. Adding a video doesn't make sense in a report so the video command shouldn't be available in report at the first place. **After this PR:** This commit aims to remove video command from studio report. task-4285231 Forward-Port-Of: odoo/enterprise#73971
Original PR description
**Before this PR:** In studio, in some report, trying to add a video using video commnad throws traceback. Adding a video doesn't make sense in a report so the video command shouldn't be available in report at the first place. **After this PR:** This commit aims to remove video command from studio report. task-4285231 Forward-Port-Of: odoo/enterprise#73971
Update the open sale/purchase journals query to include credit notes/refunds, and override the 'Bills to validate' filter to be consistent with the dashboard query which is overridden for `account_3way_match` Forward-Port-Of: odoo/enterprise#74765
Original PR description
Update the open sale/purchase journals query to include credit notes/refunds, and override the 'Bills to validate' filter to be consistent with the dashboard query which is overridden for `account_3way_match` Forward-Port-Of: odoo/enterprise#74765
Currently, while we send the carrier and the tracking number, we don't send the shipping method. While this doesn't block anything, this lead to Amazon sending warning about incomplete shipping information. Now, we will send: - Carrier name : the delivery_type if any relevant, else the carrier name as fallback. eg: "DHL" - The shipping method: the carrier name. eg: "DHL Express" or "Parcel" opw-4393663 Forward-Port-Of: odoo/enterprise#76156
Original PR description
Currently, while we send the carrier and the tracking number, we don't send the shipping method. While this doesn't block anything, this lead to Amazon sending warning about incomplete shipping information. Now, we will send: - Carrier name : the delivery_type if any relevant, else the carrier name as fallback. eg: "DHL" - The shipping method: the carrier name. eg: "DHL Express" or "Parcel" opw-4393663 Forward-Port-Of: odoo/enterprise#76156
Users creating a debit note from an invoice will need to pay attention to the document type that, with the EDI module installed, is set by taking into account only the partner 'Taxpayer Type' and not the move type (i.e. debit note) - Have an invoice with document type "(33) Factura Electrónica" accepted by SII - Create the debit note from the invoice Issue: default document type will be 33, while it should be 56 opw-4292111 Forward-Port-Of: odoo/enterprise#76011
Original PR description
Users creating a debit note from an invoice will need to pay attention to the document type that, with the EDI module installed, is set by taking into account only the partner 'Taxpayer Type' and not the move type (i.e. debit note) - Have an invoice with document type "(33) Factura Electrónica" accepted by SII - Create the debit note from the invoice Issue: default document type will be 33, while it should be 56 opw-4292111 Forward-Port-Of: odoo/enterprise#76011
Purpose ======= When creating a shortcut to a document we can't access, an error is raised, because of side effect. This commit make the verification explicit. Task-4409538 Forward-Port-Of: odoo/enterprise#75656
Original PR description
Purpose ======= When creating a shortcut to a document we can't access, an error is raised, because of side effect. This commit make the verification explicit. Task-4409538 Forward-Port-Of: odoo/enterprise#75656
In this commit: ================ This commit updates text strings Task-4364406 Related community PR-https://github.com/odoo/odoo/pull/189263 Forward-Port-Of: odoo/enterprise#74949
Original PR description
In this commit: ================ This commit updates text strings Task-4364406 Related community PR-https://github.com/odoo/odoo/pull/189263 Forward-Port-Of: odoo/enterprise#74949