1

I have a flow that I'm triggering via Process Builder on the Opty Line Item object. The flow currently creates a new Opty and then updates a custom field on the original Opty Line Item with that new Opty's ID. The flow looks like this:

enter image description here

As you can see, I have a null check at the top of the flow for a field called CSM__c, which is located on the related Account to that Opty Line Item. If CSM is null, I want create the new Opty without referencing that CSM field. If it's not blank, then I'll pass the CSM value to the new Opty.

The issue I'm having is when triggering this flow with a null CSM__c field, SFDC throws this error:

The flow failed to access the value for ParentAccount.CSM__c because it hasn't been set or assigned.

I can't for the life of me figure out how to check if this field is null..my current null check looks like this:

enter image description here

I've also tried changing the formula to "EQUALS null", "EQUALS (blank)", "WAS SET false", using a formula for ISBLANK and ISNULL, literally all of those return the same error.

Would really appreciate if someone could share best practice for checking for null values in Flows.

EDIT I've updated my Flow and Decision screenshots above with the most recent versions.

  • 1
    Are you sure it is failing at the decision and you are not setting the field later on in the update action for example? – Robin De Bondt Sep 30 '16 at 20:57
  • Are you sure that ParentAccount is the field for related account you want to use? It is used to set the Parent for the account, and the error says that this relationship wasn't set. Try to use Account.CSM__c, and, with that, you don't need any CSM__c null value validations. – o-lexi Sep 30 '16 at 21:44
  • The error states it's failing on the decision: An error occurred at element CSM_Null (FlowDecision). Regarding the ParentAccount, this is actually a custom SObject variable that I created, and I am assigning the Account to it via ProcessBuilder. It's definitely set – tenpiecenugget Oct 3 '16 at 18:00
1

When you pass a record from PB to Flow said record only contains fields that have values (not null). Otherwise those fields are "not set". You should check if they are not set first, then check if is null;

Use the was set operator and your conditions could look like this

{!ParentAccount.CSM__c}   was set   {!$GlobalCOnstant.FALSE}
{!ParentAccount.CSM__c}   is null   {!$GlobalCOnstant.TRUE}

with All conditions must be true (OR)


Change your Decision Element to look like this:

enter image description here

Note that the only difference is this:

enter image description here

  • Appreciate the suggestion, but unfortunately this didn't fix it (although I was very hopeful!). Still getting the same error: "An error occurred at element CSM_Null (FlowDecision). The flow failed to access the value for ParentAccount.CSM__c because it hasn't been set or assigned." Including screenshots of updated Flow and Decision in the original quesiton. – tenpiecenugget Oct 3 '16 at 18:02
  • @tenpiecenugget Based on your screenshot you never changed your condition logic to use OR instead of AND. I updated my answer to better show the change to make. – dBeltowski Oct 3 '16 at 20:25
  • Ah thanks for pointing that out. I actually decided to rebuild the flow with different logic and it works great now. Appreciate the help – tenpiecenugget Oct 7 '16 at 23:46

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.