Skip to content

V17 fix upgrade blockers - #742

Merged
royle-vietnam merged 2 commits into
17.0from
v17_fix_upgrade_blockers
Sep 30, 2026
Merged

royle-vietnam merged 2 commits into
17.0from
v17_fix_upgrade_blockers

Conversation

@royle-vietnam

Copy link
Copy Markdown
Collaborator

No description provided.

… columns

openupgradelib.delete_record_translations picks every field flagged
translate in ir_model_fields and applies the jsonb operator ? to the
column of that name. Such a column is not always jsonb: it can belong to
a module not loaded yet, or be a column left behind by an older version.
The account_edi 17.0 post-migration died that way on ir_cron.name, a
varchar column from the time the name was stored on ir_cron (the field
is now delegated to ir.actions.server): "operator does not exist:
character varying ? unknown" (tvtma, upgrading from 16.0; 18 scripts
call the helper). Restrict the call to the translated columns that are
jsonb already.

(cherry picked from commit a6f47d8)
…conversion type

In '%(street2)' followed by a line break, the line break becomes the
conversion type and formatting the address raises "unsupported format
character". Odoo shipped that format for Japan in 11.0 (13ee559,
fixed by 087bebf); countries are noupdate data, so databases that
loaded it back then still have it. The end-migration of
account_edi_ubl_cii writes on every partner with a country, which
computes the partner's address, and the 16.0 -> 17.0 upgrade of tvtma
died there on its two Japanese partners.

Add the missing conversion type to such placeholders before anything
reads the formats.
@royle-vietnam
royle-vietnam merged commit 55b235c into 17.0 Sep 30, 2026
7 of 9 checks passed
@royle-vietnam
royle-vietnam deleted the v17_fix_upgrade_blockers branch September 30, 2026 04:56
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