I have a grouped execution of actions on a table for when a user submits a form. I would like to get an action that forces a sync because I have delayed sync enabled and realized that we are having some data loss from people closing their apps before the form was fully submitted.
I have tried using the LINKTOROW()&"&at="&(NOW()+1)
as seen on other posts but it does not work when it is part of a grouped sequence of actions. It will not force the app to update/sync and just continue on with the delayed sync.
Hereโs a breakdown of the grouped actions when Form Submitted triggers it (via form saved behavior)
LINKTOROW([ID], "Jobs-Assigned_Detail")&"&at="&(NOW()+1)
Any ideas on what I could do to mitigate this?
Solved! Go to Solution.
Huh, that seems to have worked. Odd because I remember doing that earlier last week and it didnโt work. Fabian with the magic touch, Thank you!
Answer:
If you are making use of Delayed Sync and would like to force a sync using LINKTOROW()&"&at="&(NOW()+1)
on a grouped sequence of actions, ensure the sync is at the END of the stack.
In my case:
On Form Saved (On Reports Table)
Report Submitted Action (Grouped Execution)
LINKTOROW([ID], "Jobs-Assigned_Detail")&"&at="&(NOW()+1)
User | Count |
---|---|
14 | |
11 | |
9 | |
7 | |
4 |