Daily updates from Odoo
Friday, April 8, 2022
8 changes · master
Miscellaneous changes
If applied, this commit will fix the following bug by fixing the corresponding email template. Steps to reproduce: 1- install planning 2- try to send a planning to any employee 3- the email is not sent due to lack of recipients Bug: the template is referring wrongly to the work_email field Fix: refer to it correctly OPW-2797695 Forward-Port-Of: odoo/enterprise#25665
Original PR description
If applied, this commit will fix the following bug by fixing the corresponding email template. Steps to reproduce: 1- install planning 2- try to send a planning to any employee 3- the email is not sent due to lack of recipients Bug: the template is referring wrongly to the work_email field Fix: refer to it correctly OPW-2797695 Forward-Port-Of: odoo/enterprise#25665
** Manual FW ** -- adhoc 49505 / latam 753 --- When the user gets the AFIP error code 10154 it indicates that the user is trying to validate a CN/DN in AFIP but the value in the "FCE: Is cancellation" field is wrongly set. Depending on the conditions of the original document (has been or not been rejected by the receptor) we tell the user to set True/False the "FCE: Is cancellation". The problem is the recommendation message was switched. The proper message is: Origin Doc has been
Original PR description
** Manual FW ** -- adhoc 49505 / latam 753 --- When the user gets the AFIP error code 10154 it indicates that the user is trying to validate a CN/DN in AFIP but the value in the "FCE: Is cancellation" field is wrongly set. Depending on the conditions of the original document (has been or not been rejected by the receptor) we tell the user to set True/False the "FCE: Is cancellation". The problem is the recommendation message was switched. The proper message is: Origin Doc has been rejected then the NC should be marked as FCE Is Cancellation Origin Doc has NOT been rejected then the NC should NOT be marked as FCE Is Cancellation Forward-Port-Of: https://github.com/odoo/enterprise/pull/25004 Forward-Port-Of: odoo/enterprise#26036 Forward-Port-Of: odoo/enterprise#25760
If applied, this commit will fix the following bug by using the tax to group operations concerning the same partner, and account Steps to reproduce: 1- install accounting, l10n_de 2- create a vendor bill with 1 item with tax and another without tax 3- Accounting > reporting > general ledger > DATEV (ZIP) 4- in the account_entries csv both lines are added together in one line Bug: the grouping key is tax agnostic Fix: add tax_id to the grouping key OPW-2801576 Forward-P
Original PR description
If applied, this commit will fix the following bug by using the tax to group operations concerning the same partner, and account Steps to reproduce: 1- install accounting, l10n_de 2- create a vendor bill with 1 item with tax and another without tax 3- Accounting > reporting > general ledger > DATEV (ZIP) 4- in the account_entries csv both lines are added together in one line Bug: the grouping key is tax agnostic Fix: add tax_id to the grouping key OPW-2801576 Forward-Port-Of: odoo/enterprise#25857
Bug introduced by this commit: https://github.com/odoo/enterprise/commit/237daa874935b82db985f1b8e948244033a90a40 1:/ It seems we can have data[special_field] and data[qties] that are False values, leading to a TypeError when using the zip function 2:/ Suppose that, somehow, some users manage to validate a MO with 0 producing qty and 0 component. So it may result in rows with None value leading to a TypeError when casting float(qty) and float(value) Solution: Add defensive checks to
Original PR description
Bug introduced by this commit: https://github.com/odoo/enterprise/commit/237daa874935b82db985f1b8e948244033a90a40 1:/ It seems we can have data[special_field] and data[qties] that are False values, leading to a TypeError when using the zip function 2:/ Suppose that, somehow, some users manage to validate a MO with 0 producing qty and 0 component. So it may result in rows with None value leading to a TypeError when casting float(qty) and float(value) Solution: Add defensive checks to avoid similar errors opw-2813292 opw-2812122 opw-2813812 opw-2813303 opw-2813292 Forward-Port-Of: odoo/enterprise#25995
Forward-Port-Of: odoo/enterprise#25932
Original PR description
Forward-Port-Of: odoo/enterprise#25932
The balance sheet for the Swiss localization does not take into account the profits and losses of the previous years Steps to reproduce: 1. Install Accounting app and l10n_ch module 2. Switch to the Swiss company 3. Open Accounting and create a customer invoice with a product and an invoice date in the previous year 4. Save and confirm the invoice 5. Go to Accounting > Reporting > Switzerland > Balance Sheet 6. The 'Liabilities and equity' lines don't contain the customer invoice S
Original PR description
The balance sheet for the Swiss localization does not take into account the profits and losses of the previous years Steps to reproduce: 1. Install Accounting app and l10n_ch module 2. Switch to the Swiss company 3. Open Accounting and create a customer invoice with a product and an invoice date in the previous year 4. Save and confirm the invoice 5. Go to Accounting > Reporting > Switzerland > Balance Sheet 6. The 'Liabilities and equity' lines don't contain the customer invoice Solution: Create a new `CH_R_BS` report line which computes the profits and losses from the beginning Problem: The report line `CH_R` (which is used in `CH_299` of the balance sheet) doesn't compute the profits and losses from the beginning opw-2789072 opw-2780634 opw-2631963 Forward-Port-Of: odoo/enterprise#25923 Forward-Port-Of: odoo/enterprise#25150
If applied, this commit will fix the following bug by fethcing the correct number of followers from linkedin api. Steps to reproduce: 1- install social marketing 2- add a linkedin page 3- number of followers on dashboard is actually wrong Bug: the ```uniqueImpressionsCount``` is used instead of number of followers Fix: introduced a function to fetch correct number of followers from the correct api endpoint OPW-2502634 Forward-Port-Of: odoo/enterprise#25601
Original PR description
If applied, this commit will fix the following bug by fethcing the correct number of followers from linkedin api. Steps to reproduce: 1- install social marketing 2- add a linkedin page 3- number of followers on dashboard is actually wrong Bug: the ```uniqueImpressionsCount``` is used instead of number of followers Fix: introduced a function to fetch correct number of followers from the correct api endpoint OPW-2502634 Forward-Port-Of: odoo/enterprise#25601
Previously we only had Taxcloud and we chose not to maintain Avalara because of the pricing. However, the pricing difference is not as big anymore. Most users prefer Avatax to TaxCloud. It also allows an easier management of discounts. Co-authored-by: Joren Van Onder <jov@odoo.com> https://www.odoo.com/web?debug#id=2431648&cids=3&menu_id=4720&action=4043&model=project.task&view_type=form Forward-Port-Of: odoo/enterprise#26012 Forward-Port-Of: odoo/enterprise#23535
Original PR description
Previously we only had Taxcloud and we chose not to maintain Avalara because of the pricing. However, the pricing difference is not as big anymore. Most users prefer Avatax to TaxCloud. It also allows an easier management of discounts. Co-authored-by: Joren Van Onder <jov@odoo.com> https://www.odoo.com/web?debug#id=2431648&cids=3&menu_id=4720&action=4043&model=project.task&view_type=form Forward-Port-Of: odoo/enterprise#26012 Forward-Port-Of: odoo/enterprise#23535