[Release Notes] Version 11.1.0!

ragh · January 30, 2019, 5:59am

Hi @snv
Custom Script Reports related API’s merged?

Thanks,
Ragh.

snv · January 30, 2019, 6:01am

To answer your question, I don’t know what you’re talking about.
You can check the pull requests on GitHub.

ragh · January 30, 2019, 6:06am

Okay. Thanks!!

Helio_Jesus · January 30, 2019, 3:13pm

Congrats to all of us using, fixing and promoting such a good tool of work.

quadtree · January 31, 2019, 12:15am

Hi folks!! Ver 11 looks really amazing. But I’m facing a trouble, v 11.1 doesn’t run any of my previous Custom Scripts at all!!.. migrating from previous v10, not even for debugging. I saw a few changes on documentation regarding the use with ‘refresh’ and refresh: { func… Tried both and none seems to execute the code. Anyone facing same thing? regards!

deatram · January 31, 2019, 3:15am

same issue here. just went to check now after seeing your post and found out my custom scripts don’t work anymore.

ishanloya · January 31, 2019, 6:15am

So am I. For e.g, I have a Purchase Order Approval workflow in which the status goes from Draft to ‘To Receive and Bill’ directly even though it should ideally go to the next defined workflow state ‘Pending Approval’

johnskywalker · January 31, 2019, 6:50am

Here’s what I did, I duplicated the workflow. And then I gave access to workflow action to that particular Role. I noticed that in the v11 update there’s a new doctype workflow action.

wale · January 31, 2019, 8:35am

Hi ,

Workflows and Custom Scripts are used extensively by many ERPNext users. I think it is critical to provide a step-by-step guide on how this should be managed when migrating from V10 => V11

It can be quite devastating, in some cases, to upgrade and discover all your Workflows and Custom Scripts have stopped working!!

This needs to be looked into seriously

Thanks

johnskywalker · January 31, 2019, 9:15am

In case you guys having problems with page/report roles,

You may use this code I made:

gist.github.com

https://gist.github.com/jvfiel/3f9e5a07cfc5362665f21de9a4a3ad59

init.py

import frappe

#khs.kong_hua_school.update_report_roles
def update_report_roles():
    #KHS Student Rankings
    #KHS Mastersheets
    #KHS Report Cards
    #Kong Hua School
    for report in frappe.db.sql("""SELECT name FROM `tabReport` WHERE `tabReport`.module 
                                                              IN ('KHS Student Rankings',

This file has been truncated. show original

saurabh2804 · January 31, 2019, 9:55am

I have observed that I can no longer customize core frappe DocTypes like “User”. Is there any workaround? I need to add a few fields to the User DocTypes.

snv · January 31, 2019, 10:06am

A contact (which has a user link) can be customised. What is the usecase for customising the user doctype?

saurabh2804 · January 31, 2019, 10:18am

Use case would be if we need additional information from the user during signup itself, like profession, City, etc. Since the Signup Page defaults to the User DocType, it would have been best if I could customize the User DocType after adding the required fields. Is there a better way to go about this? I could make a web form with a custom DocType but how would I add the OTP functionality to it?

bedo · January 31, 2019, 3:34pm

Is possible to have two version (v 10 and v 11) on one server? Right now we have two sites, one for testing/trying/experimenting/learning and another one for production. But both sites run the same frappe/erpnext version.

How can I switch one site only to v11 and keep production in v10 until I test everything? Is this possible? Or only by using another server / virtual machine?

clarkej · January 31, 2019, 3:56pm

Few would disagree with you. This is a classic resource problem, we need more volunteers and contributers

edit: Don’t forget all customizations are a user responsibility, moreover regardless whether your software is proprietary or open source, the rule is caveat emptor!

wale · January 31, 2019, 5:39pm

Hi @clarkej

normally I would have agreed with you but definitely not for a major release like this. You shouldn’t put out release notes and steps to update for a major release without at least a clear warning that Custom Scripts and Workflows won’t work… that’s quite serious and will undoubtedly lead to some very nasty user experiences!

If we can save people some serious headaches then we should, rather than say “Sorry, it’s your responsibility to ensure everything works” - even if it is

Cheers

clarkej · January 31, 2019, 6:01pm

“at least a clear warning that Custom Scripts and Workflows won’t work… that’s quite serious and will undoubtedly lead to some very nasty user experiences!”

Ok yes perhaps a sentence or two of warning or say a disclaimer.

The question is, what is obvious and what to assume about the user - where do you draw the line?

Naivete and due diligence go hand in hand and usually resolve themselves in short order.

Caveat emptor means you may need to pay someone to blame

quadtree · January 31, 2019, 6:05pm

I totally agree… we don’t matter to catch-up with changes on how things work (is part of the growth process), but lack of information makes it impossible to contribute. We’ll remain in V10 until Custom Scripts are back , since our project relies on it. All the best for the magnificent work !

clarkej · January 31, 2019, 7:08pm

Well that’s the basis of this forum, for folks to inform themselves assuming they are motivated!?

EDIT: Perhaps best to close this thread now…