Skip to content

[20.0][OU-ADD] l10n_in: migration scripts - #129

Draft
dnplkndll wants to merge 1 commit into
20.0from
20.0-mig-l10n_in
Draft

dnplkndll wants to merge 1 commit into
20.0from
20.0-mig-l10n_in

Conversation

@dnplkndll

Copy link
Copy Markdown

post-migration.py

19.0 split TDS by direction; 20.0 has a single key.

account.tax.l10n_in_tax_type offered tds_sale and tds_purchase in 19.0 and
offers tds in 20.0. A selection is enforced in Python rather than by the
database, so the rows keep the old key silently: they read as blank in the
interface and match neither branch of a domain over the field. 258 of the
seed's taxes.

Nothing is lost by folding them together. Which direction a tax applies to
is what type_tax_use records, and it is untouched here.


CI: red until #118 lands

The test job fails on duplicate key value violates unique constraint "res_country_state_name_code_uniq" (Ladakh / Odisha). Not this branch:
base's pre-migration, which renames those two external ids, lives in #118 and
is not on 20.0 yet, so every branch cut from 20.0 alone hits it. Per the
fork's model the per-PR check is the lean one; the real migration gate is the
integration branch (#120), where all of this runs green over the full
585-module seed.

AI-assisted (Claude Code); every change reviewed, tested, and owned by the author.

### post-migration.py

19.0 split TDS by direction; 20.0 has a single key.

account.tax.l10n_in_tax_type offered tds_sale and tds_purchase in 19.0 and
offers tds in 20.0. A selection is enforced in Python rather than by the
database, so the rows keep the old key silently: they read as blank in the
interface and match neither branch of a domain over the field. 258 of the
seed's taxes.

Nothing is lost by folding them together. Which direction a tax applies to
is what type_tax_use records, and it is untouched here.

Assisted-by: Claude Opus 5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant