Thursday, November 26, 2020
42 changes · master
Enhancements to existing features
This update simplifies how purchase returns are handled by relying on existing return information already linked to purchase order lines. It reduces unnecessary code while keeping the return process behavior the same for users.
Original PR description
Description of the issue/feature this PR addresses: During a return the `purchase_order_line` field is propagate, `order_line.move_ids` include returned move, that why use `returned_move_ids` is not mandatory. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
Fixes an issue where the Point of Sale settings page could show an error after users discarded edits. This makes configuration changes smoother and avoids unnecessary interruptions for users managing POS setup.
Original PR description
Prior to 28762b79e3398dc883af9e0caef7c86cc5c051e0, `_enableButtons` method is mainly called after saving changes in the record, now, it is also called when discarding such that its argument can become `undefined`. This causes error in pos.config form because it uses a custom form which hooked to the said method in order to reload the window when a module_ or group_ field is modified. This commit prevents this error by having a fallback empty array when `changedFields` is `undefined`. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
What are the steps to reproduce your issue ? 1. Install 'Manufacture' and enable 'Work Order' in settings 2. Create product 'ProductA', enable 'Manufacture' in 'Inventory' tab 3. Create a BOM for 'ProductA' 4. For that BOM, create a new operation called 'OperationA' with PDF worksheet but don't attach any PDF 4. Go to 'Manufacture' and create a MO with 'ProductA', the 'OperationA' is automatically set in 'Work Orders' 5. Start the work order What is currently h
Original PR description
What are the steps to reproduce your issue ? 1. Install 'Manufacture' and enable 'Work Order' in settings 2. Create product 'ProductA', enable 'Manufacture' in 'Inventory' tab 3. Create a BOM for…
What are the steps to reproduce your issue ?
1. Install 'Manufacture' and enable 'Work Order' in settings
2. Create product 'ProductA', enable 'Manufacture' in 'Inventory' tab
3. Create a BOM for 'ProductA'
4. For that BOM, create a new operation called 'OperationA' with PDF worksheet but don't attach any PDF
4. Go to 'Manufacture' and create a MO with 'ProductA', the 'OperationA' is automatically set in 'Work Orders'
5. Start the work order
What is currently happening ?
When you try to pause, an error is raised.
'TypeError: Cannot read property 'pdfViewer' of undefined'
What are you expecting to happen ?
Start and pause the work order even without attached PDF.
Why is this happening ?
'this.pdfViewer = existing.data('PDFViewerApplication').pdfViewer'
When there is no pdf attached. The data 'PDFViewerApplication' does not exist.
How to fix the bug ?
Change worksheet default value to text, and make the field mandatory in case of a PDF type
opw-2387428
Fix in enterprise: https://github.com/odoo/enterprise/pull/14973
Forward-Port-Of: odoo/odoo#62319On a mobile, when editing a transfer operation, it is not possible to create a new lot/serial number. To reproduce the error: (Need a single company configuration) 1. Inventory > Configuration > Settings 2. Enable "Lots & Serial Numbers" 3. Inventory > Products > Products 4. Create a new one - Set "Tracking" to "By Lots" 5. Operations > Transfers 6. Create a new one - Add the product and set a demand 7. Save & Mark as todo 8. Enable the mobile mode of your browser & Refresh
Original PR description
On a mobile, when editing a transfer operation, it is not possible to create a new lot/serial number.
To reproduce the error:
(Need a single company configuration)
1. Inventory > Configuration > Settings
2. Enable "Lots & Serial Numbers"
3. Inventory > Products > Products
4. Create a new one
- Set "Tracking" to "By Lots"
5. Operations > Transfers
6. Create a new one
- Add the product and set a demand
7. Save & Mark as todo
8. Enable the mobile mode of your browser & Refresh the page
9. Edit the transfer
10. On the product line previously added, click on details (to set the quantitiy done)
11. Click on "Add"
12. Click on "Lot/Serial Number" field
13. Create
14. Save
=> Validation Error (field Company is missing)
OPW-2389965
Forward-Port-Of: odoo/odoo#62177The suspense account created doesn't have the type corresponding to the domain: https://github.com/odoo/odoo/blob/658d0fa32f35f4c4f9a1828b11fa383d3dad3b46/addons/account/models/account_journal.py#L97 opw-2387857 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#62336
Original PR description
The suspense account created doesn't have the type corresponding to the domain: https://github.com/odoo/odoo/blob/658d0fa32f35f4c4f9a1828b11fa383d3dad3b46/addons/account/models/account_journal.py#L97 opw-2387857 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#62336
Since commit https://github.com/odoo/odoo/commit/3ad4abe171e8e7e86ed0e7b7f000e734d8a2ad92 the default invoicing policy of a product is set to 'delivery'. This is not ok for the delivery products: a delivery product is never delivered. This is confusing to end users, because they do not realize that a delivery line is not included in an invoice. This is especially true if the delivery is free. This commit sets the default policy to 'order' for master data and for newly created products
Original PR description
Since commit https://github.com/odoo/odoo/commit/3ad4abe171e8e7e86ed0e7b7f000e734d8a2ad92 the default invoicing policy of a product is set to 'delivery'. This is not ok for the delivery products: a delivery product is never delivered. This is confusing to end users, because they do not realize that a delivery line is not included in an invoice. This is especially true if the delivery is free. This commit sets the default policy to 'order' for master data and for newly created products from the shipping form view. opw-2387437 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#62345
Steps to reproduce the bug: - Let's consider a product P with purchase UOM = Unit - Let's consider a UOM called Box such as 1 Box = Units - P is invoiced according to its ordered quantity - Create a PO for 1 Box of P and confirm it - Create the bill B from PO Bug: The quantity of B was 10 and its UOM was Box PS: When creating a bill from a PO, by default the quantities on the lines of B are always expected in the UOM of their respective PO line Introduced by: d0455ae opw:2
Original PR description
Steps to reproduce the bug: - Let's consider a product P with purchase UOM = Unit - Let's consider a UOM called Box such as 1 Box = Units - P is invoiced according to its ordered quantity - Create a PO for 1 Box of P and confirm it - Create the bill B from PO Bug: The quantity of B was 10 and its UOM was Box PS: When creating a bill from a PO, by default the quantities on the lines of B are always expected in the UOM of their respective PO line Introduced by: d0455ae opw:2391243 Forward-Port-Of: odoo/odoo#62311
Description of the issue/feature this PR addresses: For this case, if the invoice currency is different from the invoice company currency, the tax calculation is considered the value in a different currency, and the subtotal is the sum of the amount untaxed + the taxes (wrongly in company currency) result in an incorrect value. This is verified when printing the invoice report Current behavior before PR: Desired behavior after PR is merged: The final result of the subtotal must be in
Original PR description
Description of the issue/feature this PR addresses: For this case, if the invoice currency is different from the invoice company currency, the tax calculation is considered the value in a different currency, and the subtotal is the sum of the amount untaxed + the taxes (wrongly in company currency) result in an incorrect value. This is verified when printing the invoice report Current behavior before PR: Desired behavior after PR is merged: The final result of the subtotal must be in the currency of the invoice, assuming that the tax calculation is expressed in the currency of the invoice. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#61401
On the accounting dashboard, for bank and cash journals, we are displaying the number of items to check. Since commit https://github.com/odoo/enterprise/commit/b2dd65b9a9c054570d5796a81f2c390c4d8cb6c4, when getting bank statement data, we are filtering the ones that are not reconciled. We should also include is_reconciled = False when getting dashboard data. Description of the issue/feature this PR addresses: opw-2378876 Current behavior before PR: Desired behavior after PR is merg
Original PR description
On the accounting dashboard, for bank and cash journals, we are displaying the number of items to check. Since commit https://github.com/odoo/enterprise/commit/b2dd65b9a9c054570d5796a81f2c390c4d8cb6c4, when getting bank statement data, we are filtering the ones that are not reconciled. We should also include is_reconciled = False when getting dashboard data. Description of the issue/feature this PR addresses: opw-2378876 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#62150
CLA signing Forward-Port-Of: odoo/odoo#59052
Original PR description
CLA signing Forward-Port-Of: odoo/odoo#59052
Forward-Port-Of: odoo/odoo#62061
Original PR description
Forward-Port-Of: odoo/odoo#62061
The 'On Hand' button triggers action_open_quants on product model. It do not explode the kit into its component 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#62354
Original PR description
The 'On Hand' button triggers action_open_quants on product model. It do not explode the kit into its component 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#62354
Description of the issue/feature this PR addresses: There was missing some document types in l10n_ar data Documentation: [AFIP tables](https://www.afip.gob.ar/libro-iva-digital/documentos/Libro-IVA-Digital-Tablas-del-Sistema.pdf) -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#61878
Original PR description
Description of the issue/feature this PR addresses: There was missing some document types in l10n_ar data Documentation: [AFIP tables](https://www.afip.gob.ar/libro-iva-digital/documentos/Libro-IVA-Digital-Tablas-del-Sistema.pdf) -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#61878
Followup on 911ada2d02b24778435fd9174441a6834da2effa When modifying the company_id of a pricelist, the check to ensure a website has a pricelist available wasn't triggered. This commits ensures the Each website has Valid Pricelist with Correct or Empty company. Fixes #50707 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/
Original PR description
Followup on 911ada2d02b24778435fd9174441a6834da2effa When modifying the company_id of a pricelist, the check to ensure a website has a pricelist available wasn't triggered. This commits ensures the Each website has Valid Pricelist with Correct or Empty company. Fixes #50707 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#50785
Description of the issue/feature this PR addresses: task-2365792 Current behavior before PR: Before this commit the close button cross/multiply character was wrongly translated in some languages (e.g. Spanish) Desired behavior after PR is merged: After this commit the close button cross/multiply character is not a translatable text anymore -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#60268
Original PR description
Description of the issue/feature this PR addresses: task-2365792 Current behavior before PR: Before this commit the close button cross/multiply character was wrongly translated in some languages (e.g. Spanish) Desired behavior after PR is merged: After this commit the close button cross/multiply character is not a translatable text anymore -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#60268
Fields `views`, `closed_reason_id`, `closed_uid` and `closed_date` should not be copied while copying post. 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#60661
Original PR description
Fields `views`, `closed_reason_id`, `closed_uid` and `closed_date` should not be copied while copying post. 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#60661
Before this commit the dropzone was relative to div.content. This would create some bad position where the dropzone was covering the form view but not the chatter. task-2389929 Forward-Port-Of: odoo/odoo#62199
Original PR description
Before this commit the dropzone was relative to div.content. This would create some bad position where the dropzone was covering the form view but not the chatter. task-2389929 Forward-Port-Of: odoo/odoo#62199
When some bills are not paid, some with due date, some without, when registering the payment of these bills as a group payment with checks, it is not possible to print the check To reproduce the error: (Need account) 1. Go to Invoicing > Vendors > Bills 2. Create a new one - Add at least one line - Add the Payment Terms 3. Save & Post 4. Duplicate it, then Save & Post 5. Go back to Bills 6. Select the two bills 7. Click on Action > Register Payment 8. Select Checks, enable
Original PR description
When some bills are not paid, some with due date, some without, when registering the payment of these bills as a group payment with checks, it is not possible to print the check
To reproduce the error:
(Need account)
1. Go to Invoicing > Vendors > Bills
2. Create a new one
- Add at least one line
- Add the Payment Terms
3. Save & Post
4. Duplicate it, then Save & Post
5. Go back to Bills
6. Select the two bills
7. Click on Action > Register Payment
8. Select Checks, enable Group Payment
9. Click on Create Payment
10. Click on Print Check
11. Click on Print
=> An Odoo Error is raised
The user should be able to print it.
OPW-2389368
(Manual Forward-Port-Of #62168)
Forward-Port-Of: odoo/odoo#62365STEPS: * Create a BoM with two components purchased the same vendor, but with different "Delivery Lead Time". First component must have lower value * Create Manufactoring order, Mark as ToDo * Open created purchase order BEFORE: Order Date is equal "MO planned day MINUS delivery lead time for the first project" AFTER: Order Date is equal "MO planned day MINUS maximum amout delivery lead time for the products" --- opw-2388031 Description of the issue/feature this PR addresses:
Original PR description
STEPS: * Create a BoM with two components purchased the same vendor, but with different "Delivery Lead Time". First component must have lower value * Create Manufactoring order, Mark as ToDo * Open created purchase order BEFORE: Order Date is equal "MO planned day MINUS delivery lead time for the first project" AFTER: Order Date is equal "MO planned day MINUS maximum amout delivery lead time for the products" --- opw-2388031 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#62382
Leftover from commit b5e39fc (#61771) -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#62379
Original PR description
Leftover from commit b5e39fc (#61771) -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#62379
task-2387820 Forward-Port-Of: odoo/odoo#62166
Original PR description
task-2387820 Forward-Port-Of: odoo/odoo#62166
What are the steps to reproduce your issue ? 1. Install "google_calendar" 2. Log in with "admin" 3. Create an eventX with "admin" and "demo" has attendees 4. Run "Google Calendar Synchronization" from "Scheduled Actions" What is currently happening ? eventX is successfully added to Google but without admin if you sync Odoo to Google one more time, Google will overwrite eventX and it will remove admin from attendees What are you expecting to happen ?
Original PR description
What are the steps to reproduce your issue ? 1. Install "google_calendar" 2. Log in with "admin" 3. Create an eventX with "admin" and "demo" has attendees 4. Run "Google Calendar Synchronization"…
What are the steps to reproduce your issue ?
1. Install "google_calendar"
2. Log in with "admin"
3. Create an eventX with "admin" and "demo" has attendees
4. Run "Google Calendar Synchronization" from "Scheduled Actions"
What is currently happening ?
eventX is successfully added to Google but without admin
if you sync Odoo to Google one more time, Google will overwrite eventX
and it will remove admin from attendees
What are you expecting to happen ?
Sync Odoo to Google and Google to Odoo without lost attendees
Why is this happening ?
Because there is a filter that prevent addition of current user to the attendees
How to fix the bug ?
Remove the filter
This reverts commit 287ee0f83ae6fd457e5356860c8a8ab5a4e66754.
opw-2382443
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#62406Before this commit if a product template has no image, no image was displayed in the website shop for the product After this commit if a product template has no image, the image of the first variant is displayed in the website shop https://github.com/odoo/odoo/issues/52463 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/subm
Original PR description
Before this commit if a product template has no image, no image was displayed in the website shop for the product After this commit if a product template has no image, the image of the first variant is displayed in the website shop https://github.com/odoo/odoo/issues/52463 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#61322
Please add me has member of camptocamp organization. Forward-Port-Of: odoo/odoo#62410 Forward-Port-Of: odoo/odoo#61575
Original PR description
Please add me has member of camptocamp organization. Forward-Port-Of: odoo/odoo#62410 Forward-Port-Of: odoo/odoo#61575
Description of the issue/feature this PR addresses: Fiscal position can be deleted while already assigned on invoice Current behaviour before PR: Fiscal position will be deleted Desired behaviour after PR is merged: Should provide a warning message if current fiscal position already assigned in invoice Fixes #61942 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#62398 Forward-Port-Of: odoo/odoo#62167
Original PR description
Description of the issue/feature this PR addresses: Fiscal position can be deleted while already assigned on invoice Current behaviour before PR: Fiscal position will be deleted Desired behaviour after PR is merged: Should provide a warning message if current fiscal position already assigned in invoice Fixes #61942 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#62398 Forward-Port-Of: odoo/odoo#62167
This makes the act of replacing the dummy text easier. @Tecnativa -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#62413 Forward-Port-Of: odoo/odoo#55433
Original PR description
This makes the act of replacing the dummy text easier. @Tecnativa -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#62413 Forward-Port-Of: odoo/odoo#55433
Include mindicador.cl connection, to update the following currencies: USD and EUR. Also the connection can update to financial indexes: UF (stands for "Unidad de Fomento") and UTM (stands for "Unidad Tributaria Mensual"). These two currencies (USD and EUR) are the most common currencies used in Chile for international transactions and the rates supplied by the site "mindicador.cl". The UF is an index that is forecasted in a daily basis using the IPC (consumer prices index) and is an in
Original PR description
Include mindicador.cl connection, to update the following currencies: USD and EUR. Also the connection can update to financial indexes: UF (stands for "Unidad de Fomento") and UTM (stands for "Unidad Tributaria Mensual"). These two currencies (USD and EUR) are the most common currencies used in Chile for international transactions and the rates supplied by the site "mindicador.cl". The UF is an index that is forecasted in a daily basis using the IPC (consumer prices index) and is an intensively used value in different business transactions, to keep the amounts independent from inflation. The UTM is an index used for taxes or fines adjustments or money returns used by the government. Even when this value is published on a monthly basis. Forward-Port-Of: odoo/enterprise#14552 Forward-Port-Of: odoo/enterprise#13023
Behavior prior to this commit: - if "SEPA Direct Debit" is the only payment acquirer activated, it will be pre-selected as payment method. But when paying an invoice online, the signature box is not initially shown when the payment popup shows up. Instead the user has to click on the payment option again, to get the form to reload. - this does not happen when paying on the ecommerce site (because the payment form is not shown in a modal there) Behavior after this commit: - when
Original PR description
Behavior prior to this commit: - if "SEPA Direct Debit" is the only payment acquirer activated, it will be pre-selected as payment method. But when paying an invoice online, the signature box is not initially shown when the payment popup shows up. Instead the user has to click on the payment option again, to get the form to reload. - this does not happen when paying on the ecommerce site (because the payment form is not shown in a modal there) Behavior after this commit: - when the modal is shown, if the signature control appears to have not been initialized yet, it will be re-initialized (recalculating its size in the process) Note: - we use `resetSignature`, rather than `resizeSignature`, because the latter does not properly reset the control (the gray signature line for example) in case there is a "large" resize (in this instance, resizing from 0) opw-2389869 Forward-Port-Of: odoo/enterprise#14898
Generally this is not mandatory See: https://emploi.belgique.be/fr/themes/remuneration/intervention-de-lemployeur-dans-les-frais-de-deplacement-domicile-lieu-de But this is the case for the CP200 See: https://www.sfonds200.be/fonds-social/infos-sectorielles/frais-de-transport/prive-2020 Forward-Port-Of: odoo/enterprise#14858
Original PR description
Generally this is not mandatory See: https://emploi.belgique.be/fr/themes/remuneration/intervention-de-lemployeur-dans-les-frais-de-deplacement-domicile-lieu-de But this is the case for the CP200 See: https://www.sfonds200.be/fonds-social/infos-sectorielles/frais-de-transport/prive-2020 Forward-Port-Of: odoo/enterprise#14858
Purpose ======= From the documents application: - Employees can access their own payslips - Document managers can access their own payslips - Payroll users can access all the payslips Forward-Port-Of: odoo/enterprise#15004
Original PR description
Purpose ======= From the documents application: - Employees can access their own payslips - Document managers can access their own payslips - Payroll users can access all the payslips Forward-Port-Of: odoo/enterprise#15004
…pensation Purpose ======= If a public time off happens less than 30 days after the end of the contract, the employee could get paid for it according to the number of worked days. But, this makes no sense if the contract is followed by another one. Example: After an appraisal. Forward-Port-Of: odoo/enterprise#14891
Original PR description
…pensation Purpose ======= If a public time off happens less than 30 days after the end of the contract, the employee could get paid for it according to the number of worked days. But, this makes no sense if the contract is followed by another one. Example: After an appraisal. Forward-Port-Of: odoo/enterprise#14891
Currently, In Helpdesk create a ticket as the description of the ticket is empty, it is displayed 'false' on the forum post. So in this commit, the forum post should also be empty instead of having 'false' displayed. Links PR #13791 TaskID: 2345334 Forward-Port-Of: odoo/enterprise#14131 Forward-Port-Of: odoo/enterprise#13791
Original PR description
Currently, In Helpdesk create a ticket as the description of the ticket is empty, it is displayed 'false' on the forum post. So in this commit, the forum post should also be empty instead of having 'false' displayed. Links PR #13791 TaskID: 2345334 Forward-Port-Of: odoo/enterprise#14131 Forward-Port-Of: odoo/enterprise#13791
Since commit https://github.com/odoo/enterprise/commit/07c245d234a7f903a62ac73604a693d0685e950c, we are using a payment template containing some information common to all SEPA pain versions, see _generate_payment_template. This introduced a small change regarding field InstrId, which contains payment['name'] value. As stated in legal documents, the definition of this field is the following : Unique identification as assigned by an instructing party for an instructed party to unambiguously i
Original PR description
Since commit https://github.com/odoo/enterprise/commit/07c245d234a7f903a62ac73604a693d0685e950c, we are using a payment template containing some information common to all SEPA pain versions, see _generate_payment_template. This introduced a small change regarding field InstrId, which contains payment['name'] value. As stated in legal documents, the definition of this field is the following : Unique identification as assigned by an instructing party for an instructed party to unambiguously identify the instruction. We must therefore ensure we are using an unique value inside that field, which can be achieved by adding the ID of the payment at the beginning. opw-2381047 Forward-Port-Of: odoo/enterprise#15000 Forward-Port-Of: odoo/enterprise#14987
Forward-Port-Of: odoo/enterprise#14052
Original PR description
Forward-Port-Of: odoo/enterprise#14052
If you have push notifications enabled, a button on the event allows to manually send the configured push reminders for the event tracks. Before this commit, the action would simply trigger the same method as the social CRON job, which would send ALL ready social.posts, whether they are related to the event or not. Now, pressing the button will only send push notifications that are the ready reminders for the tracks of this specific event. We also took the opportunity to move the bu
Original PR description
If you have push notifications enabled, a button on the event allows to manually send the configured push reminders for the event tracks. Before this commit, the action would simply trigger the same method as the social CRON job, which would send ALL ready social.posts, whether they are related to the event or not. Now, pressing the button will only send push notifications that are the ready reminders for the tracks of this specific event. We also took the opportunity to move the button and python action from website_event_social to website_event_track_social where it belongs. As this is a fix for stable, the method in website_event_social was left empty to avoid breaking potential overrides. It will be removed in master. Task 2360932 Forward-Port-Of: odoo/enterprise#14984
- In test_mode, mocking the signing of an invoice is incorrect in one case - The computation of partner_bank_vat is incorrect when the country is not Mexico Forward-Port-Of: odoo/enterprise#14964
Original PR description
- In test_mode, mocking the signing of an invoice is incorrect in one case - The computation of partner_bank_vat is incorrect when the country is not Mexico Forward-Port-Of: odoo/enterprise#14964
Task ID: 2311363 Forward-Port-Of: odoo/enterprise#14859
Original PR description
Task ID: 2311363 Forward-Port-Of: odoo/enterprise#14859
What are the steps to reproduce your issue ? 1. Install "project_forecast" 2. Create a projectX with taskA 3. Create new plan with taskA on projectX and "publish & send" 4. Archive taskA and projectX What is currently happening ? cannot manage Users > ValidationError: Your task is not in the selected project What are you expecting to happen ? Manage users without ValidationError Why is this happening ? Because the task is archived, so i
Original PR description
What are the steps to reproduce your issue ?
1. Install "project_forecast"
2. Create a projectX with taskA
3. Create new plan with taskA on projectX and "publish & send"
4. Archive taskA and projectX
What is currently happening ?
cannot manage Users
> ValidationError: Your task is not in the selected project
What are you expecting to happen ?
Manage users without ValidationError
Why is this happening ?
Because the task is archived, so it will not belong to "project_id.tasks" in the constrain
How to fix the bug ?
Ignore archived records
opw-2390943
Forward-Port-Of: odoo/enterprise#14980'l10n_mx_edi_cfdi_name' no longer exists in account.move. Forward-Port-Of: odoo/enterprise#14963
Original PR description
'l10n_mx_edi_cfdi_name' no longer exists in account.move. Forward-Port-Of: odoo/enterprise#14963
Since commit https://github.com/odoo/odoo/commit/3ad4abe171e8e7e86ed0e7b7f000e734d8a2ad92 the default invoicing policy of a product is set to 'delivery'. This is not ok for the delivery products: a delivery product is never delivered. This is confusing to end users, because they do not realize that a delivery line is not included in an invoice. This is especially true if the delivery is free. This commit sets the default policy to 'order' for master data. opw-2387437 Forward-Port-O
Original PR description
Since commit https://github.com/odoo/odoo/commit/3ad4abe171e8e7e86ed0e7b7f000e734d8a2ad92 the default invoicing policy of a product is set to 'delivery'. This is not ok for the delivery products: a delivery product is never delivered. This is confusing to end users, because they do not realize that a delivery line is not included in an invoice. This is especially true if the delivery is free. This commit sets the default policy to 'order' for master data. opw-2387437 Forward-Port-Of: odoo/enterprise#14988
When adding a variant product to an invoice, the generated XML file does not contain the product code. To reproduce the error: (Need account_accountant,l10n_co_edi_ubl_2_1,contacts) 1. Set the company's country to Colombia 2. Accounting > Customers > Customers 3. Create a new one. Fill in the Fiscal information, for instance: - Tipo de Representación: R-01-PN - Tipo Establecimiento: E-01 - Obligaciones y Responsabilidades: O-02 - Usuario Aduanero: A-05 4. Accounting > Customers
Original PR description
When adding a variant product to an invoice, the generated XML file does not contain the product code. To reproduce the error: (Need account_accountant,l10n_co_edi_ubl_2_1,contacts) 1. Set the company's country to Colombia 2. Accounting > Customers > Customers 3. Create a new one. Fill in the Fiscal information, for instance: - Tipo de Representación: R-01-PN - Tipo Establecimiento: E-01 - Obligaciones y Responsabilidades: O-02 - Usuario Aduanero: A-05 4. Accounting > Customers > Invoices 5. Create a new one - Set the previously created client - Add a variant product (it must have an internal reference) 6. Save & Post => In the log notes, a XML file is generated. It does not contain the product's internal reference (search for ITE_18). This is an error. OPW-2382170 Forward-Port-Of: odoo/enterprise#14955 Forward-Port-Of: odoo/enterprise#14927
What are the steps to reproduce your issue ? 1. Install 'Manufacture' and enable 'Work Order' in settings 2. Create product 'ProductA', enable 'Manufacture' in 'Inventory' tab 3. Create a BOM for 'ProductA' 4. For that BOM, create a new operation called 'OperationA' with PDF worksheet but don't attach any PDF 4. Go to 'Manufacture' and create a MO with 'ProductA', the 'OperationA' is automatically set in 'Work Orders' 5. Start the work order What is currently h
Original PR description
What are the steps to reproduce your issue ? 1. Install 'Manufacture' and enable 'Work Order' in settings 2. Create product 'ProductA', enable 'Manufacture' in 'Inventory' tab 3. Create a BOM for…
What are the steps to reproduce your issue ?
1. Install 'Manufacture' and enable 'Work Order' in settings
2. Create product 'ProductA', enable 'Manufacture' in 'Inventory' tab
3. Create a BOM for 'ProductA'
4. For that BOM, create a new operation called 'OperationA' with PDF worksheet but don't attach any PDF
4. Go to 'Manufacture' and create a MO with 'ProductA', the 'OperationA' is automatically set in 'Work Orders'
5. Start the work order
What is currently happening ?
When you try to pause, an error is raised.
'TypeError: Cannot read property 'pdfViewer' of undefined'
What are you expecting to happen ?
Start and pause the work order even without attached PDF.
Why is this happening ?
'this.pdfViewer = existing.data('PDFViewerApplication').pdfViewer'
When there is no pdf attached. The data 'PDFViewerApplication' does not exist.
How to fix the bug ?
Check the existence of 'PDFViewerApplication' before trying to get 'pdfViewer' attribute.
opw-2387428
Fix in community: https://github.com/odoo/odoo/pull/62319
Forward-Port-Of: odoo/enterprise#14973