Any changes recorded on an account record push to our financial program outside of salesforce.
Our account object has a related object whose records contain data/detail that we also push to our financial system with the account record.
The challenge is a change to the record of the related object does not qualify as a change to the account record. When we make a change/update to this related object record, I have to go back to the related account record and make an arbitrary change in order for the related object’s change to be captured in our financial software.
The goal: for any change made to a record of this account’s related object, it triggers an update on the related account record – thus automating/capturing the change in our financial software.
What would be best practice in this scenario?
A Process Builder, Flow? Something else? I’ve been warned to not go crazy with Process Builders – I guess if you have enough of them they can slow things down in your org? I’m also slightly terrified of Flows and creating improper loops or having things setup in a way that are excessive and create an unnecessary burden on our org.
Finally, when speaking about “triggering an update” on the account record, do you think I will need to create an arbitrary field to act as a receptable of registering a change on the record? A Boolean field or checkbox that goes on/off? Also trying to brainstorm what might be best practice here.
Thank you in advance for any thoughts or advice!
답변 2개
Michael Brown (Salesforce) 
Forum Ambassador
Hi Jeff,
You should be fine if you implement Process Builder/Flow for something like this. You could do something as simple as creating a date/time field on the Account that will capture the last modified date of your related object.
You could then have a process or flow fire whenever a child record is modified, and then have that automation tool timestamp your new date/time field on the Account with the time of the update. This would register an update on your Account.
This shouldn't cause any issues since this would be a relatively simple update operation and it's not like you would be looping through each child object and updating a bunch of records.
Thanks,
Mikey
