Administrators archivos de la lista de correo

Upgrade report: 14.0

Fields renamed

• Models google.service: the field id has been renamed to id_. The following server actions may need update.

  • Failed to install demo data for some modules, demo disabled
  • Correct inconsistencies for reservation
• Models account.move: the field type has been renamed to move_type. The following server actions may need update.

  • Config: Run Remaining Action Todo
  • Failed to install demo data for some modules, demo disabled
  • Correct inconsistencies for reservation
  • Generate Pricelist
  • Generate Pricelist
• Models account.invoice.report: the field type has been renamed to move_type. The following server actions may need update.

  • Config: Run Remaining Action Todo
  • Failed to install demo data for some modules, demo disabled
  • Correct inconsistencies for reservation
  • Generate Pricelist
  • Generate Pricelist
• Models account.invoice.report: the field type has been renamed to move_type. The following server actions may need update.

  • Config: Run Remaining Action Todo
  • Failed to install demo data for some modules, demo disabled
  • Correct inconsistencies for reservation
  • Generate Pricelist
  • Generate Pricelist
• Models account.move: the field type has been renamed to move_type. The following server actions may need update.

  • Config: Run Remaining Action Todo
  • Failed to install demo data for some modules, demo disabled
  • Correct inconsistencies for reservation
  • Generate Pricelist
  • Generate Pricelist
• Models account.bank.statement.line: the field name has been renamed to payment_ref. The following server actions may need update.

  • Correct inconsistencies for reservation
  • Generate Pricelist
  • Generate Pricelist
• Models quality.point: the field product_id has been renamed to product_ids. The following server actions may need update.

  • Correct inconsistencies for reservation

Accounting

• IMPORTANT NOTICE

  The numbering of journal entries & invoices changed in Odoo 14; sequences are replaced by a more robust approach, to prevent mistakes (e.g. 2020/12/0003 for an invoice posted in *September*, or 2020/00003 for a document in fiscal year 2019).

  If you had wrong journal entries, you might face blocking messages like this when validating a document. To fix such issues, you can either correct the number of the last journal entry for the month / year, or assign a number manually on a draft document before posting it. To do so, use the "Renumbering" action available from the *list* of journal entries. Once you fix the latest entry, all future entries will be correct.

• IMPORTANT NOTICE

  Payments have been heavily refactored in Odoo 14.0. To make sure the upgrade of your payments is done correctly, you should ensure a few things.

  Before upgrading:

  • Check that the lock dates for all companies are correctly set; the more recent the lock date, the better.
  • Check if the default accounts on the bank/cash journal is of type liquidity (bank/cash):
    • In case they are, new outstanding payment accounts will be created during the migration.
    • In case they are current asset accounts, no new account will be created.
  • Make sure all accounting entries have a consistant number regarding the fiscal year they belong to. (e.g. a journal entry dated of 2019 shouldn’t have a name xx/2020/xx/xxxx)

  After upgrading:

  • Check the outstanding payment accounts are correctly created. You will have to change the code/name to fit your own chart of accounts.
  • Check that pre-recorded payments (recorded before migration, using the "register payment" button on invoices) in the not-locked periods can correctly be reconciled (after migration) with an incoming statement.

  We highly encourage you to watch this video explaining the differences between Odoo 13.0 and Odoo 14.0 when registering payments. You will need to decide which workflow you want to use. By default the upgrade will assume that your workflow is to reconcile all payments on invoices with bank transactions. Invoices will be marked "in payment" when a payment is registered and will only be marked as "paid" after reconciling with a bank transaction. If reconciling bank transactions is not part of your workflow, you should change the outstanding account for incoming and / or outgoing payments on the relevant bank journal to the bank account of that journal. If this is done, payments registered on invoices result in them being marked as "paid" right away, and it will no longer be possible to reconcile a bank transaction with them.

• Following a refactoring in how the payments (bank statements) work in the accounting of Odoo 14.0, the lock date, defining a date limit before which the accounts must be left untouched, has to be set on your companies for the upgrade. Without it, the upgrade could change your accounting for periods you consider as closed/locked. As the lock date was not set on your company(ies) Moller SpA (or they were very old), it has been set automatically to 2021-07-26. If you do not agree with this lock date, please set your lock date on your company(ies) before upgrading your database.
• The following payments have been deleted during the migration because there were posted but no longerlinked to any journal entry: [1325, 3311]

Disabled views

The below custom views have been disabled during the migration because they were no longer valid.
Odoo Studio: account.supplier.payment.tree customization