[19.0][MIG] contract_sale_invoicing: Migration to 19.0#1487
Open
prayagrk wants to merge 31 commits into
Open
Conversation
[REF] Contract Sale Invoicing: update translations [IMP] - Assert that the predecessor is available for new link at uncancel [RMV] - remove usless changes [RMV] - Remove usless field recurring_invoices after the total isolation between contract model and account analytic one. recurring_invoices which was used to mark analytic account as contract became usless [IMP] - P3 syntax [IMP] - use @openupgrade.migrate() and openupgrade.logged_query [IMP] - drop transient table in migration script
Since that commit : https://github.com/OCA/contract/blob/a429b10c20cfd7b40064cbfdfd0313a5b1e27007, account_analytic_id has been moved to group_id.
replaced contract's account_analytic_id by group_id
TT45293 Co-Authored-By: Pedro M. Baeza <pedro.baeza@tecnativa.com>
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: contract-17.0/contract-17.0-contract_sale_invoicing Translate-URL: https://translation.odoo-community.org/projects/contract-17-0/contract-17-0-contract_sale_invoicing/
Currently translated at 100.0% (3 of 3 strings) Translation: contract-17.0/contract-17.0-contract_sale_invoicing Translate-URL: https://translation.odoo-community.org/projects/contract-17-0/contract-17-0-contract_sale_invoicing/it/
Sale Order on 18.0 has no longer the field `analytic_account_id`. Instead, a variable distribution of multiple Analytic Accounts per Sale Order Line is possible. We adapted the module to consider only Sale Order Lines that match with 100%* on the analytic account of the contract.
The flag is not seen when doing recurrency by line, and the position anyway is a bit weird, so let's put it with the generation type selection. This also doesn't make sense for supplier invoices or other kind of generation. TT58137
…e same contract invoice Before this commit, when a sale order was invoiced from a contract, it created a new invoice, resulting in two invoices, one for the contract and another for the sale order. After this commit, when this new field is checked in the contract, the sale order lines are invoiced in the same invoice as the contract.
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: contract-18.0/contract-18.0-contract_sale_invoicing Translate-URL: https://translation.odoo-community.org/projects/contract-18-0/contract-18-0-contract_sale_invoicing/
Currently translated at 100.0% (6 of 6 strings) Translation: contract-18.0/contract-18.0-contract_sale_invoicing Translate-URL: https://translation.odoo-community.org/projects/contract-18-0/contract-18-0-contract_sale_invoicing/it/
Currently translated at 100.0% (6 of 6 strings) Translation: contract-18.0/contract-18.0-contract_sale_invoicing Translate-URL: https://translation.odoo-community.org/projects/contract-18-0/contract-18-0-contract_sale_invoicing/nl/
Currently translated at 100.0% (6 of 6 strings) Translation: contract-18.0/contract-18.0-contract_sale_invoicing Translate-URL: https://translation.odoo-community.org/projects/contract-18-0/contract-18-0-contract_sale_invoicing/fr/
Currently translated at 100.0% (6 of 6 strings) Translation: contract-18.0/contract-18.0-contract_sale_invoicing Translate-URL: https://translation.odoo-community.org/projects/contract-18-0/contract-18-0-contract_sale_invoicing/sl/
OCA-git-bot
added
series:19.0
mod:contract_sale_invoicing
prayagrk
force-pushed
the
19.0-mig-contract_sale_invoicing
branch
from
July 17, 2026 06:35
ccf8c51 to
659c2c5
Compare
prayagrk
force-pushed
the
19.0-mig-contract_sale_invoicing
branch
from
July 17, 2026 06:43
659c2c5 to
2cddf34
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
19 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
contract_sale_invoicing: Migration to 19.0