Saturday, July 27, 2024
25 changes · saas-17.2
Enhancements to existing features
This update improves Odoo's internal Hoot testing framework, making automated tests clearer, more reliable, and easier for developers to diagnose. It does not change customer-facing business workflows, but helps reduce risk by improving the quality signals used during development and validation.
Original PR description
## Pull Request HOOT (PRHOOT) - part 21 Part 1: https://github.com/odoo/odoo/pull/152930 Part 2: https://github.com/odoo/odoo/pull/153018 Part 3: https://github.com/odoo/odoo/pull/153023 Part 4:…
## Pull Request HOOT (PRHOOT) - part 21 Part 1: https://github.com/odoo/odoo/pull/152930 Part 2: https://github.com/odoo/odoo/pull/153018 Part 3: https://github.com/odoo/odoo/pull/153023 Part 4: https://github.com/odoo/odoo/pull/153203 Part 5: https://github.com/odoo/odoo/pull/153425 Part 6: https://github.com/odoo/odoo/pull/153700 Part 7: https://github.com/odoo/odoo/pull/154054 Part 8: https://github.com/odoo/odoo/pull/154579 Part 9: https://github.com/odoo/odoo/pull/155073 Part 10: https://github.com/odoo/odoo/pull/155639 Part 11: https://github.com/odoo/odoo/pull/156255 / https://github.com/odoo/enterprise/pull/58135 Part 12: https://github.com/odoo/odoo/pull/156869 Part 13: https://github.com/odoo/odoo/pull/158384 / https://github.com/odoo/enterprise/pull/59019 Part 14: https://github.com/odoo/odoo/pull/158916 Part 15: https://github.com/odoo/odoo/pull/160292 / https://github.com/odoo/enterprise/pull/59971 Part 15.5: https://github.com/odoo/odoo/pull/166463 Part 16: https://github.com/odoo/odoo/pull/166311 Part 17: https://github.com/odoo/odoo/pull/168328 Part 18: https://github.com/odoo/odoo/pull/171004 / https://github.com/odoo/enterprise/pull/65657 Part 19: https://github.com/odoo/odoo/pull/171242 / https://github.com/odoo/enterprise/pull/65767 Part 20: https://github.com/odoo/odoo/pull/173332 / https://github.com/odoo/enterprise/pull/66895 Enterprise: https://github.com/odoo/enterprise/pull/67296 This pull requests brings various improvements and fixes to Hoot and the Odoo unit test ecosystem. See the different commit messages for more details. Note: these changes are made in stable to avoid having to support multiple versions of the HOOT API. As such, these changes are intended to be strictly limited to unit tests as to not put the rest of the code base at risk. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
This fix prevents an error in Point of Sale when staff create a new contact and no identification types are configured. It helps keep checkout and customer setup workflows running smoothly in affected localizations.
Original PR description
Before this commit, attempting to create a new contact without any identification type available in the database would result in an error. This commit ensures that a new contact can be created even when no identification types are present. Community PR: https://github.com/odoo/odoo/pull/174493 opw-4068907
Miscellaneous changes
…payments Steps to reproduce: - Install l10n_mx_edi - Switch to a Mexican company (e.g. ESCUALA KEMPER URGATE) - Create an invoice: * Customer: [a Mexican customer] (e.g. INMOBILIARIA CVA) * Invoice Date: [yesterday] * Invoice Lines: - Product: [any product with UNSPSC Category set] - Price: [any] - Quantity: 2 - Taxes: [any] - Confirm the invoice - Generate CFDI via "Send & Print" button - Create a partial credit note: * Reversal date: [yesterday] * Quantity: 1
Original PR description
…payments Steps to reproduce: - Install l10n_mx_edi - Switch to a Mexican company (e.g. ESCUALA KEMPER URGATE) - Create an invoice: * Customer: [a Mexican customer] (e.g. INMOBILIARIA CVA) * Invoice…
…payments
Steps to reproduce:
- Install l10n_mx_edi
- Switch to a Mexican company (e.g. ESCUALA KEMPER URGATE)
- Create an invoice:
* Customer: [a Mexican customer] (e.g. INMOBILIARIA CVA)
* Invoice Date: [yesterday]
* Invoice Lines:
- Product: [any product with UNSPSC Category set]
- Price: [any] - Quantity: 2 - Taxes: [any]
- Confirm the invoice
- Generate CFDI via "Send & Print" button
- Create a partial credit note:
* Reversal date: [yesterday]
* Quantity: 1
- Confirm the credit note
- Register Payment:
* Amount: [the remaining amount]
* Payment Way: Efectivo
* Payment Date: [Today]
- Update Payments
- Go to the payment
- Force CFDI
Issue:
In the generated XML file, "ImpSaldoInsoluto" attribute (corresponding to the residual amount) is not 0.00
Cause:
Credit notes are not taken into account during the computation of the payments values.
opw-3857949
Forward-Port-Of: odoo/enterprise#67496
Forward-Port-Of: odoo/enterprise#67437This update corrects issues in Odoo's automated test checks for the Gantt area and related test tooling. It helps ensure test results are clearer and more dependable, reducing the risk of development mistakes reaching users.
Original PR description
## Pull Request HOOT (PRHOOT) - part 21 Part 1: https://github.com/odoo/odoo/pull/152930 Part 2: https://github.com/odoo/odoo/pull/153018 Part 3: https://github.com/odoo/odoo/pull/153023 Part 4:…
## Pull Request HOOT (PRHOOT) - part 21 Part 1: https://github.com/odoo/odoo/pull/152930 Part 2: https://github.com/odoo/odoo/pull/153018 Part 3: https://github.com/odoo/odoo/pull/153023 Part 4: https://github.com/odoo/odoo/pull/153203 Part 5: https://github.com/odoo/odoo/pull/153425 Part 6: https://github.com/odoo/odoo/pull/153700 Part 7: https://github.com/odoo/odoo/pull/154054 Part 8: https://github.com/odoo/odoo/pull/154579 Part 9: https://github.com/odoo/odoo/pull/155073 Part 10: https://github.com/odoo/odoo/pull/155639 Part 11: https://github.com/odoo/odoo/pull/156255 / https://github.com/odoo/enterprise/pull/58135 Part 12: https://github.com/odoo/odoo/pull/156869 Part 13: https://github.com/odoo/odoo/pull/158384 / https://github.com/odoo/enterprise/pull/59019 Part 14: https://github.com/odoo/odoo/pull/158916 Part 15: https://github.com/odoo/odoo/pull/160292 / https://github.com/odoo/enterprise/pull/59971 Part 15.5: https://github.com/odoo/odoo/pull/166463 Part 16: https://github.com/odoo/odoo/pull/166311 Part 17: https://github.com/odoo/odoo/pull/168328 Part 18: https://github.com/odoo/odoo/pull/171004 / https://github.com/odoo/enterprise/pull/65657 Part 19: https://github.com/odoo/odoo/pull/171242 / https://github.com/odoo/enterprise/pull/65767 Part 20: https://github.com/odoo/odoo/pull/173332 / https://github.com/odoo/enterprise/pull/66895 Community: https://github.com/odoo/odoo/pull/174337 This pull requests brings various improvements and fixes to Hoot and the Odoo unit test ecosystem. See the different commit messages for more details. Note: these changes are made in stable to avoid having to support multiple versions of the HOOT API. As such, these changes are intended to be strictly limited to unit tests as to not put the rest of the code base at risk. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Point of Sale users in Argentina and Peru can now create new contacts even when no identification types are configured. This prevents an error that previously blocked contact creation and helps keep checkout or customer setup workflows moving smoothly.
Original PR description
Before this commit, attempting to create a new contact without any identification type available in the database would result in an error. This commit ensures that a new contact can be created even when no identification types are present. Enterprise PR: https://github.com/odoo/enterprise/pull/67328 opw-4068907 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
- Create 4 invoices: A, B, C, D with a correct MX setup - Make sure C will fail by removing the SAT code on the product for example - Run the send and print wizard on all invoices and check 'Download' (to force a synchronous run). After each call to the web-service, the code does: ``` # Check for success. if invoice.l10n_mx_edi_cfdi_state == 'sent': continue ``` However, the `cr.commit` is at the end of the loop. So the transacti
Original PR description
- Create 4 invoices: A, B, C, D with a correct MX setup - Make sure C will fail by removing the SAT code on the product for example - Run the send and print wizard on all invoices and check…
- Create 4 invoices: A, B, C, D with a correct MX setup
- Make sure C will fail by removing the SAT code on the product for example
- Run the send and print wizard on all invoices and check 'Download' (to force a synchronous run).
After each call to the web-service, the code does:
```
# Check for success.
if invoice.l10n_mx_edi_cfdi_state == 'sent':
continue
```
However, the `cr.commit` is at the end of the loop. So the transaction is not committed except in case of error!
When running the send and print synchronously, the error is raised to the user that will rollback the whole
transaction.
In case of the setup above, A, B and C are well commit but D is sent and has been rollback.
Then, the user will sign again D making the invoice signed twice.
To solve the issue, let's commit right after each web-service call.
That way, whatever the way we use to call the web-services, the transaction is commit immediately.
opw-4003043
opw-3985376
opw-4059666
opw-3955553
...and many others!
Forward-Port-Of: odoo/enterprise#67466
Forward-Port-Of: odoo/enterprise#67365Step to reproduce: - install `l10n_uk_reports` - create 2 user or more - for each user, fill their hmrc token values - select a user different from the current environment user - remove their credential with the button "Remove Authentication Credentials" Current behavior: - The selected user's credential is not removed, but the environment user one got removed Expected behavior: - the selected user's credential should be the one that is removed, and the environment user should
Original PR description
Step to reproduce: - install `l10n_uk_reports` - create 2 user or more - for each user, fill their hmrc token values - select a user different from the current environment user - remove their credential with the button "Remove Authentication Credentials" Current behavior: - The selected user's credential is not removed, but the environment user one got removed Expected behavior: - the selected user's credential should be the one that is removed, and the environment user should not be removed. Why it happens: - In `_clean_tokens` function, it clears the credential of the environment user by default. Solution: - Add way to clear the selected user's credential instead of the environment user's opw-4041604 todo in master: make the user argument required instead of default Forward-Port-Of: odoo/enterprise#66870
Currently, if a user uses a sale order sequence that contains special characters like `/` (e.g. SO/2024/12/31/01), they do not see such a sale order in suggestions in bank reconciliation if the label doesn't match the name of the sale order exactly. That is, a label `SO/2024/12/31/01 test` would not much this sale order, but a label `SO2024123101 test` would much a sale order with a name `SO2024123101`. This is because we format tokens and filter out special characters and then compare them t
Original PR description
Currently, if a user uses a sale order sequence that contains special characters like `/` (e.g. SO/2024/12/31/01), they do not see such a sale order in suggestions in bank reconciliation if the label doesn't match the name of the sale order exactly. That is, a label `SO/2024/12/31/01 test` would not much this sale order, but a label `SO2024123101 test` would much a sale order with a name `SO2024123101`. This is because we format tokens and filter out special characters and then compare them to names. With this commit, we'll compare names and tokens that are formatted the same way. opw-3964898 Forward-Port-Of: odoo/enterprise#67176
Current behaviour: --- Connected as Marc Demo, cannot set the Unique Field of any marketing campaign Steps to reproduce: --- 1. Go to Settings > Users > Marc Demo 2. At Marketing Automation, set User 3. Connect as Marc Demo 4. Go to Marketing Automation 5. Open any campaign 6. Try to set the Unique Field 7. Access Error Cause of the issue: --- unique_field_id is comodel of ir.model.fields Fix: --- Give group_marketing_automation_user the right to read ir.model.fields op
Original PR description
Current behaviour: --- Connected as Marc Demo, cannot set the Unique Field of any marketing campaign Steps to reproduce: --- 1. Go to Settings > Users > Marc Demo 2. At Marketing Automation, set User 3. Connect as Marc Demo 4. Go to Marketing Automation 5. Open any campaign 6. Try to set the Unique Field 7. Access Error Cause of the issue: --- unique_field_id is comodel of ir.model.fields Fix: --- Give group_marketing_automation_user the right to read ir.model.fields opw-4001919 Forward-Port-Of: odoo/enterprise#66690
Since odoo/odoo@c853c3b rpc requests doesn't block anymore the UI, so in commit odoo/enterprise@70c7a747a19 the manual rpc bus notifications were removed, thus preventing the loading indicator to show up. As we're not blocking the UI anymore, this commit simply change the "silent" rpc call to normal rpc calls so that the loading indicator shows up again. Forward-Port-Of: odoo/enterprise#67367
Original PR description
Since odoo/odoo@c853c3b rpc requests doesn't block anymore the UI, so in commit odoo/enterprise@70c7a747a19 the manual rpc bus notifications were removed, thus preventing the loading indicator to show up. As we're not blocking the UI anymore, this commit simply change the "silent" rpc call to normal rpc calls so that the loading indicator shows up again. Forward-Port-Of: odoo/enterprise#67367
eBay recently changed the URL they send in the viewitemURL. We found 3 different ways they send it, but there might be more. We shouldn't have relied on this URL to match products in the beginning, but we can't refactor this flow in stable, instead, we try a different way to match the url, and fallback on another eBay call to get the expected variant. opw-3934127 Forward-Port-Of: odoo/enterprise#66924
Original PR description
eBay recently changed the URL they send in the viewitemURL. We found 3 different ways they send it, but there might be more. We shouldn't have relied on this URL to match products in the beginning, but we can't refactor this flow in stable, instead, we try a different way to match the url, and fallback on another eBay call to get the expected variant. opw-3934127 Forward-Port-Of: odoo/enterprise#66924
Before, in a multi company and mutli website setup, booking an appointment used the companies on the organizer for the context. This was leading to issue for appointment type in Website 2 tied to Company 2. Indeed the mails for the booking were sent with the context of Company 1 (value based on the allowed_company_ids of the user). Now, when website_appointment is installed, if a website is linked to the actual request we use the company tied to it. This ensure that we always use the corre
Original PR description
Before, in a multi company and mutli website setup, booking an appointment used the companies on the organizer for the context. This was leading to issue for appointment type in Website 2 tied to Company 2. Indeed the mails for the booking were sent with the context of Company 1 (value based on the allowed_company_ids of the user). Now, when website_appointment is installed, if a website is linked to the actual request we use the company tied to it. This ensure that we always use the correct company of the website for the creation of the event. We target 17.0 to avoid a behavior change in older stable as the multi website was officially supported for appointment type in that version. Could be backported if really necessary. task-3977787 Forward-Port-Of: odoo/enterprise#64144
Description of the issue/feature this PR addresses: 1 - Create a quality.point and add a repair operation type in the 'picking_type_ids' field 2 - Create a repair picking Current behavior before PR: No QC is created. This is expected because of https://github.com/odoo/enterprise/pull/59509 - only available since 17.3 Desired behavior after PR is merged: Exclude “repair” operation types from the domain of the “picking_type_ids” field to avoid confusing the user. opw-4052819 Forw
Original PR description
Description of the issue/feature this PR addresses: 1 - Create a quality.point and add a repair operation type in the 'picking_type_ids' field 2 - Create a repair picking Current behavior before PR: No QC is created. This is expected because of https://github.com/odoo/enterprise/pull/59509 - only available since 17.3 Desired behavior after PR is merged: Exclude “repair” operation types from the domain of the “picking_type_ids” field to avoid confusing the user. opw-4052819 Forward-Port-Of: odoo/enterprise#67257
### Steps to reproduce: - Install hr_holidays_contract_gantt module - Create two employees one with a contract and another without - Create a time off for each employee - Check Time Off -> Overview ### Current behavior before PR: The employee who has a contract will have grey cells on weekend days that are coming after his contract start date but the ones before will be white. The employee who has no contract won't have any grey cells neither for his off days nor the weekend days.
Original PR description
### Steps to reproduce: - Install hr_holidays_contract_gantt module - Create two employees one with a contract and another without - Create a time off for each employee - Check Time Off -> Overview ### Current behavior before PR: The employee who has a contract will have grey cells on weekend days that are coming after his contract start date but the ones before will be white. The employee who has no contract won't have any grey cells neither for his off days nor the weekend days. ### Desired behavior after PR is merged: Both employees should show the grey cells in the gantt view whether they have contract or not because if so we fallback on the employee working hours and then company's working hours 'According to the PO' opw-3961873 Forward-Port-Of: odoo/enterprise#65470
Adding another report for SYSCEBNL. We need to provide a way to add an availability for children of a COA, so the reports is only available for Associations (and not for Companies). Forward-Port-Of: odoo/enterprise#62883
Original PR description
Adding another report for SYSCEBNL. We need to provide a way to add an availability for children of a COA, so the reports is only available for Associations (and not for Companies). Forward-Port-Of: odoo/enterprise#62883
accounts and group from syscebnl taxes adapted for these accounts for each country --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#166211
Original PR description
accounts and group from syscebnl taxes adapted for these accounts for each country --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#166211
*loyalty, pos_loyalty, sale_loyalty Currently, archived products that are used in loyalty programs may cause the POS shop to crash. Steps to reproduce: ------------------- * Go to the **Point of Sale** App * Go to the products * Look for the product `Simple Pen` * Archive the product * Add some product to the order * Add a customer that has loyalty points (`Azure Interior`) > Observations: Blank screen. Error in the console: Cannot read properties of undefined (reading 'id') at P
Original PR description
*loyalty, pos_loyalty, sale_loyalty Currently, archived products that are used in loyalty programs may cause the POS shop to crash. Steps to reproduce: ------------------- * Go to the **Point of…
*loyalty, pos_loyalty, sale_loyalty
Currently, archived products that are used in loyalty programs may cause the POS shop to crash.
Steps to reproduce:
-------------------
* Go to the **Point of Sale** App
* Go to the products
* Look for the product `Simple Pen`
* Archive the product
* Add some product to the order
* Add a customer that has loyalty points (`Azure Interior`)
> Observations: Blank screen. Error in the console: Cannot read properties of undefined (reading 'id') at Proxy._computeUnclaimedFreeProductQty
> Doing an equivalent flow in sales, when you select `Promotions`, an error message appears saying: Invalid Operation. Invalid product to claim.
Why the fix:
------------
When loading the `loyalty.rewards` to the pos session we check if there is at least one active product. If there is none, we don't load the reward.
Explanation of the domain:
* We only filter in the case where the `reward_type` is `product`.
* Second condition:
* We cannot have a condition like `('reward_product_id', '!=', False)`
We could have a setting with both `reward_product_id` and `reward_product_ids` being set. In this condition it would skip the check on `reward_product_ids`
* We connot have a condition like `('reward_product_ids', '!=', False)` as `reward_product_ids` is always at least an empty set, thus it will always be '`True`'
* We put the condition on `reward_product_tag_id`. When there is one set the computation of `reward_product_ids` is triggered. `reward_product_ids` will always include `reward_product_id`. When there is no tag set, we will always, at least, have a `reward_product_id`.
opw-[3968140](https://www.odoo.com/web#id=3968140&view_type=form&model=project.task)
Forward-Port-Of: odoo/odoo#174319
Forward-Port-Of: odoo/odoo#168442**Current behavior before PR:** Long texts overflowed beyond the banner's boundaries. **Desired behavior after PR is merged:** Ensure that text remains within the banner's limits to improve readability and visual consistency. task-4037185 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#174381 Forward-Port-Of: odoo/odoo#172071
Original PR description
**Current behavior before PR:** Long texts overflowed beyond the banner's boundaries. **Desired behavior after PR is merged:** Ensure that text remains within the banner's limits to improve readability and visual consistency. task-4037185 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#174381 Forward-Port-Of: odoo/odoo#172071
Was always failing because of an invalid signature Forward-Port-Of: odoo/odoo#174217
Original PR description
Was always failing because of an invalid signature Forward-Port-Of: odoo/odoo#174217
…x tags wizard After updating taxes, we didn't update already existing journal entries tags to map correctly into new reports. We let the user change his data which can be very time consuming. To tackle that we introduce a new wizard accessible in accounting settings in which user can set a date from which we will update tags on his journal entries for him. task-3330327 Forward-Port-Of: odoo/odoo#174339 Forward-Port-Of: odoo/odoo#127077
Original PR description
…x tags wizard After updating taxes, we didn't update already existing journal entries tags to map correctly into new reports. We let the user change his data which can be very time consuming. To tackle that we introduce a new wizard accessible in accounting settings in which user can set a date from which we will update tags on his journal entries for him. task-3330327 Forward-Port-Of: odoo/odoo#174339 Forward-Port-Of: odoo/odoo#127077
If a quotation template is set on an order, and that template has a "Confirmation mail", it'll be used to send quotes on confirmation, regardless of the flow (backend/frontend). For frontend flows (portal/ecommerce), a confirmation mail is sent after the order confirmation: * after SO signature on portal (if no payment is required) * on payment post processing (payment on portal or ecommerce) * on free order confirmation (ecommerce) Issue: If a template (with confirmation mail)
Original PR description
If a quotation template is set on an order, and that template has a "Confirmation mail", it'll be used to send quotes on confirmation, regardless of the flow (backend/frontend). For frontend flows…
If a quotation template is set on an order, and that template has a "Confirmation mail", it'll be used to send quotes on confirmation, regardless of the flow (backend/frontend). For frontend flows (portal/ecommerce), a confirmation mail is sent after the order confirmation: * after SO signature on portal (if no payment is required) * on payment post processing (payment on portal or ecommerce) * on free order confirmation (ecommerce) Issue: If a template (with confirmation mail) is used in on the quote in one of those flows, two mails would be sent on confirmation: * the template confirmation mail * the default confirmation mail (could be the same mail) Solution: Harmonize and factorize a bit the behavior, to only send 1 mail maximum. In backend, only send a confirmation mail if there is one configured on the quotation template (as before). In frontend, always send one unique mail, either the default one, or the quotation template one if one is set. opw-3997315 Forward-Port-Of: odoo/odoo#171059
Description of the issue/feature this PR addresses: - Updated the condition of groups for shipping_field as suggested in the previous PR https://github.com/odoo/odoo/pull/173162#discussion_r1686292899 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr opw - [4044861](https://www.odoo.com/odoo/project.task/4044861?cids=2) Forward-Port-Of: odoo/odoo#174072 Forward-Port-Of: odoo/odoo#174031
Original PR description
Description of the issue/feature this PR addresses: - Updated the condition of groups for shipping_field as suggested in the previous PR https://github.com/odoo/odoo/pull/173162#discussion_r1686292899 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr opw - [4044861](https://www.odoo.com/odoo/project.task/4044861?cids=2) Forward-Port-Of: odoo/odoo#174072 Forward-Port-Of: odoo/odoo#174031
Update the OWL lib. Release notes: https://github.com/odoo/owl/releases/tag/v2.3.0 These releases contain small improvements v2.3.0 -- * [IMP] compiler: add support for the .translate suffix 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#174621
Original PR description
Update the OWL lib. Release notes: https://github.com/odoo/owl/releases/tag/v2.3.0 These releases contain small improvements v2.3.0 -- * [IMP] compiler: add support for the .translate suffix 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#174621
Description of the issue/feature this PR addresses: Real information was used as a demo data partner, which caused complaints from the company which was the owner of this information Current behavior before PR: Data of the affected company available for demo databases Desired behavior after PR is merged: Data replaced for a fake demo company Task: [4071645](https://www.odoo.com/odoo/project/1625/tasks/4071645?cids=3) --- I confirm I have signed the CLA and read the PR guidelines a
Original PR description
Description of the issue/feature this PR addresses: Real information was used as a demo data partner, which caused complaints from the company which was the owner of this information Current behavior before PR: Data of the affected company available for demo databases Desired behavior after PR is merged: Data replaced for a fake demo company Task: [4071645](https://www.odoo.com/odoo/project/1625/tasks/4071645?cids=3) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#174603 Forward-Port-Of: odoo/odoo#174301
…s needed --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#174716 Forward-Port-Of: odoo/odoo#174566
Original PR description
…s needed --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#174716 Forward-Port-Of: odoo/odoo#174566