I'm working on a migration script for that module as I forgot to add one when I migrated the module. Hopefully on Monday I'll push a PR for this issue.

When installing the module base_iso3166 the installation fails if the pycountry version installed is 19.8.18. The documentation states: " It works also with pycountry >= 16.11.8" but for 19.8.18 that statement seems to no longer be true.
After downgrading back to 16.11.8 the installation works fine, also I've tested updating de pycountry after successful installation with 16.11.8 to 19.8.18 again and after that the module does not work, reverting to 16.11.8 again makes it work just fine.

tracebackerror.txt

We have just developt an addon for downloading NACE items in proper languages and associating them to partner via a custom field, instead of category. More details in OCA/partner-contact#106. Main new features are:

• Use custom partner fields (main_nace/many2one and secondary_naces/many2many), don't use res.partner.category. Reasons:
  • NACE texts are so long
  • NACE items have rich descriptions to indicate user when used them.
• Downloads NACE items from RAMON online service, and translates them in all available languages (all languages of European Community countries) through a wizard.
• Filter partners by main NACE activity
• Group partner by main NACE activity

As @clonedagain comments:

The existing NACE module uses partner categories because several community modules worked this way.
If you think it's wrong please just make a proposal to change the existing module.
I for one have no preferences. If others agree with you I'd not block, as long as migration scripts are provided.

We do not have enought resources to improve OCA/community-data-files/l10n_eu_nace addon and we have already partner_nace addon in production in one customer. But, we moved this PR to our public repo, Antiun/antiun-odoo-addons@59b062c, in order to allow anyone to do pending work:

• Merge new features (Antiun/antiun-odoo-addons/partner_nace)
• Provide migration scripts from current version (l10n_eu_nace) to new implementation

References:

• OCA/partner-contact#106
• Antiun/antiun-odoo-addons@59b062c
• #4
• https://github.com/jordillinares/addons/tree/master/l10n_es_cnae_2009
• OCA/l10n-france#3
• #3

There are so many repositories under OCA organisation. Which repos. do I need to install from OCA to have full accounting support in OCB 15.0 or 16.0 ?

regarding "base_bank_from_iban"

Is your feature request related to a problem?

Because the IBAN is sufficient to fetch the corresponding BIC and Country, it would be a great improvement to do this automatically.

Another problem is, that the module did not quite work for me, following the same steps as in the test instruction and the test file. For the exact same data it worked, but as soon as I have changed to German banks and partners it did not work correctly.

Describe the solution you'd like

On a partner's bank account list: when entering an IBAN it should check for available banks, if none is available it should suggest/ask if a new bank should be created with the information available from this API:
https://openiban.com/validate/DE89370400440532013000?getBIC=true

Describe alternatives you've considered

Additional context

When creating SEPA mandates sometimes BIC codes are necessary, but these are not always available in the database and it is time consuming to check for the BIC codes, while this can be automated.

Looking forward to your response, best regards
Michael

Todo

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

Modules to migrate

• account_tax_unece - By @hbrunn - #20
• base_iso3166
• base_unece - By @hbrunn - #20
• l10n_eu_nace
• product_uom_unece - By @hbrunn - #20

Todo

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

Modules to migrate

• account_payment_unece - By @levkar - #48
• account_tax_unece - By @levkar - #49
• base_bank_from_iban - By @pedrobaeza - #41
• base_currency_iso_4217 - By @levkar - #52
• base_iso3166 - By @aitorbouzas - #42
• base_unece - By @levkar - #47
• l10n_eu_nace - By @sbejaoui - #53
• product_fao_fishing - By @ernestotejeda - #75
• product_uom_unece > uom_unece - By @levkar - #47

Todo

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

Modules to migrate

• account_payment_unece
• account_tax_unece
• base_bank_from_iban
• base_bank_from_iban - By @manuelregidor - #123
• base_currency_iso_4217
• base_iso3166 - By @josepmy - #130
• base_unece
• uom_unece

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

Todo

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

Modules to migrate

• account_payment_unece - By @bealdav - #147
• account_tax_unece - By @syera94 - #146
• base_bank_from_iban - By @pegonzalezspesol / @pedrobaeza - #141
• base_currency_iso_4217 - By @BT-anieto - #171
• base_iso3166 - By @ramiadavid - #143
• base_unece - By @syera94 - #142
• company_sanitary_registry - By @CarlosRoca13 - #167
• product_fao_fishing - By @stefan-tecnativa - #162
• uom_unece - By @marielejeune - #140

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

Todo

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

Modules to migrate

• account_payment_unece - By @alexis-via - #194
• account_tax_unece - By @nguyenminhchien - #192
• base_bank_from_iban - By @javierobcn - #180
• base_currency_iso_4217
• base_iso3166 - By @ramiadavid - #179
• base_unece - By @alexis-via - #193
• company_sanitary_registry
• l10n_eu_nace - By @manuelregidor - #200
• product_fao_fishing - By @youelEl - #183
• uom_unece - By @youelEl - #182

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

Todo

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

Modules to migrate

• base_iso3166 - By @etobella - #25
• base_unece - By @alexis-via - #17
• account_payment_unece - By @alexis-via - #17
• account_tax_unece - By @alexis-via - #17
• l10n_eu_nace - By @mayjo79 - #18
• product_uom_unece - By @alexis-via - #17

Some duplicate data in res_currency_data.xml (for example base.EUR)

Some have different names with same id (for example base.TRY) Turkish Lira & New Turkish Lira.

Shouldn't it be based on https://www.iso.org/iso-4217-currency-codes.html ?

Very nice and necessary module indeed! Thanks!

@jbeficent

Todo

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

Modules to migrate

• account_payment_unece - By @astirpe - #36
• account_tax_unece - By @astirpe - #34
• base_iso3166 - By @etobella - #29
• base_unece - By @astirpe - #33
• l10n_eu_nace - By @oihane - #39
• product_uom_unece - By @astirpe - #35

Hello,

I'm working for a French customer running Odoo v13.0 EE on Odoo.sh and migrating to v16.0 CE.

Enterprise edition has a module account_intrastat that can help to declare EMEBI (ex-DEB) monthly to customs services, but it is quite simple.

So, we decided in 2021 to develop extra features on a private module inspired by several OCA modules :

• l10n_fr_intrastat_product
• l10n_be_intrastat_product
• intrastat_product
• etc.

To ease the configuration by logistic and accounting department employees, this module embed every TARIC codes suitable for France (also called NC8) at date with secondary units. This is 9000+ codes.

Now that we want to migrate to CE, we will use the OCA modules listed before, but we wonder if the database for TARIC codes could be useful for the community.
Of course, some codes were added and some removed, so we need to update this database.

The complete up-to-date database is accessible in the TARIC and Quota data and information page.
As described in that page :

Tariff data, nomenclature and reference files are updated every month. The nomenclature is extracted by default in English, French and German and, twice a year, in all official languages (except Maltese and Gaelic, which are not included in the TARIC)

Describe the solution you'd like
We'd like to know if someone is interested in a new l10n_eu_taric module that would bring the TARIC nomenclature (with translations) and keep it up-to-date.
For the moment, we have to migrate codes with translations for EN and FR

Describe alternatives you've considered
Maybe we can also automate the update by fetching data daily...

Additional context
@alexis-via, we are working with Akretion for that customer, and I know that you're well informed on the EMEBI topic, so feel free to comment.

We're not sure if this is the right place for such module, maybe l10n-france is a better one... any suggestions are welcome

When installing base_iso3166 many issues are documented related to pycountry version (see #108 and #108 ). I've recently faced another one with v14 and Python 3.8. Depending on the Odoo/Python active version, is it possible to pin a certain version of this library and prevent this issue, or is it a bad practice, and any error should be fixed upgrading or downgrading pycountry library?

Module

base_iso3166

Describe the bug

When installing the addon, an error is raised. In v14 and Python 3.8.10 case a LookupError one. It's been fixed downgrading pycountry from 20.7.3 to 19.8.18.

To Reproduce

It seems to be a general problem, depending on the development status of pycountry library and the Odoo target version.

Steps to reproduce the behavior (in v14):

1. Use a Python 3.8 environment, e.g. 3.8.10.
2. Install pycountry via pip, without version selection.
3. Install an addon that depends on base_iso3166 (e.g. l10n_es_facturae, for Spanish l10n) => an error is fired.

Expected behavior
Installation without errors

Additional context
If in this issue is defined a clear strategy for v14, I'd make a PR, but I'm not sure which soluction fits better OCA conventions (oca_dependencies.txt, manifest file, setup file,...)

cc @rousseldenis @pedrobaeza

Todo

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

Modules to migrate

• account_payment_unece - By @astirpe - #76
• account_tax_unece - By @astirpe - #74
• base_bank_from_iban - By @emagdalenaC2i - #72
• base_currency_iso_4217
• base_iso3166 - By @ThomasBinsfeld - #81 By @ernestotejeda - #95
• base_unece - By @astirpe - #73
• product_fao_phising - By @sergio-teruel - #85
• uom_unece - By @astirpe - #71

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

Hi folks!

I'd like to contribute to the development of the NACE modules. I didn't know the existence of this project, so I developed a module of my own with spanish CNAE version. This module sets an entity for NACE records (only spanish version), and relates it to leads and partners through many2many_tags widgets on their respective forms. It also writes the NACE codes of a given lead to the partner created when lead is escalated to opportunity.

I thought I'd better somehow refactor and integrate my work into this project. If you agree, let me know how I can help.

Todo

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

Modules to migrate

• account_payment_unece - By @alexis-via - #100 / #107
• account_tax_unece - By @alexis-via / @StefanRijnhart - #103
• base_bank_from_iban - By @ozono - #101
• base_currency_iso_4217 - By @CarlosRoca13 - #102
• base_unece - By @alexis-via - #98
• product_fao_fishing
• product_meat_unece
• uom_unece - By @alexis-via - #97

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

Hi, the Python module 'pycountry' now uses an underscore in some parameters:

>>> import pycountry
>>> len(pycountry.countries)
249
>>> list(pycountry.countries)[0]
Country(alpha_2='AF', alpha_3='AFG', name='Afghanistan', numeric='004', official_name='Islamic Republic of Afghanistan')

So, when a modification in the field 'code' triggers the recompute function '_compute_codes(...)', it fails.

    @api.multi
    @api.depends('code')
    def _compute_codes(self):
        for country in self:
            try:
                c = pycountry.countries.get(alpha_2=country.code)
                country.code_alpha3 = c.alpha_3
                country.code_numeric = c.numeric
            except KeyError:
                try:
                    c = pycountry.historic_countries.get(alpha_2=country.code)
                    country.code_alpha3 = c.alpha_3
                    country.code_numeric = c.numeric
                except KeyError:
                    country.code_alpha3 = False
                    country.code_numeric = False