Migration to version 16.0

[sbidoul]

Todo

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

Modules to migrate

• pos_access_right - By @geomer198 - [16.0][MIG] pos_access_right #957
• pos_customer_display - By @legalsylvain - [16.0][mig] pos_customer_display #1159
• pos_default_partner - By @alv97 - 16.0 mig pos default partner #853
• pos_edit_order_line - By @flachica - [16.0][MIG] pos_edit_order_line #926
• pos_escpos_status - By @nwinkelstraeter - [MIG][16.0] pos_escpos_status #910
• pos_event_sale - By @BT-dmoreno - [16.0][MIG] pos_event_sale: Migration 16.0 #1022
• pos_event_sale_registration_qr_code
• pos_hide_banknote_button - By @legalsylvain - [16.0][MIG] pos_hide_banknote_button: Migration to 16.0 (from 12.0) #1173
• pos_hide_cost_price_and_margin
• pos_journal_image - By @legalsylvain - [16.0] mig pos_journal_image. (now : pos_payment_method_image) #1021
• pos_lot_barcode - By @yankinmax - [16.0][MIG] pos_lot_barcode: Migration to 16.0 #934
• pos_lot_selection - By @yankinmax - [16.0][MIG] pos_lot_selection: Migration to 16.0 #935
• pos_margin_account_invoice_margin - By @legalsylvain - [16.0] mig pos_margin_account_invoice_margin #1128
• pos_order_remove_line - By @suker - [16.0] [MIG] pos_order_remove_line: migration to 16.0 #925
• pos_order_to_sale_order - By @legalsylvain - 16.0 mig pos order to sale order #854
• pos_partner_firstname - By @victor-champonnois - [16.0] [MIG] pos_partner_firstname #1027
• pos_payment_change - By @julenfl - [MIG] [16.0] pos_payment_change #929
• pos_payment_method_cashdro - By @chienandalu - [16.0][MIG] pos_payment_method_cashdro: migration to 16.0 #1161
• pos_payment_terminal - By @nwinkelstraeter - [MIG][16.0] pos_payment_terminal #908
• pos_price_to_weight - By @legalsylvain - [16.0] MIG: pos_price_to_weight (from 12.0) #1146
• pos_pricelist_technical - By @legalsylvain - [16.0][MIG] pos_pricelist_technical #1130
• pos_product_display_default_code - By @suker - [16.0][MIG] pos product display default code: migration to 16.0 #927
• pos_product_mergeable_line - By @legalsylvain - [16.0] mig pos_product_mergeable_line #1145
• pos_product_multi_barcode - By @nguyenminhchien - [16.0][MIG] pos_product_multi_barcode: Migration to 16.0 #1037
• pos_receipt_hide_price - By @danielduqma - [MIG] pos_receipt_hide_price: Migration to 16.0 #851
• pos_reset_search - By @victor-champonnois - [16.0] [MIG] pos_reset_search #1030
• pos_sale_pos_event_sale
• pos_ticket_extra_company_info - By @legalsylvain - [16.0][MIG] pos_ticket_extra_company_info #1131
• pos_timeout - By @benwillig - [16.0][MIG] pos_timeout: Migration to 16.0 #1148
• pos_to_weight_by_product_uom - By @legalsylvain - 16.0 mig pos_to_weight_by_product_uom (from 12.0) #1127

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

[danielduqma]

Migration of pos_receipt_hide_price from 14.0 made in #851

[alv97]

Migration of pos_default_partner from 14.0 made in #853

[alexis-via]

No need to port pos_no_cash_bank_statement from v14 to v16. According to my tests, Odoo v16 generate by default accounting entries no only for cash journals but also for bank journals. It seems Odoo SA changed their mind again... good move this time :)

[legalsylvain]

Hi @alexis-via. Thanks for your remark. One question, the feature is native in which module (account, other ?), and since which release (15 / 16) ?
if the feature is native, I'll do a PR against openupgrade in the apriori file. (merged_modules section).

thanks for your reply.

[nwinkelstraeter]

Migration of pos_payment_terminal from 14.0 in #908 which is still missing from this list.
pos_escpos_status is also missing, which I would also like to migrate

[alexis-via]

About account move generation on POS v16: I made more tests, and I confirm that bank statement generation works well, but I have another problem: in v14, the boolean field "split_transactions" on pos_payment_method had a string "Split Transactions". In v16, this boolean field still exists, but it's string is "Identify Customer", so, if you enable it, it will not only split transactions but also force you to select a customer.
I will probably develop a module to be able to split transactions without obliging to select a customer ; I need it for payment by check.
FYI, I'll have to develop that before 31/12/2022

[legalsylvain]

In v16, this boolean field still exists, but it's string is "Identify Customer", so, if you enable it, it will not only split transactions but also force you to select a customer.

wow ! definitively, V16 looks not finished ! Please ping me when your module is ready.

And regarding my previous remark. Is pos_no_cash_bank_statement unnecessary in V15 or in V16 ?

thanks.

[nwinkelstraeter]

Migration of pos_escpos_status from 14.0 in #910

[alexis-via]

As promised, I worked on having 2 booleans fields on pos.payment.method:

• keep the native "split_transaction" ONLY to split the transactions
• add a second boolean "identify_customer" to oblige to select a customer
  As I found it too difficult to develop it via inheritence, I wrote a module "pos_check_deposit" https://github.com/akretion/odoo-usability/tree/16.0/pos_check_deposit that requires to apply a patch on the point_of_sale module of Odoo, that's why I didn't submit this module to OCA. Unfortunately, the patch is bigger than I thought (see file odoo-pos_check_deposit.diff at the root directory of the module) because in the generation of the account.move.line when closing the POS session, when split_transaction is enabled, Odoo always consider that a partner has been selected, so I had to patch 3 methods in pos.session that handle the generation and reconciliation of the account.move.line.

Another idea would be to be able to configure a "default partner" on a pos.payment.method ; when selecting a payment method in the POS frontend, if no customer has been selected yet, Odoo would automatically select this "default partner" as customer. That way, on the "Check" POS payment method, you would set the "default partner" to a generic "POS Check". Advantages:

• no need to modify the code that generate the account.move.lines.
• the cashier doesn't spend time creating/selection a partner when a customer pays by check
  I don't plan to write that module myself in the short term, so feel free to do it if you think this idea is good.

@legalsylvain I confirm that pos_no_cash_bank_statement is not needed in v16.

[suker]

Migration of pos_order_remove_line from 14.0 made in #925

[flachica]

Migration of pos_edit_order_line from 14.0 #926

[suker]

@sbidoul pre-commit needs to be update, pipeline are failing:

repo: https://github.com/PyCQA/isort
   rev: 5.10.1

to

repo: https://github.com/PyCQA/isort
   rev: 5.12.0

[rousseldenis]

@sbidoul pre-commit needs to be update, pipeline are failing:

repo: https://github.com/PyCQA/isort
   rev: 5.10.1

to

repo: https://github.com/PyCQA/isort
   rev: 5.12.0

@suker The errors you have there : #925 are real errors. You have to solve them

[suker]

Migration of pos_product_display_default_code from 15.0 #927

[julenfl]

Migration of pos_payment_change from 15.0 #929

[yankinmax]

@sbidoul @ivantodorovich I've opened new migration PRs for pos_lot_barcode and pos_lot_selection to supersede existing ones which needs fixing.
Old ones:

• [16.0][MIG] pos_lot_barcode: Migration to 16.0 #918
• [16.0][MIG] pos_lot_selection: Migration to 16.0 #917

New ones with tests green:

• [16.0][MIG] pos_lot_barcode: Migration to 16.0 #934
• [16.0][MIG] pos_lot_selection: Migration to 16.0 #935

[berteh]

please kindly add pos_tare to the modules that still need migration to 16.0.

[raulovallet]

why pos_report_session_summary is not here?