[SalesForce] Process Builder and Formula evaluates to true

Is there a trick to the Formula evaluates to true option in Process Builder? I tried the following formula:

[Opportunity].Record_Type_Name__c == 'New License' && [Opportunity].StageName == 'Closed Won - Not Paid' && NOT(CONTAINS([Opportunity].Type, 'Additional'))

The flow never gets triggered.

Best Answer

Try using one equal sign:

[Opportunity].Record_Type_Name__c = 'New License' && [Opportunity].StageName = 'Closed Won - Not Paid' && NOT(CONTAINS([Opportunity].Type, 'Additional'))

EDIT: Found this note in the guide...

There must be a space between the function’s parentheses and the contents of the parentheses. For example, you’ll get an error for TEXT([Account].LastModifiedDate) but not for TEXT( [Account].LastModifiedDate )

EDIT2: Found an article that states picklist formulas are not supported and in the above guide there is a generic picklist not supported everywhere.

Either tool will work however workflow may be the better option right now. There is no function help in process builder so complicated formulas may be difficult to build out. Also picklist formulas do not work in process builder. - See more at: http://gearscrm.com/overview-of-salesforce-process-builder#sthash.jbW4B8Kc.dpuf

Guide states:

Processes evaluate picklist fields as if they’re text fields, so some functions that normally support picklists may not support those fields.

Related Solutions

[SalesForce] Using ISCHANGED(ISPICKVAL(StageName)) in Process Builder Formula

Your first formula was probably the closest. Here's the revised version.

The IsPickVal function requires two parameters, separated by a comma. The IsChanged function requires one parameter, the field to check for changes.

OR(
  AND( ISPICKVAL([Opportunity].StageName, "Prospecting"),
       ISBLANK([Opportunity].NextStep) ),
  AND (ISPICKVAL([Opportunity].StageName, "Prospecting"),
   ISCHANGED([Opportunity].StageName),
  NOT(ISBLANK([Opportunity].NextStep)),
  NOT(ISCHANGED([Opportunity].NextStep)) ) )

[SalesForce] Validation Rule stops Process Builder to fire

You have two options,

You can create a WF rule to update "Close Date" on Opportunity, Unlike PB, WF rule field update doesn't trigger validation rule (as per order of execution where as process builder updates are enforced to evaluate validation Rules)
You can create a field "exclude_pb__c" and add ischanged condition on this field in you validation rule. You should also update this field from your PB(see image attached..). You still need to give edit access to exclude_pb__c for the profiles mentioned in the pb and hide this field from the layout so they will not be able to modify this field.

AND( 
ISPICKVAL(PRIORVALUE(StageName),"Closed Won"), 
CASE($Profile.Name, 
"ProfileName1",1, 
"ProfileName2",1, 0) = 0,
NOT(ISCHANGED(exclude_pb__c))
 )

of the two, I recommend first option.

Best Answer

Related Solutions

[SalesForce] Using ISCHANGED(ISPICKVAL(StageName)) in Process Builder Formula

[SalesForce] Validation Rule stops Process Builder to fire

Related Topic