Tuesday, May 6, 2025
28 changes · saas-18.1
Resolved issues and error corrections
The mail composer now correctly hides the file upload option when uploads are disabled, including in spreadsheet cell discussions. This prevents users from seeing an action they are not allowed to use, making the interface more consistent and less confusing.
Original PR description
## Description In spreadsheet cell thread, setting `allowUpload` to false did not hide the file upload button in the composer. This was due to missing `allowUpload` checks within the composer actions logic. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update keeps WhatsApp attachment upload checks in one place, making the composer behave more consistently. It reduces the chance of upload controls appearing incorrectly and helps maintain a smoother messaging experience.
Original PR description
## Description Instead of checking thread type and attachment count in composer actions, override the allowUpload method in the WhatsApp composer patch to encapsulate the condition logic.
Miscellaneous changes
- when an employees has a flex calendar the custom hours leaves should not be limited to the avg_hours_per_day Task: 4744248 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#208427
Original PR description
- when an employees has a flex calendar the custom hours leaves should not be limited to the avg_hours_per_day Task: 4744248 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#208427
Before this commit, the "Analytic Items" and "Analytic Report" menu items were visible even when the analytic feature was disabled, leading to potential confusion. To address this: - "Analytic Items": The solution is to restrict visibility by keeping only the `group_analytic_accounting` group and removing all the other groups. - "Analytic Report": After consideration, it was decided to leave this menu item with `group_account_readonly`. While this is not a perfect solution, it remains the b
Original PR description
Before this commit, the "Analytic Items" and "Analytic Report" menu items were visible even when the analytic feature was disabled, leading to potential confusion. To address this: - "Analytic…
Before this commit, the "Analytic Items" and "Analytic Report" menu items were visible even when the analytic feature was disabled, leading to potential confusion. To address this: - "Analytic Items": The solution is to restrict visibility by keeping only the `group_analytic_accounting` group and removing all the other groups. - "Analytic Report": After consideration, it was decided to leave this menu item with `group_account_readonly`. While this is not a perfect solution, it remains the best option compared to the alternatives: - Making it visible to everyone when the analytic feature is enabled, which would grant access too broadly. - Creating a dedicated parent menu item to set `group_account_readonly` at the parent level and `group_analytic_accounting` at the child level. However, this would introduce unnecessary complexity and negatively impact the UI/UX. task-4497442 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#199242
…dd it in the tax details 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#208205 Forward-Port-Of: odoo/odoo#206052
Original PR description
…dd it in the tax details 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#208205 Forward-Port-Of: odoo/odoo#206052
When settling an order from the POS, the amount to invoice was not correctly computed. Steps to reproduce: ------------------- * Create a draft sale order with a product * Go to the POS and select the order * Pay for the order * Go to the backend and check the amount to invoice > Observation: The amount to invoice is still the full order amount Why the fix: ------------ We should take into account the PoS payment lines when computing the amount to invoice of an order. opw-460367
Original PR description
When settling an order from the POS, the amount to invoice was not correctly computed. Steps to reproduce: ------------------- * Create a draft sale order with a product * Go to the POS and select the order * Pay for the order * Go to the backend and check the amount to invoice > Observation: The amount to invoice is still the full order amount Why the fix: ------------ We should take into account the PoS payment lines when computing the amount to invoice of an order. opw-4603671 Forward-Port-Of: odoo/odoo#208004 Forward-Port-Of: odoo/odoo#202950
…l10n_es_type Probably forgotten to update the agriculture changes when splitting the csv file for the Canary Islands CoA. Runbot error 161596 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#208122
Original PR description
…l10n_es_type Probably forgotten to update the agriculture changes when splitting the csv file for the Canary Islands CoA. Runbot error 161596 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#208122
Analytic distribution is not tracked when synchronising the tax line Steps: - Have an income account X with a sale tax set - Create a journal entry with one line, having account X and debit xxx$ - Save the form, two lines should have been created, auto balancing line and tax line - Set an analytic distribution on these two lines and save the form -> The analytic distribution is unset from the tax line Before this commit, we were keeping values of `amount_currency` and `balance`, now we ke
Original PR description
Analytic distribution is not tracked when synchronising the tax line Steps: - Have an income account X with a sale tax set - Create a journal entry with one line, having account X and debit xxx$ - Save the form, two lines should have been created, auto balancing line and tax line - Set an analytic distribution on these two lines and save the form -> The analytic distribution is unset from the tax line Before this commit, we were keeping values of `amount_currency` and `balance`, now we keep also `analytic_distribution` in the tracked fields opw-4662784 Forward-Port-Of: odoo/odoo#205551
PROBLEM 1: Steps to reproduce: - Create branch company - Create a user for the branch company and assign the bookkeeper role - Log in as the newly created user - Inside accounting module navigate to Vendor menu -> Payment - Create a payment and set the amount - Attempt to edit the payment Error:- Access Error: Access to unauthorized or invalid companies. Cause: Before this pr, the context passed during the accessible branches calculation included 'journal_id.company_id' (i.e., t
Original PR description
PROBLEM 1: Steps to reproduce: - Create branch company - Create a user for the branch company and assign the bookkeeper role - Log in as the newly created user - Inside accounting module navigate to…
PROBLEM 1: Steps to reproduce: - Create branch company - Create a user for the branch company and assign the bookkeeper role - Log in as the newly created user - Inside accounting module navigate to Vendor menu -> Payment - Create a payment and set the amount - Attempt to edit the payment Error:- Access Error: Access to unauthorized or invalid companies. Cause: Before this pr, the context passed during the accessible branches calculation included 'journal_id.company_id' (i.e., the parent company_id). This led to an error during validation in the companies method of the env class, since the parent company_id is not valid for branch-specific operations/users. Solution: After this pr, remove the context modification introduced by the 'with_company()' method during the invocation of '_accessible_branches()', ensuring that the correct branch context is used for access validation. PROBLEM 2: Steps to reproduce: - First 3 steps are same as problem 1 - Inside accounting module navigate to bank reconciliation list view - Create new bank statement line - Attempt to edit the bank statement line Error:- Access Error: because of company rule employee Cause: Before this pr, in the '_synchronize_to_moves' method the 'company_currency' calculation included 'journal.company_id.currency_id' in which 'journal.company_id' is the parent company_id to which the user does not have access. Solution: After this pr, adding 'sudo()' method call at the time of accessing 'journal.comapny_id' (i.e., parent company_id) for bypassing the access rights. Task - 4654866 Forward-Port-Of: odoo/odoo#208461 Forward-Port-Of: odoo/odoo#205548
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#206849
Original PR description
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#206849
Before this commit, the session closing message was in the method called from the UI. But in case of error during the closing control, the user must close it from the backend. In this case, the message was not sent to all devices. This commit moves the message to the write method of the session to ensure that the message is sent to all devices, even if the session is closed from the backend. Forward-Port-Of: odoo/odoo#208373
Original PR description
Before this commit, the session closing message was in the method called from the UI. But in case of error during the closing control, the user must close it from the backend. In this case, the message was not sent to all devices. This commit moves the message to the write method of the session to ensure that the message is sent to all devices, even if the session is closed from the backend. Forward-Port-Of: odoo/odoo#208373
At the moment, whenever the partner is changed on an invoice, the l10n_latam_document_type_id field is recomputed and re-set to the default value corresponding to the partner and invoice type. We don't want this to happen if the existing l10n_latam_document_type_id is already compatible with the new partner. opw-4168385 Forward-Port-Of: odoo/odoo#208324 Forward-Port-Of: odoo/odoo#195581
Original PR description
At the moment, whenever the partner is changed on an invoice, the l10n_latam_document_type_id field is recomputed and re-set to the default value corresponding to the partner and invoice type. We don't want this to happen if the existing l10n_latam_document_type_id is already compatible with the new partner. opw-4168385 Forward-Port-Of: odoo/odoo#208324 Forward-Port-Of: odoo/odoo#195581
Versions -------- - 18.0+ Steps ----- 1. Have a combo product with only items that are invoiced on delivery; 2. add it to a sale order; 3. validate the delivery; 4. create & confirm an invoice. Issue ----- The sale order is still invoicable. Cause ----- The `qty_to_invoice` field for the combo item line isn't being updated when its linked lines were delivered. Solution -------- Add `linked_line_ids.qty_delivered` to the `api.depends` of the compute method. opw-4633972
Original PR description
Versions -------- - 18.0+ Steps ----- 1. Have a combo product with only items that are invoiced on delivery; 2. add it to a sale order; 3. validate the delivery; 4. create & confirm an invoice. Issue ----- The sale order is still invoicable. Cause ----- The `qty_to_invoice` field for the combo item line isn't being updated when its linked lines were delivered. Solution -------- Add `linked_line_ids.qty_delivered` to the `api.depends` of the compute method. opw-4633972 Forward-Port-Of: odoo/odoo#205499
**Problem:** When clicking the button Purchase Matching, in a Vendor Bill, if the vendor is an individual but has a company, the bill will not appear below the Purchase Orders. If the vendor is an individual without a company, the Purchase Matching button will display everything like it should. **Steps to reproduce:** - Make a Purchase Order, the vendor has to be an individual with a company. - Create a bill for the same product and vendor. - Use the Purchase Matching button on the bi
Original PR description
**Problem:** When clicking the button Purchase Matching, in a Vendor Bill, if the vendor is an individual but has a company, the bill will not appear below the Purchase Orders. If the vendor is an…
**Problem:** When clicking the button Purchase Matching, in a Vendor Bill, if the vendor is an individual but has a company, the bill will not appear below the Purchase Orders. If the vendor is an individual without a company, the Purchase Matching button will display everything like it should. **Steps to reproduce:** - Make a Purchase Order, the vendor has to be an individual with a company. - Create a bill for the same product and vendor. - Use the Purchase Matching button on the bill. - The bill is not displayed, but the Purchase Orders are. **Cause of the issue:** https://github.com/odoo/odoo/blob/cc9e7cb92f1a6237a496b9acabd93506a8724a62/addons/purchase/models/account_invoice.py#L143-L144 The partner_id for the Purchase Orders are the current individual vendor, but we are trying to match it with the partner_id of an Account Move Line, which is set to be the commercial partner of the individual, meaning the company, as seen below. https://github.com/odoo/odoo/blob/9e9e992698946b75212040ca0ff812194200a8bf/addons/account/models/account_move_line.py#L481-L483 On the matching table, we use the partner of the Account Move Line, and this is the why filtering on the individual doesn't give any result, if we wanted some we would need to filter on the company. https://github.com/odoo/odoo/blob/45533a1c6a70a3b86cf744a0f950c92d8a99afcf/addons/purchase/models/purchase_bill_line_match.py#L109 **Fix:** The domain was updated to take both the individual and the commercial partner (the company). This ensures that the bill will be found even in we are dealing with an individual that is in a company. opw-4577643 Forward-Port-Of: odoo/odoo#202012
### Steps to reproduce: - Install "l10n_it" and switch to an Italian company - Change the currency exchange rate so USD and EUR are not equal - Create a vendor bill or invoice in USD, with at least one product and a price higher than 0 - Confirm, send and inspect the XML generated for the SDI - The value of PrezzoTotale is different than PrezzoUnitario*Quantita ### Cause: "prezzo_unitario" is rounded during the currency conversion. ([see](https://github.com/odoo/odoo/blob/9a48804ed07779
Original PR description
### Steps to reproduce: - Install "l10n_it" and switch to an Italian company - Change the currency exchange rate so USD and EUR are not equal - Create a vendor bill or invoice in USD, with at least one product and a price higher than 0 - Confirm, send and inspect the XML generated for the SDI - The value of PrezzoTotale is different than PrezzoUnitario*Quantita ### Cause: "prezzo_unitario" is rounded during the currency conversion. ([see](https://github.com/odoo/odoo/blob/9a48804ed07779692da2952476d3906d1abfa302/addons/l10n_it_edi/models/account_move.py#L330)) But "prezzo_totale" is never rounded, it is taken directly from the tax details ### Solution: When converting "prezzo_unitario" avoid the rounding by adding `round=False`. opw-4720375 Forward-Port-Of: odoo/odoo#207084
<b>Steps to reproduce:</b> 1. Website > shop > Open any product > Open Editor(Edit) 2. Customize → Navigate to Customer → Click on Rating. 3. Theme → Navigate to Colors → Navigate to Light & Dark > Choose Dark theme. <b>Issue:</b> Website Shop, when using a dark background, the text in write a message box and comment bubbles in reviews sections becomes white making it invisible. <b>Cause:</b> In light mode, the text appears black, making it easy to read. However, when switching to
Original PR description
<b>Steps to reproduce:</b> 1. Website > shop > Open any product > Open Editor(Edit) 2. Customize → Navigate to Customer → Click on Rating. 3. Theme → Navigate to Colors → Navigate to Light & Dark >…
<b>Steps to reproduce:</b> 1. Website > shop > Open any product > Open Editor(Edit) 2. Customize → Navigate to Customer → Click on Rating. 3. Theme → Navigate to Colors → Navigate to Light & Dark > Choose Dark theme. <b>Issue:</b> Website Shop, when using a dark background, the text in write a message box and comment bubbles in reviews sections becomes white making it invisible. <b>Cause:</b> In light mode, the text appears black, making it easy to read. However, when switching to dark mode, the text changes to white, which makes it difficult to read against the light bubble background. <b>Solution:</b> This commit adds class text-black to the comment and description container to improve the visibility. <b>opw : 4724764</b> <b>BUG:</b>    <b>FIX:</b>    Forward-Port-Of: odoo/odoo#206803
**Steps to reproduce:** Create a new contact/company with more than 25 character **Issue:** The name field is partially shown as compared to version 16. **Cause:** The issue occurs after this change (odoo/odoo@a68cfbb) in version 17. The below CSS for the partner autocomplete field has been removed as the field has 'field_partner_autocomplete' widget. https://github.com/odoo/odoo/blob/05e60f226a0d15bfa3b71eaebe2786f4d687f23e/addons/partner_autocomplete/static/src/scss/partner_autocompl
Original PR description
**Steps to reproduce:** Create a new contact/company with more than 25 character **Issue:** The name field is partially shown as compared to version 16. **Cause:** The issue occurs after this change (odoo/odoo@a68cfbb) in version 17. The below CSS for the partner autocomplete field has been removed as the field has 'field_partner_autocomplete' widget. https://github.com/odoo/odoo/blob/05e60f226a0d15bfa3b71eaebe2786f4d687f23e/addons/partner_autocomplete/static/src/scss/partner_autocomplete.scss#L31-L34 **Solution:** Reintroduce partner autocomplete CSS fix (odoo/odoo@b9788544b7101e5a202cf87989bc3f5fc0495249) [opw-4686705](https://www.odoo.com/odoo/project/49/tasks/4686705) 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#205661
Fix an issue in the xml template where the custom import form reference is set at the wrong place, causing errors when it is in use at the same time as a customer reference. task-4761954 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#208048
Original PR description
Fix an issue in the xml template where the custom import form reference is set at the wrong place, causing errors when it is in use at the same time as a customer reference. task-4761954 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#208048
Apply the HSN schema based on the 'l10n_in_reports.hsn_new_schema_apply_date' system parameter. If the parameter is missing or invalid, default to 2025-05-01 as per government guidelines. Forward-Port-Of: odoo/enterprise#84745
Original PR description
Apply the HSN schema based on the 'l10n_in_reports.hsn_new_schema_apply_date' system parameter. If the parameter is missing or invalid, default to 2025-05-01 as per government guidelines. Forward-Port-Of: odoo/enterprise#84745
Steps to Reproduce: 1. Install industry_fsm_sale module. 2. Create a SO with at least one SOL. 3. Save the record. 4. Delete the line, then click the Catalog button without saving. Issue: - An error occurs indicating a missing record. Cause: - The action_add_from_catalog method is accessing self.task_id, but self still includes the deleted SOL, which no longer exists. As a result, accessing its fields raises an error. Fix: - Move the action_add_from_catalog method to the
Original PR description
Steps to Reproduce: 1. Install industry_fsm_sale module. 2. Create a SO with at least one SOL. 3. Save the record. 4. Delete the line, then click the Catalog button without saving. Issue: - An error occurs indicating a missing record. Cause: - The action_add_from_catalog method is accessing self.task_id, but self still includes the deleted SOL, which no longer exists. As a result, accessing its fields raises an error. Fix: - Move the action_add_from_catalog method to the sale.order model, which is the appropriate place to handle this logic, ensuring the method doesn't depend on potentially stale or deleted lines. opw-4760487 Forward-Port-Of: odoo/enterprise#84414
Steps to reproduce: - Install payroll, payroll Mexican localisation - Switch to the Mexican company - Choose an employee from the Mexican company - Change the contract to be hourly waged instead of monthly - Set a value for the wage/hour - Create some work entries for that employee - Generate a payslip for the employee in the duration you are testing - Edit the work entries you have to have some unpaid leaves - Generate another payslip for the employee Current Behavior: Payslip is g
Original PR description
Steps to reproduce: - Install payroll, payroll Mexican localisation - Switch to the Mexican company - Choose an employee from the Mexican company - Change the contract to be hourly waged instead of…
Steps to reproduce: - Install payroll, payroll Mexican localisation - Switch to the Mexican company - Choose an employee from the Mexican company - Change the contract to be hourly waged instead of monthly - Set a value for the wage/hour - Create some work entries for that employee - Generate a payslip for the employee in the duration you are testing - Edit the work entries you have to have some unpaid leaves - Generate another payslip for the employee Current Behavior: Payslip is generated without taking into consideration the number of hours actually worked and the unpaid leaves taken by the employee. It also generates the payslip with the value of the wage/month regardless of the value of the wage/hour you added. Issue: In df8f53b0cad4738537f18890e628c286dedaa141, Mexican localisation was implemented but with computing the amount of the `payslip_worked_days` using the `contract.wage` which is the fixed amount of wage/month. https://github.com/odoo/enterprise/blob/25caeeab01abc0b47f6bd6b02658c3bbbe0aba96/l10n_mx_hr_payroll_localisation/models/hr_payslip_worked_days.py#L19-L20 opw-4604675 Forward-Port-Of: odoo/enterprise#83135
**Steps to reproduce:** - Install Accounting - Activate "Analytic Accounting" in Accounting settings - Go to "Accounting / Accounting / Journal Entries" - Create an entry with some analytic distribution - Go to "Accounting / Reporting / Audit Reports / Trial Balance" - Activate "Analytic Group By" in the settings of the report - Add the account used in the analytic distribution in "Analytic" group option **Issue:** In the "End Balance" column, all the amounts are summed in the total c
Original PR description
**Steps to reproduce:** - Install Accounting - Activate "Analytic Accounting" in Accounting settings - Go to "Accounting / Accounting / Journal Entries" - Create an entry with some analytic distribution - Go to "Accounting / Reporting / Audit Reports / Trial Balance" - Activate "Analytic Group By" in the settings of the report - Add the account used in the analytic distribution in "Analytic" group option **Issue:** In the "End Balance" column, all the amounts are summed in the total column instead of being grouped by analytic accounts. It results on a total amount being twice what it should be as the total column of each period is also included in the sum. opw-4648009 Forward-Port-Of: odoo/enterprise#84044
Currently it's possible for a timesheet user to set and write the project to False in the timesheet list view. The UI will say the project is missing but the analytic line is changed anyway. This PR add check that the project is set before writing to the analytic line record. opw-4649817 Forward-Port-Of: odoo/enterprise#83420
Original PR description
Currently it's possible for a timesheet user to set and write the project to False in the timesheet list view. The UI will say the project is missing but the analytic line is changed anyway. This PR add check that the project is set before writing to the analytic line record. opw-4649817 Forward-Port-Of: odoo/enterprise#83420
The SpreadsheetName component is designed to grow indefinitely with the length of its text content. However, this means that it'll end up breaking the page layout. This revisions revisits the component structurea and embedding to prevent it from growing larger than the visible viewport of the client. Task: 4760366 Forward-Port-Of: odoo/enterprise#84664 Forward-Port-Of: odoo/enterprise#84410
Original PR description
The SpreadsheetName component is designed to grow indefinitely with the length of its text content. However, this means that it'll end up breaking the page layout. This revisions revisits the component structurea and embedding to prevent it from growing larger than the visible viewport of the client. Task: 4760366 Forward-Port-Of: odoo/enterprise#84664 Forward-Port-Of: odoo/enterprise#84410
Beofre this commit: Products with both positive and negative sales order lines in SO can result it total quantity = 0 when calcuating average cost. Causing division by zero error. After this commit: Added a check to prevent division if total quantity of product is zero. Negative order lines are usually used for return of product, it is not included in shipping request. opw-4655713 Forward-Port-Of: odoo/enterprise#83911 Forward-Port-Of: odoo/enterprise#83500
Original PR description
Beofre this commit: Products with both positive and negative sales order lines in SO can result it total quantity = 0 when calcuating average cost. Causing division by zero error. After this commit: Added a check to prevent division if total quantity of product is zero. Negative order lines are usually used for return of product, it is not included in shipping request. opw-4655713 Forward-Port-Of: odoo/enterprise#83911 Forward-Port-Of: odoo/enterprise#83500
**issue:** When a task with an allocated time > 0.0 but no timesheets is created in a shared project (with edit rights), the portal user incorrectly sees 0.0 as the allocated time. **Steps to reproduce:** - Ensure the sale_timesheet module is installed. - Create a new project. - Create a task with allocated time and no timesheets. - Share the project with a portal user (edit permission). In the portal user's kanban view, the allocated time of the task is displayed as 0.0 instead o
Original PR description
**issue:** When a task with an allocated time > 0.0 but no timesheets is created in a shared project (with edit rights), the portal user incorrectly sees 0.0 as the allocated time. **Steps to reproduce:** - Ensure the sale_timesheet module is installed. - Create a new project. - Create a task with allocated time and no timesheets. - Share the project with a portal user (edit permission). In the portal user's kanban view, the allocated time of the task is displayed as 0.0 instead of the correct allocated time. opw-4582705 Forward-Port-Of: odoo/enterprise#82171
The compute method was removed in this commit, but is declared in the field. Traceback: --- AttributeError: 'product.product' object has no attribute '_compute_pricer_display_price' This commit resolves the above error by skipping the compute method when it is called. commit : https://github.com/odoo/enterprise/commit/70d96c44bb834ecbe89b5720ae18a93038301796#diff-2f3d348951d6293f7e805819d7053ac4ec65994bbacc829dac5dc68b00c932c> sentry-6547636163 Forward-Port-Of: odoo/enterprise#835
Original PR description
The compute method was removed in this commit, but is declared in the field. Traceback: --- AttributeError: 'product.product' object has no attribute '_compute_pricer_display_price' This commit resolves the above error by skipping the compute method when it is called. commit : https://github.com/odoo/enterprise/commit/70d96c44bb834ecbe89b5720ae18a93038301796#diff-2f3d348951d6293f7e805819d7053ac4ec65994bbacc829dac5dc68b00c932c> sentry-6547636163 Forward-Port-Of: odoo/enterprise#83599
Version: - saas-17.4 Steps to reproduce: - Create request signature activity for sign request. - Try to send document for sign from activity. Issue: - It will give a traceback to user. Cause: - It will try to create a record for 'sign.request' model and in reference_doc field it was showing wrong value as we are not allowing to create reference_doc for 'sign.request' model. Solution: - Since reference_doc is not supported for 'sign.request', this fix adds a condition to explici
Original PR description
Version: - saas-17.4 Steps to reproduce: - Create request signature activity for sign request. - Try to send document for sign from activity. Issue: - It will give a traceback to user. Cause: - It will try to create a record for 'sign.request' model and in reference_doc field it was showing wrong value as we are not allowing to create reference_doc for 'sign.request' model. Solution: - Since reference_doc is not supported for 'sign.request', this fix adds a condition to explicitly skip setting it for that model task-4416253 Forward-Port-Of: odoo/enterprise#75611