You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A one line description of the request. Skip this if the title is already a good summary.
Want to be able to determine what datasources or workbooks are associated with a schedule.
Request Type
If you know, say which of these types your request is in the title, and follow the suggestions for that type when writing your description.
Type 1: support a REST API:
If it is functionality that already exists in the REST API, example API calls are the clearest way to explain your request.
This functionality does exist within the API: https://help.tableau.com/current/api/rest_api/en-us/REST/rest_api_ref_jobs_tasks_and_schedules.htm#list_extract_refresh_tasks1
There are no functions to retrieve this information: https://github.com/tableau/server-client-python/blob/master/tableauserverclient/server/endpoint/schedules_endpoint.py
Description
A clear and concise description of what the feature request is. If you think that the value of this feature might not be obvious, include information like how often it is needed, amount of work saved, etc. If your feature request is related to a file or server in a specific state, describe the starting state when the feature can be used, and the end state after using it. If it involves modifying files, an example file may be helpful.
We need to be able to confirm that all of our workbooks and datasources are properly associated with the correct schedules.
The text was updated successfully, but these errors were encountered:
Tableau Support: https://help.salesforce.com/s/case-view?caseId=500Hx00000kv75VIAQ
Summary
A one line description of the request. Skip this if the title is already a good summary.
Request Type
If you know, say which of these types your request is in the title, and follow the suggestions for that type when writing your description.
Type 1: support a REST API:
If it is functionality that already exists in the REST API, example API calls are the clearest way to explain your request.
Description
A clear and concise description of what the feature request is. If you think that the value of this feature might not be obvious, include information like how often it is needed, amount of work saved, etc. If your feature request is related to a file or server in a specific state, describe the starting state when the feature can be used, and the end state after using it. If it involves modifying files, an example file may be helpful.

The text was updated successfully, but these errors were encountered: