Parent Table checkbox changed, triggers automation that updates child table for notification

  • 0
  • 1
  • Question
  • Updated 11 months ago
  • In Progress
  • (Edited)
I'm currently trying to send Notifications based on individual records in a child table. The Trigger for this is when a checkbox is checked in a parent record.

I know that there's a current limitation in not letting a lookup field to be a trigger for a Email Notification, so I started thinking outside of the box.

I have an automation set up, which is triggered when the parent table is changed, and it will update a "system" field in the related children records.

I then am having this system field be the trigger for a notification at the child table level.

My question is this... with this setup, will the notification come across as a Multiple Record Version email, or as a single record email?
Photo of Ryan Stanford

Ryan Stanford

  • 1,992 Points 1k badge 2x thumb

Posted 11 months ago

  • 0
  • 1
I tested this once out of the curiosity of that exact question, and the Automaton ran slow enough to be seen as separate updates and hence separate email Notifications. 
... and the release notes just came out, so my answer has a best before date of October 14th! In other words, I retract my answer.

  • Starting in November, the modify records action in an Automation will now edit records in bulk instead of one at a time. This will make your automations significantly more efficient and prevent some “rate threshold limit” errors from happening when you have an automation that triggers another automation. Note: If you are using a modify action to trigger email notifications with a custom message, you should make sure the notification is set up to properly use the multiple record version of the email notification. More about setting up multiple record notifications.
Photo of Alex Wilkinson

Alex Wilkinson

  • 1,186 Points 1k badge 2x thumb
I have not tested this or done something similar. However, I concur with Mark's 2nd comment that it will be a "multi-record" operation, but for a slightly different reason.

The "starting in November" release-note really does not directly answer your question. It seems to imply, however, that an automations with an action step that modifies more than one record will be processed like a "multi-record" operation. Possibly, the internal implementation is similar to doing a grid-edit on multiple records and saving them as a batch (not one by one). If so, then the internal implementation for your follow-up email-notification would be the same as if you had done a batch grid-edit or a csv-import, i.e., a multi-record email.

As a precaution, you might use the same email template for both single-record and multi-record scenarios, if you can craft the text of the email appropriately to fit both scenarios.