Saturday, March 15, 2025
4 changes · saas-17.4
Miscellaneous changes
For existing customers, when coretax is installed, the new luxury tax group and its tax will not be loaded into Odoo. During XML generation, it will look for the tax group by XML ID which will not be found and hence resulting to traceback error. To mitigate this issue, we will introduce a post_init_hook to manually create the tax group and not raise exception when env.ref() doesn't find the tax group opw-4635356 --- I confirm I have signed the CLA and read the PR guidelines at www.odo
Original PR description
For existing customers, when coretax is installed, the new luxury tax group and its tax will not be loaded into Odoo. During XML generation, it will look for the tax group by XML ID which will not be found and hence resulting to traceback error. To mitigate this issue, we will introduce a post_init_hook to manually create the tax group and not raise exception when env.ref() doesn't find the tax group opw-4635356 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#201643 Forward-Port-Of: odoo/odoo#201523
There are currently 2 issues with the "Gaps in the sequence" warning on journals in the accounting dashboard. (1) Sequence check per company issue: We query and thus do the the sequence check only on the moves of a single company. This e.g. fails though in the following case (all moves in the same journal) ``` move0: company_A move1: company_B move2: company_A ``` The query for company_A will find a gap between move0 and move2. But there is no gap (it just belongs to a different compa
Original PR description
There are currently 2 issues with the "Gaps in the sequence" warning on journals in the accounting dashboard. (1) Sequence check per company issue: We query and thus do the the sequence check only on…
There are currently 2 issues with the "Gaps in the sequence" warning on journals in the accounting dashboard. (1) Sequence check per company issue: We query and thus do the the sequence check only on the moves of a single company. This e.g. fails though in the following case (all moves in the same journal) ``` move0: company_A move1: company_B move2: company_A ``` The query for company_A will find a gap between move0 and move2. But there is no gap (it just belongs to a different company). (2) Lockdate per company issue: Consider the case that the child company is already locked but the parent is not. E.g ``` move0: parent company move1: child company (move is locked) move2: parent company ``` We would find a gap for the parent company. The "right" lock date to use for a journal is the lock date of the journal company: * A branch company is locked when the parent is locked. * Parent companies of the journal company can not add moves to the journal. So we will find all holes that can still be corrected. After this commit we query per lock date (instead of per company). In each query we check all the journals restricted by the same lock date. This solves both issues: (1) is solved since query all moves independent of the company (2) is not an issue since we use the "right" lock date (see reasoning above) opw-4548453 Forward-Port-Of: odoo/odoo#201732
The test is failing due to an expired certificate, removing the module from tests for now. Forward-Port-Of: odoo/odoo#201971
Original PR description
The test is failing due to an expired certificate, removing the module from tests for now. Forward-Port-Of: odoo/odoo#201971
Forward-Port-Of: odoo/enterprise#81496
Original PR description
Forward-Port-Of: odoo/enterprise#81496