Tableau utilizes a Get request from Tableau to the browser. The maximum length that most browsers will accept in a get request is 2048 bytes.
For instance - IE:
And on Chrome from Google dev forum:
Again 2048 and this is a standard for Web.
Absolutely not helpful and inaccurate.
The microsoft link you sent me was for IE8 and hasn't been updated in six years.
The google link you sent me was for Google Charts, not for Chrome itself.
If you google 'maximum query parameter length' the first hit is a stack overflow page clearly indicating that different browsers can support much, much larger query parameters.
I am in complete control of the environment that I need the GET to arrive at, and can set maximum URL limits on that end as necessary. For example, if I hop into server.xml in my Apache implementation, I can set maxHttpHeaderSize to whatever value I want and blast away. I can direct my users who will be using this feature to set their default browser to whatever I want. I have successfully sent hardcoded query parameters far exceeding 2084 characters using Chrome and Safari as testbeds.
I don't care about the web standard, because all of my work is going on behind our firewalls. In order to get there, however, I need the tool to populate a URL that may include over 2084 characters, something which a great many browsers support, and can be configured for acceptance on my target servers.
1 of 1 people found this helpful
I am not sure this type of reply is going to get you far. You might try a different approach--and you can easily contact Tableau Support rather than posting an insulting reply on a forum.
Patrick is a Tableau employee, and is graciously volunteering his time (this is not part of his job) to try and help you. He pretty clearly states that the links he provided indicate a Web standard, and not a direct response to your question.
You are probably correct. I have a support case open, and Patrick closed it and responded here. My case was already escalated once to that level. It is a little bit frustrating to have two layers of support give me an answer that:
1) Is demonstrated as false by the most primitive Google search.
It might be one thing if I'd been told that the tool just won't support that at this time, but instead, I was told that it was impossible even though it isn't, and given references to alternatives that do not share any overlap with my problem. I'm getting around to the fact that the existing build of Tableau cannot generate outbound GETS with long query strings, but perhaps a POST option should be considered for their next build. I imagine there are plenty of people that would like to give their user the ability to select a bunch of data points and send that information to other services behind the firewall where the limitations imposed by specific browsers or Google Chart APIs are not of concern.
I've got a *beautiful* visualization of data that will really help some people out, and I am going to have to go to them and tell them to only grab 150 points per transaction, remember which points they grabbed from the map and *don't* grab them again, then merge the results together after the fact, because the tools that I have can't go the last inch.
Hi Brian -
IE's character limit (in the "open" window) is indeed 2083 - The article Patrick referred you to appear to be the most recent documentation that Microsoft has on the subject. Is it old? Yep – but it is correct.
Patrick's reference to using POST instead of GET assumes your users will be leveraging Tableau Server to get "out" to somewhere else. If users are not consuming vizzes in the browser, then you can't leverage the JS API to POST. Most folks constructing "large-ish" query strings aren't doing so for users in Desktop/Reader - they do it in Server for larger communities of users, where the JS API is a viable alternative. Your scenario is an edge case.
From what I'm seeing, we cut off query strings somewhere slightly north of 2K characters - probably keeping in mind the least able browser (IE) in this regard (or the fact that until recently we used wininet for our http work) -- but that's guesswork on my part.
I'd suggest that you make a feature request in the ideas forum - That's where the product team goes to see what features they may want to think about based on how the larger community votes things up or down.
The company I am working for is running into this same issue on Tableau v8.2.3 using IE v8 and Chrome v42.0.2311.90 m. May I please ask if an example could be provided using the JS API to Post? The report is being consumed internally via a Tableau Dashboard.