Thank you, I will explore this route, otherwise I will just stick to a batch file with tabcmd.
2 of 2 people found this helpful
Hey Alex Braun,
Tableau 10.5 beta includes the ability to filter views when exporting the image via the REST API now. It works similarly to the way it works from tabcmd, but you have to preprend vf_ to your field name so that we can differentiate between url parameters meant for the rest api, and ones meant for the underlying view.
This is a beta, so please let us know if you have any questions or run into any issues.
Is there any documentation available on this new feature?
All the best
Great to know, thanks Russel!
Are there any Tableau Conference sessions which go through new API features?
I'm working with our docs people to get it in there. I'm waiting to hear back on exactly when it'll get updated. I should mention that we also discovered a bug that caused filtering during pdf export to not work. That'll get fixed in the next maintenance releases, and TSC is being updated to include that ability as soon as this PR is merged into development: Implement view filters on the populate* request options by RussTheAerialist · Pull Request #260 · tableau/server-client-…
Russell Hay That's great news. Also, as a request, could you please make the Query View API methods support POST requests as well? Having it only work with GET poses a serious limit to the request parameters which makes its usefulness very limited.
I'll put in a feature request for being able to do that. What do you envision sending in the body of the POST in your ideal scenario?
For the body, I imagine that it will be composed of at most two parts:
fieldName: [value1, ... valuen]
// Image Resolution, or PDF Export options, etc, this can remain as part of the URI though.
And that the request URI will be pretty much the same as what is documented for the GET request version as of today.
It's pretty simple.
In the end, what I'm most concerned about is the ability to send in n field parameters with n values of various lengths. If for example, a field parameter has the ability to accept over 100 different values, each a string of unknown length, and a request is sent in with 80 values for that field parameter, its likely that it will exceed the character limit for a GET request.
That makes sense. I'll get that feature request put in to get it added to our dev schedule.
Hi Russell Hay,
I'm seeing this feature on the API Docs now, but it doesn't say how or if I'm allowed to send in multiple field values to a field name.
Can I do this by comma separation?