Apex Code Development You need to sign in to do that
Don't have an account?
TROG isblank formula not working in Visual Flow
I add a text input field to a FLOW screen. Its an optional field - not required. I later check to see if the user entered a value in to this field using a formula 'isblank'. When the user doesn't enter anything the result of this formula incorrectly states 'false'. My understanding is that isblank() is supposed to be TRUE if the value is either blank or NULL...per this help article:
*https://help.salesforce.com/articleView?id=customize_functions.htm&type=5
"IMPORTANT Use ISBLANK instead of ISNULL in new formulas. ISBLANK has the same functionality as ISNULL, but also supports text fields. Salesforce will continue to support ISNULL, so you do not need to change any existing formulas."
I created a small test FLOW to easily/quickly identify this issue.
Debugging...dont enter anything on the first screen and press next.
Failed. Why is it reporting isblank = false, when the user didn't enter anything???
*https://help.salesforce.com/articleView?id=customize_functions.htm&type=5
"IMPORTANT Use ISBLANK instead of ISNULL in new formulas. ISBLANK has the same functionality as ISNULL, but also supports text fields. Salesforce will continue to support ISNULL, so you do not need to change any existing formulas."
I created a small test FLOW to easily/quickly identify this issue.
Debugging...dont enter anything on the first screen and press next.
SImmyI am also facing the same issue please let me know if you comes up with any solution
TROGI dont have a developer support license, so SFDC told me they wouldn't work on this defect (Visual Flow not supported?!?) and kicked me to post it to this dev forum. If anyone sees this and has one, PLEASE post this defect/case so SFDC can work on resolving it. Thanks!
SImmyI have come up with an idea and it worked..so if yu want you can reply over here.
TROGSImmy - sure, love to hear your idea. I too used a work-around checking for both null and "", but we shouldn't have to. Its a defect, and unfortunately SFDC doesn't support fixing defects in Visual Flow unless you have a developer support package, so they told me to post it in the dev forums in hopes that someone that did have that package would see this and create a ticket to fix it (rrrrgg).