TeamDesk Knowledge Base & Support

   Home      FAQ      Forum      Idea Exchange      Ask a Question      My Stuff      Help   
Force update NOW Action (Docs and attachments)
Dear All

We are all using TeamDesk and its various Workflow actions. They are easy and powerful.

Yet, one some actions, their effect is delayed and this is a problem.

Example : A button commands two actions
- Action 1 : update a field of some record.
- Action 2 : send a TeamDesk document using the field changed in Action 1 via a Call / POST action.

If you press this button, the update of the Action 1 will happen after the Action 2 occurs.
Action 2 will send a non-updated version of the document.

As of now, the solution consists in creating a Time Trigger, and placing the action 2 in this Trigger.
Time Triggers run every 5 minutes : this is not acceptable for some usages.

This also occurs when you move files (URL Doc -> File Attachment)

What would be great, would be to have an action Update which we could use as
Action 1.5 : Force update NOW the data

There might be a solution with todays tools / I would love to learn about it.

Kind regards,


Date Created
6/14/2022 12:54:58 PM
Date Updated
7/5/2022 6:20:56 AM
Not Planned
Promoted By
calvin petersHeather ClemonsPatricio Bustos
Kirill Bondar  Staff  6/14/2022 2:12:42 PM
This kind of action would allow a limited gain mainly in context of calling own API via Call URL, but will allow for undesirable consequences (partial updates) when misused.

We added a lot to Create/Update/Delete actions to allow them to be used instead of "self" REST API calls and "Generate and Store Document" seems the only jewel missing in the crown.
Pierre 6/14/2022 2:26:19 PM
OK - I am creating the request !!
Pierre 6/14/2022 2:28:24 PM
upsert is also missing
Kirill Bondar  Staff  6/14/2022 4:36:58 PM
Upsert in fact is a "convenience method" -- API checks for a presence or absence of key and then routes the execution either to Create or Update. With the relation, summary / count of records and a pair of triggers you can achieve the same :)

But well, it's on an edge of the radar.
Philipp Matuschka (MMB) 6/15/2022 4:01:44 AM
I think this can be solved by
- having a hidden Button 2 for the second action
- doing the first action with Button 1
- as the last action of Button 1, call Button 2.
that way the update from Button 1 is committed when Button 2 starts it work.

I am pretty sure I have done this somewhere in the past, just can't find it right now.
Pierre 6/15/2022 4:07:22 AM

Brilliant idea ! Thanks for the input

How do you call a button in an action ? do you make a call to URL address of the button ?
Something like :

Kind regards


calvin peters 6/15/2022 11:42:31 AM

*How do you call a button in an action ? do you make a call to URL address of the button ?
Something like :

I have used NAVIGATION action for the second hidden button actions.
It has worked well for me in a number of instances

NAVIGATION allows for the selection of a CUSTOM BUTTON as a destination

Kirill Bondar  Staff  7/5/2022 6:20:56 AM
Document action is "officially released" now, with some bonus:
Back to Search Results