ContributionsMost RecentMost LikesSolutionsRe: Ground rules for triggering an email notification or automationMark, The pipeline worked great. It appears the sequential operation of the For…Each loop on the search results allows for each record to be triggered slowly enough that QB treats it as a single notification. Thanks for your help, your suggestion to check for QB treating the email as a multi-notification pointed me to root cause. I’m not clear why the automation daisy chain didn’t work, but since the pipeline works I’ll go with that. Thanks! Paul Re: Ground rules for triggering an email notification or automationYep, separate automation. I understood that you didn’t mean multiple actions in the same automation. I’m going to try to use a pipeline to trigger the notifications instead of automations. I’m thinking that maybe I can design the pipeline to search for a set of records that meet filter criteria for sending out notifications, then step through each record to set the trigger field for the notification. I’m hoping that the sequential flow in the pipeline will force QB to recognize the notifications as single rather than multi. Don’t know if this will work, but worth at least looking at. I’ll report back. Thanks Paul Re: Ground rules for triggering an email notification or automationMark, The daisy chain automations triggered, and the "request" and "actually" checkboxes are checked, but the email notifications are still being considered by QB as multi-notifications. I even added another step in the daisy chain with a second "request" checkbox between the first "request" checkbox and the "actually" checkbox, including of course the additional automation to set it the additional checkbox, and still the same issue occurs. I'm not getting any automation errors. The sole problem is that QB is considering the record updates as a multi-notification instead of single. I'm wondering if a pipeline would fix this, to search for the records that need to be triggered, then step through the search results recordset one record at a time to set a trigger checkbox that would trigger the notifications. Thoughts? Thanks Paul ------------------------------ Paul Streit ------------------------------ Re: Ground rules for triggering an email notification or automation Mark, You were right, I verified that QB is considering them to be a multi-notification type. I'll try your solution and report back. I didn't see this before because the notifications were set for single notification only, so nothing was going out even though triggering was occurring. Back soon, Paul Re: Ground rules for triggering an email notification or automationOK, I'm almost there. I set things up but in the very last step, the automation that sets the trigger checkbox that in turn triggers the email notifications has an issue. The automation is setting the checkbox correctly, but the email notification doesn't trigger off of it. If I manually set the checkbox the email notification triggers. So it appears that when an automation updates a field in a record this is not the same as manually placing the record in edit mode, setting the checkbox, and then saving it. Any suggestions on what to do here? Thank you, Paul ------------------------------ Paul Streit ------------------------------ Re: Ground rules for triggering an email notification or automationGood point regarding the approval response as a trigger. This may work. I’ll mess with it and report back. Might be a few days. Thanks Paul Re: Ground rules for triggering an email notification or automationGood point regarding the approval response as a trigger. This may work. I’ll mess with it and report back. Might be a few days. Thanks Paul Re: Ground rules for triggering an email notification or automationMark, The formula field on the parent record is changing through the passage of time and due to changes in summary fields so it will not trigger a notification directly. The parent table is a table of proposal records. The child table stores a list of approvers, one approver per record. Some approvers must approve before other approvers, so there is a sequence priority field in the approver table that stores the sequence priority which is simply an integer like 1 for the first set of approvers, 2 for the second, etc. There is a a formula checkbox field in the parent proposals table that is set to true when all of the first set of approvers have responded and approved. When the formula checkbox field toggles to true I want to update a trigger field in the parent table proposal approval record that triggers an automation to update a similar trigger field in the child approver records filtered on the sequence priority 2 field which in turn would trigger email notifications to each second sequence priority approver. So I'm thinking that the way to do this is to have a formula URL field that checks if the formula-checkbox field is true, and if so, places the proposal record into edit mode, updates a trigger text field in the proposal record with the current date/time converted to text, then saves the record by redirecting back to display the proposal table default home screen report. The update of the trigger field would then fire an automation or action that would update a text trigger field with the current date/time converted to text in all sequence priority 2 child approver table records. I'm assuming that when the automation updates each child approver record that this effectively edits and saves the record which would trigger the email notification. Is this a correct assumption? I wrote code for the parent proposal record formula-URL field. The [Logic Checks Complete] field is the formula checkbox field that indicates when all sequence priority 1 approvers have approved and that sequence priority 2 approver email notifications can be sent out. Field ID 210 is the proposal record text trigger field that would be updated with the current date/time by the formula-URL field. It doesn't work. I'm guessing that maybe assuming a formula URL field can execute automatically without a user manually clicking it as a button is the issue, but I don't really know. If that's wrong, is there another way to automatically update the trigger field based on the state of the formula checkbox field? The formula URL field code is shown below: //Check to see if sequence priority 1 approvals are complete IF([Logic Checks Complete]=0, "", //Edit the current proposal record URLRoot() & "db/" & Dbid() & "?act=API_EditRecord&rid=" & [Record ID#] //Set the automation trigger field (a text field) to the current date/time & "&_fld_210=" & ToText(Now()) //Redisplay the current proposal record to automatically save the change which should trigger the automation & "&rdr=" & URLEncode(URLRoot() & "db/" & Dbid() & "?a=dr&rid=" & [Record ID#]) ) I suspect that many QB app developers encounter this situation where they want to trigger an email notification, action, or automation based on a calculation instead of a record add/delete/modify event, so how to address this would likely be useful to the entire community. Thanks, Paul ------------------------------ Paul Streit ------------------------------ Re: Ground rules for triggering an email notification or automationMark, I set up both an automation and an action as you described. Both have the same issue - I somehow have to trigger an email notification when a formula field checkbox is true. Is there a way to detect the change in the formula field, then update a trigger field and then save the record which would trigger the automation? I included some formula URL code in my original post but it didn’t work, not clear why. Thanks Paul Re: Ground rules for triggering an email notification or automationHey Monster, I added the fields and action as you suggested, but the action doesn't trigger even though the formula checkbox changed value. I think it's because the action only triggers if a record is edited and saved or added and saved, meaning it won't trigger when a formula field simply changes. Thoughts? Thank you, Paul ------------------------------ Paul Streit ------------------------------