I have a custom field that is a lookup to the standard parent field to use in place of it for a functionality on the Account object. I now have a requirment for the standard parent field to have the same value as the custom lookup field whenever it is edited. Would it be easier to create logic with a class and trigger or process builder?


Process Builder would be a lot simpler in this case, although it may have unintended side effects during mass updates, so you will want to test your logic carefully with bulk updates to make sure you don't run in to any problems.

  • Process Builder has created some issues in terms of mass updates in my org already so I guess Id better go with a class and trigger. I'm relatively new to coding but I haven't found much documentation on how to code something like this. Has anyone asked a similar question on here about the logic? – B Valentine Mar 21 '19 at 15:54
  • @BValentine I personally have answered this a number of times. Here's one example. Lots of other examples exist here on SFSE and elsewhere as well. – sfdcfox Mar 21 '19 at 16:02

I would say use the process builder, however, it all depends on what you're more comfortable with, I personally would use a process builder as its such a simple process.

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.