0

There is an object called CustomerOfTheWeek.

It has a lookup field called Account.

There is another field called Account Type, which is a field update (+ workflow rule) which for the purpose of this question assume it's just the Account Type from the Account. (In reality it simplifies the account types in the Account object to a more generic set of values).

The field update gets triggered when something on the CustomerOfTheWeek changes.

The issue is that if the Account Type changes, the Account Type field in the CustomerOfTheWeek doesn't get changed. (which makes sense but that is not what the client expects).

So a mere edit and save on the CustomerOfTheWeek is now required to trigger the Account Type change.

Is there any way to trigger the change in Account Type in Account object to cause a trigger on the Account Type in CustomerOfTheWeek object?

  • should the two fields have the same values? If yes, why not a formula field? – m Peixoto Mar 20 at 9:03
1

In lieu of using a formula field, which would probably work in most cases, you can use a Process Builder on the Account to update the Customer of the Week record. The Process Builder has an option to update child records related to a parent record.

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.