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][OU-ADD] account: migration to 17.0 #4457

Closed

Conversation

duong77476-viindoo
Copy link
Contributor

No description provided.

@pedrobaeza
Copy link
Member

pedrobaeza commented Jun 13, 2024

@duong77476-viindoo
Copy link
Contributor Author

@flachica Hello, i apply your fix here, please notify me if you have something in your mind :v

@flachica
Copy link

@flachica Hello, i apply your fix here, please notify me if you have something in your mind :v

I will close my PR and internally use this branch. Thanks for you amazing work.

@rvalyi
Copy link
Member

rvalyi commented Jul 9, 2024

Hello, I'm creating a new analysis tool called odoo-module-diff, it's explained here: https://github.com/akretion/odoo-module-diff

To review or complete the PR, you might be interested by these key commits of the account module migration to 17.0:
https://github.com/akretion/odoo-module-diff-analysis/tree/main/17.0/account

]

_columns_copies = {
"account_tax": [("description", "invoice_label", "JSONB")],
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When trying the script, I get the following error:

psycopg2.errors.DatatypeMismatch: column "invoice_label" is of type jsonb but expression is of type character varying
LINE 4: ...             UPDATE account_tax SET invoice_label=description

Comment on lines +604 to +605
convert_column_translatable(env.cr, "account_tax", "description", "jsonb")
openupgrade.copy_columns(env.cr, _columns_copies)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ecino Ok maybe do same here

)


def _res_partner_bank_create_column(env):
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove


account / res.partner.bank / has_iban_warning (boolean) : NEW isfunction: function, stored
account / res.partner.bank / has_money_transfer_warning (boolean): NEW isfunction: function, stored
# DONE create column in pre-migration and compute using orm in end-migration
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should be nothing to do

@@ -0,0 +1,13 @@
# Copyright 2024 Viindoo Technology Joint Stock Company (Viindoo)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove whole file

---XML records in module 'account'---
DEL account.payment.term: account.account_payment_term_2months (noupdate)
DEL account.tax.group: account.tax_group_taxes (noupdate)
# DONE: removed in post-migration
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

as written above, I think we should keep them

DEL ir.model.constraint: account.constraint_account_report_line_code_uniq
DEL ir.model.constraint: account.constraint_account_tax_name_company_uniq
DEL ir.model.constraint: account.constraint_account_tax_template_name_company_uniq
DEL ir.model.constraint: account_sequence.constraint_account_move_unique_name
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this one is actually added in account now, so we need to uniquify names.

And the whole _work file needs updating from the current analysis file, it contains confusing bogus entries

@hbrunn
Copy link
Member

hbrunn commented Oct 28, 2024

I'll create a followup-PR next Monday of nobody else has picked this up until then

@duong77476-viindoo
Copy link
Contributor Author

I'll create a followup-PR next Monday of nobody else has picked this up until then

Thank you sir

@hbrunn
Copy link
Member

hbrunn commented Nov 4, 2024

I didn't manage to finish this today, so I just pushed an intermediate version on my fork. Still working on a correct payment term migration, Payment terms and tax groups should be fine already.

@pedrobaeza
Copy link
Member

pedrobaeza commented Nov 7, 2024

@hbrunn is this finished on your side (or on hold)? It's for resuming from here.

@hbrunn
Copy link
Member

hbrunn commented Nov 7, 2024

my comments from #4457 (comment) down need addressing still, so if you've the time, please resume from there

@hbrunn
Copy link
Member

hbrunn commented Nov 8, 2024

PS: I'll continue with this on Monday if I don't hear anything to the contrary

@pedrobaeza
Copy link
Member

I'm today resuming this, so probably it will be done. I'll tell you.

@hbrunn
Copy link
Member

hbrunn commented Nov 11, 2024

I don't find any new commits on https://github.com/Tecnativa/OpenUpgrade/commits/17.0-account - what are you working on so that I can do something else today?

@pedrobaeza
Copy link
Member

I'm still working on this.

@hbrunn
Copy link
Member

hbrunn commented Nov 11, 2024

today?

@pedrobaeza
Copy link
Member

Yes, I will push my result at the end of the morning.

@hbrunn
Copy link
Member

hbrunn commented Nov 11, 2024

great, then I'll pick it up from there and do some more reviews meanwhile

@hbrunn
Copy link
Member

hbrunn commented Nov 11, 2024

?

@pedrobaeza
Copy link
Member

I have opened #4662, but it's still not finished. I'm just stuck at the new invoice_label to fill proper data. I have reviewed/reworked till https://github.com/OCA/OpenUpgrade/pull/4662/files#diff-22f22a0c72f96258826774abe5ffb855f21883cf30e51b7e81fbcaaca048214aR275

@pedrobaeza pedrobaeza closed this Nov 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants