Skip to content

[16.0][MIG] l10n_fr_chorus_en16931: backport from v18 to v16 - #83

Open
arnaudlayec wants to merge 1 commit into
16.0from
16.0-l10n_fr_chorus_en16931
Open

arnaudlayec wants to merge 1 commit into
16.0from
16.0-l10n_fr_chorus_en16931

Conversation

@arnaudlayec

@arnaudlayec arnaudlayec commented Sep 10, 2026

Copy link
Copy Markdown

The only adaptations from v18 code are:

  • module version
  • field invoice_sending_method not existing on res.partner => use instead ("customer_invoice_transmit_method_code", "=", "fr-chorus") in the wizard
  • on account.move: the method chorus_get_invoice has no underscore in v16, and _get_en16931_invoice_bin directly returns the file content, not a tuple (remove the [0])

@arnaudlayec
arnaudlayec marked this pull request as draft September 10, 2026 14:34
@arnaudlayec
arnaudlayec force-pushed the 16.0-l10n_fr_chorus_en16931 branch from d08229d to b5b5523 Compare September 10, 2026 14:40
@ak-git-bot ak-git-bot added series:16.0 mod:l10n_fr_chorus_en16931 Module l10n_fr_chorus_en16931 labels Sep 10, 2026
@arnaudlayec arnaudlayec changed the title [MIG] l10n_fr_chorus_en16931: backport from v18 to v16 [16.0][MIG] l10n_fr_chorus_en16931: backport from v18 to v16 Sep 14, 2026
@arnaudlayec
arnaudlayec marked this pull request as ready for review September 14, 2026 09:08
@arnaudlayec

Copy link
Copy Markdown
Author

Tested on a first v16.0 customer, seems OK

@alexis-via

Copy link
Copy Markdown
Member

You didn't keep commit history.
The last point in your initial message is linked to a change in 18.0 that hasn't been backported to 16.0.
I propose to keep it in this PR and then re-backport the module once the 16.0 will be on-par with 18.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

mod:l10n_fr_chorus_en16931 Module l10n_fr_chorus_en16931 series:16.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants