Forum Discussion

MarkShnier__You's avatar
MarkShnier__You
Icon for Qrew Legend rankQrew Legend
5 years ago
It could  be this issue here.

I believe that the modify records action will be done slow enough that it will be seen as a single record notification update for Notifications. If you get this working but the Notification only fires a multi record change notification which would not be suitable for your needs, let me know and we will just daisy chain one automation to call the next and that will slow it down enough to make individual record change notifications.   


I suggest that you enable the multi record notification feature of the Notification configuration and set it to come to you.  If it comes to you it means that the Notification is firing, but the updates are so fast that Quick Base considers them to be a multi record notification type.

If that is the case, then we need to slow them down so we daisy chain. Create a new field called [Date/Time to Actually trigger Notification].  Rename the old field to be called  [Date/Time to Request Notification].

Make a new Automation fire when the [Date/Time to Request Notification] changes to change the field [Date/Time to Actually Trigger Notification] to the current date/time.

Change the Notification to fire on this field [Date/Time to Actually Trigger Notification]

------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
PaulStreit's avatar
PaulStreit
Qrew Member
5 years ago

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



  • PaulStreit's avatar
    PaulStreit
    Qrew Member
    5 years ago
    Mark,

    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
    ------------------------------