[Release Notes] ERPNext Version 13 has been released

[nabinhait]

@knimer

frappe.reload_doc('regional', 'report', 'uae_vat_201')

Have you committed after reloading from console?

Use frappe.db.commit() to commit.

[nabinhait]

@Majid_Ejaz

frappe.reload_doc(‘accounts’, ‘doctype’, ‘pos_invoice_item’)

Use this frappe.reload_doc('accounts', 'doctype', 'pos_invoice_item')

[gsarunk]

@nabinhait

bench switch-to-branch version-13 frappe erpnext --upgrade

I do face the same issue. Any fix ?

[rachanna]

How to upgrade bench CLI?

[nabinhait]

So, you are using perpetual inventory system and in perpetual inventory system, when you receive an Item, system debits “Stock In Hand” instead of booking expenses (COGS). In version 13, the system corrects it automatically and gives a message.

[revant_one]

I shared this in last post.

I’m sharing it again.

This topic is a tutorial for installing and upgrading bench [Tutorial] Installing and Upgrading Bench CLI (ver. 5.3)

[nabinhait]

@mainul

Try skip failing.
bench --site dev.nectar.lmnas.com migrate --skip-failing

skip-failing is not recommended, it can lead to other unwanted problems. Always try to dig deep and solve the actual error.

[Majid_Ejaz]

I did this

Use frappe.db.commit() to commit.

now getting

frappe.exceptions.DoesNotExistError: DocType UAE VAT Settings not found

[nabinhait]

Reload these doctypes as well:

frappe.reload_doc('regional', 'doctype', 'uae_vat_settings')
frappe.reload_doc('regional', 'doctype', 'uae_vat_account')
 

[gsarunk]

@mainul

bench --site dev.nectar.lmnas.com migrate --skip-failing

This method did not work. Still the same error.

[gsarunk]

I tried this method. Still the same error.

[Majid_Ejaz]

So to Summarise (especially for UAE instances) following steps are required:

bench --site your-site-name console

In [1]: frappe.reload_doc(‘accounts’, ‘doctype’, ‘pos_invoice’)
Out[1]: True
In [1]: frappe.reload_doc(‘accounts’, ‘doctype’, ‘pos_invoice_item’)
Out[1]: True

For UAE Variant
In [1]: frappe.reload_doc(‘regional’, ‘doctype’, ‘uae_vat_settings’)
Out[1]: True
In [1]: frappe.reload_doc(‘regional’, ‘doctype’, ‘uae_vat_account’)
Out[1]: True
In [1]: frappe.db.commit()

It worked just fine for me.

Thank you very much

[rachanna]

Please advise when we have Pyhton 2.7 then what should be the method from upgrading from ERPNext: v12.19.0 (version-12), Frappe Framework: v12.16.3 (version-12)

[rachanna]

Thanks, it is working fine but do I need to repeat above installation steps?

[krnkris]

@casesolved-co-uk

There is not a must to use this or other programs.
There is a must to contribute to make it better.
The complain at least must be equal with contribution.

Not all reported bugs means real failure, but people always relay to it, try to get immediate attention as getting used to it on differ platforms.

Better to understand how this program builds up + understand the environment around it, then search a little bit and then find the solution, it moves things forward.
Not only the program works the environment must work around it.

Hope it gives a little clarification.

[amit_vaid]

npm yarn version , issue i resolved

[martin42]

Bench in editable mode warning is discussed here, but without clear solution

Easy install production install bench in editable mode

It is recommended to install bench not in editable mode for production. Manually this can be done by doing pip3 install frappe-bench. But using easy-install even if I’m add --production, the bench is still installed in editable mode. WARN: bench is installed in editable mode! This is not the recommended mode of installation for production. Instead, install the package from PyPI with: `pip install frappe-bench` Is this a bug in the install script or is it required to do this way? Can I dele…

[mujeerhashmi]

Got rid of custom_script fixtures in the custom app. I could update to v13.

[gsarunk]

@nabinhait

frappe.db.commit()

Solved: if you are running multi sites, we need to bench --site sitename console and run above commands.

[mujeerhashmi]

No resolution for this yet.