Skip to main content
Michael Dely a posé une question dans #Collaboration
Hi I have a User Field on the Task object that sends a notification when a value is entered.  I've noticed when the field is changed from one user to another the notification seems to still go to the previous owner.  I am unsure why.  It seems like the workflow fires too quick and just doesn't catch the change in time.  Here is my formula.  Look forward to hearing everyone's feedback.  

 

NOT(ISBLANK([Task].FYI__c)) &&

 

ISCHANGED([Task].FYI__c)

 

Thanks,

 

Mike 
16 réponses
  1. Forum Ambassador Michael Brown (Salesforce)
    10 mars 2021, 02:22
    Hey Michael, 

     

    Sorry for the delay! We can definitely get this resolved. You'll need to add an OR statement so your workflows fire on create. This is what this looks like on my end. 

     

    For the 1st workflow that sets the FYI Email field, my workflow now looks like this:

    OR(

    AND(ISCHANGED(FYI__c),NOT(ISBLANK(FYI__c))),

    AND(ISNEW(),NOT(ISBLANK(FYI__c))))

    Basically, this will fire if either of these criteria are met:

     

    1. FYI__c is populated when a new record is created

     

    2. FYI__c is changed on an existing record and is not null

     

    For the 2nd workflow that sends the notification when the FYI Email is changed, it looks like this:

    OR(

    AND(ISCHANGED(FYI_Email__c),NOT(ISBLANK(FYI_Email__c))),

    AND(ISNEW(),NOT(ISBLANK(FYI_Email__c))))

    This 2nd workflow will fire if either of these criteria are met:

     

    1. FYI_Email is populated on a new record

     

    2. FYI_Email is changed on an existing record and is not null

     

    Where this can get confusing is that at first it doesn't seem like FYI_Email is being populated on creation, since it's being populated via the first workflow rule after the record is created when FYI is populated. However, the 2nd workflow transaction is still technically fired upon creation. 

     

    I hope that gets you sorted out, but let me know if you have any questions. 

     

    Thanks!