Timeline for Salesforce Flow : Check for null value in custom lookup field
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 3, 2016 at 18:08 | history | edited | tenpiecenugget | CC BY-SA 3.0 |
added 115 characters in body
|
| Oct 3, 2016 at 18:00 | comment | added | tenpiecenugget | 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 | |
| Sep 30, 2016 at 21:44 | comment | added | o-lexi |
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.
|
|
| Sep 30, 2016 at 20:59 | answer | added | dBeltowski | timeline score: 1 | |
| Sep 30, 2016 at 20:57 | comment | added | Robin De Bondt | Are you sure it is failing at the decision and you are not setting the field later on in the update action for example? | |
| Sep 30, 2016 at 20:51 | history | edited | tenpiecenugget | CC BY-SA 3.0 |
added 55 characters in body
|
| Sep 30, 2016 at 20:47 | review | First posts | |||
| Sep 30, 2016 at 20:59 | |||||
| Sep 30, 2016 at 20:45 | history | asked | tenpiecenugget | CC BY-SA 3.0 |