0

I have an object (let's call it Object2), which has a lookup to account.

Object2 has a field called combined, which concatenates the value of account.Customer type and a few other fields (including a large text area field).

The issue I have is that when the account customer type gets changed, the field update workflow doesn't get triggered.

I wanted to solve this issue in this way: created a field called customer type in Object2, added a process builder to update customer type field. So far this works fine, ie updating the account customer type will cause the object2 customer type to be updated.

But still this change doesn't trigger the workflow field update to update the combined field.

I can see that last modified values are showing the latest change that was caused by update on account and triggering process builder. But still the workflow field update is not triggering.

Here is the rule criteria for the workflow field update:

OR(IsChanged( LastModifiedDate ),IsChanged( CreatedDate),NOT(ISBLANK(OwnerId)))

I can't understand what causes the workflow not to be triggered. I am wondering can the process builders even trigger a workflow field update, or I am making a mistake somewhere else?

  • 1
    Just use every time it is updated or created as the type and use the ownerid part as the criteria. If you do not want it on insert add !isNew() to the criteria. – Eric Mar 21 at 4:05
  • @eric worked fine. Thanks! – apadana Mar 21 at 4:09
  • 1
    great. Added it as answer. IIRC the lastmodifued and created date are done after the fact and do not trigger more updates – Eric Mar 21 at 4:14
1

Change they type to whenever created or edited

Use the ownerid part in the criteria. If you want to exclude insert add !isNew() to the criteria

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.