Thursday, February 6, 2020
7 changes · master
Resolved issues and error corrections
This fix prevents an error when creating an invoice from a sales order line that has no product. Sales teams can now handle incomplete or empty sales orders more smoothly without the process failing unexpectedly.
Original PR description
Description of the issue/feature this PR addresses: Improve the behaviour of the sale subscription dashboard for salesman. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The eBay sales integration now avoids unnecessary warning messages when it is installed but not yet configured. This keeps scheduled background checks from cluttering logs, making monitoring cleaner for teams that are not actively using the integration.
Original PR description
When sale_ebay is installed but not configured, its crons are frequently raising unnecessary warnings, and polluting logs.
A small typo in a filtering rule caused the inter-company sales and purchase screen to crash in the browser. This update corrects the typo so users can open and use the affected configuration without interruption.
Original PR description
The domain operator is 'not in ' (notice the trailing space). With that trailing space, the operator is not recognized as a supported operator and the domain interpretation crashes (JS side). Domain introduced in 7570c39
Miscellaneous changes
### Description of the issue/feature this PR addresses: The refund wizard is not compatible with the LATAM document types. This PR try to extend the original wizard to be able to properly create credit notes and invoices ("modify" option in the wizard). There are multiples fixes so we enumerate the errors bellow, each one has their own commit ### Current behavior before PR: 1. We are not able to set Document type in the Refund wizard. 2. When selecting "modify" option in the Refund
Original PR description
### Description of the issue/feature this PR addresses: The refund wizard is not compatible with the LATAM document types. This PR try to extend the original wizard to be able to properly create…
### Description of the issue/feature this PR addresses:
The refund wizard is not compatible with the LATAM document types. This PR try to extend the original wizard to be able to properly create credit notes and invoices ("modify" option in the wizard).
There are multiples fixes so we enumerate the errors bellow, each one has their own commit
### Current behavior before PR:
1. We are not able to set Document type in the Refund wizard.
2. When selecting "modify" option in the Refund wizard it raise and error "can not create credit note" and do not let us to create neither the credit note. or the new invoice.
3. Credit note is been created in the default journal of the system and not in the same journal of the original invoice.
### Desired behavior after PR is merged:
1. We are able to select Document type in the Refund wizard when creating a credit note.
2. When selecting "modify" option now we can create both the credit note and the new invoice, each one now has the proper document type.
3. Credit note now is created in the same journal of the original invoice.
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#44616
Forward-Port-Of: odoo/odoo#43514Because the tax closing entry is created (empty) at the creation of the CoA, it is not possible anymore to change it later, even if the user didn't create any journal entry. By checking that there are no account.move.line instead of account.move, and also there are no entries with a name different from '/' (to ensure that the sequences are untouched) we can change the CoA if needed. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior aft
Original PR description
Because the tax closing entry is created (empty) at the creation of the CoA, it is not possible anymore to change it later, even if the user didn't create any journal entry. By checking that there are no account.move.line instead of account.move, and also there are no entries with a name different from '/' (to ensure that the sequences are untouched) we can change the CoA if needed. 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#44647
Since commit 92737f2 (finetuning of 7b49f58) field website_id, website_tag_ids are missing from form view of res partner. Now we use a more precise xpath, hardcoding the group name into the xpath to be sure that fields are correctly added below the company_id field from a visible tab. 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.odo
Original PR description
Since commit 92737f2 (finetuning of 7b49f58) field website_id, website_tag_ids are missing from form view of res partner. Now we use a more precise xpath, hardcoding the group name into the xpath to be sure that fields are correctly added below the company_id field from a visible tab. 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#44120
Also make the CoA translatable -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#43768
Original PR description
Also make the CoA translatable -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#43768