OCA / bank-payment

Odoo Electronic Payment

Home Page:https://odoo-community.org/psc-teams/banking-10

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Migration to version 15.0

OCA-git-bot opened this issue · comments

Todo

https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-15.0

Modules to migrate

Missing module? Check https://github.com/OCA/maintainer-tools/wiki/%5BFAQ%5D-Missing-modules-in-migration-issue-list

account_payment_mode #870

account_payment_partner #873

account_payment_order #876

account_payment_purchase #877

account_payment_purchase_stock #878

account_payment_sale #880

I'm currently working on porting account_banking_pain_base to v15. I wanted to update the CodeList because I received information from a bank that they needed the category purpose RPRE which is not in the current list. So I was in the process of updating the code list for "purpose" and "category_purpose". But, in the latest version of the codeset (cf https://www.iso20022.org/catalogue-messages/additional-content-messages/external-code-sets), the purpose field (code set = "ExternalPurpose1Code") has 323 entries ! The list provided in the fields.Selection for the field "purpose" was already quite big (95 entries)... but now it's 323 entries. I think a fields.Selection is not appropriate for 323 entries ; you can't do a name_search in it, etc. So I'm planning to convert the fields "purpose" and "category_purpose" to a m2o field (and write some mig scripts). If you disagree with this change, please SAY SO NOW (this change is not fun and takes quite some time, so if many of you are against it I prefer not to do the work at all).

I see it correct. Another possible improvement in the payment order is to have a store=False field to set them, and propagate to the existing lines. Remember to put the active mechanism for disabling them.

It was not fun, but I did it: #885
I'll migrate account_banking_sepa_credit_transfer and account_banking_sepa_direct_debit tomorrow or in the coming days (some changes will be needed in those modules too to use the new code lists).

account_payment_purchase #928
based on #877

account_invoice_select_for_payment #1090

There hasn't been any activity on this issue in the past 6 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 issue to never become stale, please ask a PSC member to apply the "no stale" label.