Bora Beran can probably address your concerns.
You can also omit the parameter altogether. Hopefully, you've also looked at this:
Thanks not sure I understand your answer. The stored procedure requies input parameters so not sure how it can be omitted in this case unless you are talking in general or suggesting I hard code
I am simply stating that a parameter is NOT required to connect to a Stored Proc in Tableau. Its not a necessary component. We have a couple of stored procs with no parameters being passed, and we have no issues connecting to them. When I connect to these, I simply choose the Stored Proc from the list, and skip the "Define Parameters" option. Viola, it works great.
This is something that is not clear in the documentation. I'd love to see more robust documentation.
I originally thought a parameter was required, as well--but upon testing, no parameter is required to connect to a Stored Proc in Tableau.
2. True. They are static.
3. While not optimal, you might be able to be able to accomplish this in Server by calling the report in question with the parameter value included on the URL: http://server/views/myWorkbook/myViz?Parameter=SomeValue
To answer your third question, you can achieve this with parameters since parameter have a display value separate from the value that is passed to the procedure. In the screenshot below, John Doe and Jane Doe is what users would see in the drop down while the IDs 123, 456 is what would be passed to the stored procedure.
You have specified about input parameters.
I have a query on that.
My SP takes 2 input parameters: Year and Country
In year: we will have years starting from 2000 to current year.
For country: All countries in Americas
I have given all the values for the year and country through parameter list. But a user is not able to choose values like 2000, 2013 as he wishes. I couldn't establish multi-select value in each filter.
Please let me know if you have come across such scenarios.
I am stuck here.
Any answers would be of great help.
Tableau currently doesnt offer multi select in Parameters. User can be able to select a single value in parameter and pass it to the stored procedure.
Unfortunately we currently don't support multi-select with parameters. Parameters are literals passed 'as is' unlike quick filters that are converted to where clauses. Given that in a future release this scenario could be supported via parameters only if multiple selections were converted to a single delimited string e.g. comma separated values (2010, 2011, 2013) which then needs to be processed on the receiving end in this case the stored procedure ( to break into its parts as - 2010 2011 2013). Please vote on the ideas forum and mention your interest in multi-select parameters with the specific use case of stored procedures.
Thank you Bora for your immediate response. Is there any other workaround for this?
I have the logic's built in SP. If I am able to pass the parameters as we do in any other front end application, then I could reuse the logic's built in the SP for multiple dashboards.
Thanks in advance.
Thank you Vishwanath for your immediate response.
Please let me know if there is any other work around.
I don't believe there is any really great workaround for this. Nothing I've seen, anyway.
If you have a dashboard published on Tableau Server, there is a workaround that relies on URL Actions.
You will need two sheets or dashboards one of which will serve as source where the user makes the selection and the other will work as destination.
In this case my Tableau Parameter is called Parameter 1. If you check the box "Allow Multiple Values" it will pass the values of Region to Parameter1 as delimited text for the selections made by user. If you select "Run Action On" = Select then user can select multiple options from the viz, that opens the other workbook (destination workbook that runs the stored procedure) in a browser window and passes the selections in the URL in the form
(%20 is the encoded representation of space since it is Parameter 1.)
Second sheet/dashboard will read the values of parameter from the URL and pass it to stored procedure.
Make sure you make the parameter a string since in multi-select due to the delimiter, they will need to become strings even if they are numbers in single select case. E.g. pass to stored procedure as '1,2,3,4' since passed as a number 1,2,3,4 would fail.
I hope this helps.
Awesome, Bora. This sounds great and it has given me some motivation!
Thank you so much!
I will try it out and get back to you in case of any clarification.