1 of 1 people found this helpful
The refresh can be run with the following command: Reference-Tableau Server REST API - Tableau using the schedule-id(found with the Query Schedule command linked below) as the task-id in the refresh command.
As for the follow up question, Tableau schedules can be queried using the following command: Reference-Tableau Server REST API - Tableau
More information can be found in this thread: What's the relationship between schedule task id's and extract ids in REST API?
Hope this helps Jeff!
Hey Patrick. The way I'm reading the "more info thread" is that they are querying and getting back a collection of the extracts (i.e. for a given schedule) and then they are running the items in this collection. This will work as well, but it's not as straight forward as tabcmd runschedule.
Have you tried plugging in the schedule id to the task id on the run extract refresh task? I somehow doubt this will actually work, but I will try it if you say it actually works
FYI. I tried plugging in the schedule id, and it didn't work.
I actually have no solution for you, but I am blown away by this idea to trigger a schedule instead of list of extracts (which I am doing now) How do you make sure the extract doesn't run at the time it is scheduled in Tableau server, just when it is triggered? Do you disable it once it runs until next day/week/month? Please tell me more details.
We query posgresql to check the status of the extract, maybe there is something in workgroup db to indicate if the schedule run successfully?
Hello Iwona. Many of our Tableau defined schedules are in disabled status which doesn't translate into they don't run at all, but rather they are not time triggered by Tableau. Instead they are triggered by our external Enterprise scheduler via tabcmd runschedule. Does this help?
Yes, this is very useful to me. Thank you.