Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[17.0][MIG] account_statement_import_coda #223

Open
wants to merge 14 commits into
base: 17.0
Choose a base branch
from

Conversation

antonioburic
Copy link
Member

No description provided.

marielejeune and others added 12 commits July 7, 2024 16:03
The field doesn't exist anymore on this model, but is inherit from the account.move.line.
The name of the account.move.line is auto generated when posted if empty.
Setting it to the communication of the coda can lead to a validation exception from the sequence.mixin
 since it can extract a year from it (such as a strucured communication, see _constrains_date_sequence)
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: l10n-belgium-16.0/l10n-belgium-16.0-account_statement_import_coda
Translate-URL: https://translation.odoo-community.org/projects/l10n-belgium-16-0/l10n-belgium-16-0-account_statement_import_coda/
@antonioburic antonioburic mentioned this pull request Jul 7, 2024
7 tasks
@antonioburic antonioburic marked this pull request as draft July 7, 2024 14:23
@antonioburic antonioburic force-pushed the 17.0-mig-account_statement_import_coda branch 2 times, most recently from d6922a0 to fe86e4b Compare July 7, 2024 19:25
@antonioburic antonioburic force-pushed the 17.0-mig-account_statement_import_coda branch from fe86e4b to 77e3afb Compare July 7, 2024 19:36
@antonioburic antonioburic marked this pull request as ready for review July 7, 2024 19:39
@sbidoul
Copy link
Member

sbidoul commented Jul 8, 2024

/ocabot migration account_statement_import_coda

@OCA-git-bot OCA-git-bot added this to the 17.0 milestone Jul 8, 2024
Copy link

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Nov 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants