You need to sign in to do that
Don't have an account?
Stewart McNaught
Field Update: Pushing null into a field with flow
I have created a flow that loads data from a custom object called staging plan.
- Staging plan contains fields that are group into the follow sections
Action Plan 1, Action Plan 2 & Action Plan 3
- The user is then asked the type of task they want to create from the data.
For example: Use select Action Plan 1
- A task is created populated with Action Plan 1 Fields on staging plan.\
- Next the data in the plan fields need to be set to null.
So the four field in Action plan need to be cleared.
What variable\constant do I use to remove the previous value and store a null in the field?
I am using the Cloud Flow designer.
Thank you - Global Constant: EmptyString.
I originally though that variable was causing an error, but it turned out to be an error when I am trying to create the TASK record. The WHOID is throwing an error ... AccountID is not valid if account is a person account.
To resolve this issue, I added logic to the flow to determine if the account record is a person account using the IsPersonAccount field. If this evaluates as true then I assign the id stored in the account field PersonContactId.
All Answers
Are you in the Desktop or Cloud Flow Designer?
If you're in the Cloud Designer and this is a text field, try the Global Constant EmptyString. I can't find any documentation on what it does, but I wouldn't be surprised if it emptied the string.
As for the Desktop Designer, I'm not sure this will work, but I know for Bulk API calls, you blank out a field by passing the value #N/A to it. This is basically a wild shot in the dark, since I don't think Visual Workflow uses Bulk API on the back end.
I am using the Cloud Flow designer.
Thank you - Global Constant: EmptyString.
I originally though that variable was causing an error, but it turned out to be an error when I am trying to create the TASK record. The WHOID is throwing an error ... AccountID is not valid if account is a person account.
To resolve this issue, I added logic to the flow to determine if the account record is a person account using the IsPersonAccount field. If this evaluates as true then I assign the id stored in the account field PersonContactId.
I tested both :
- Leaving the field blank
- Assigning the global constant : {!$GlobalConstant.EmptyString}
But nothing is working !
The data / value in the field is not removed !
Do you have any other solution / workaround ?
Thank you !