The need for tableau reports on the web:
Tableau lets people across your organization to communicate and understand the data in a whole new interactive way, at the same time continuing with the existing license and security framework available to you.
A good organizations’ dashboard makes its users understand the information within a glance. It allows even the non-technical users to create interactive and real-time visualizations within minutes. Furthermore, it may also have advantages to grasp the existing security options of the defined web portal.
Many people might not be comfortable in reporting and making correct decisions while accessing the information on a particular website. They might get drifted easily which in turn makes their whole work look less efficient.
Whereas embedding tableau in a particular web portal makes it even more interesting and appealing to the users wanting them to access more data and information for their needs
When offering service to the clients you need to control the overall branding of the product as well as dashboard. Instead of redirecting the users from the actual product to the third party solution i.e tableau server and making them resent, you can embed the tableau report directly into your particular product. The ultimate result is the seamless blend of the underlying technology (which users are unaware of) and the branding of the commodity, as a result of making the whole process more user-friendly.
Embedding dashboard can be achieved by using any of the below methods:
Regardless of any of the above methods you choose to use, you can control the complete embedded view with the help of equally important ‘passed parameters’. We shall now explore into details of all the above three methods as well as subsequent parameters.
You can notice that tags are used to specify or enter certain values. Additionally, tags can also be used to pass parameters such as an initial filter. Below is an example:
As we can see the entry will initially filter the embedded view by restricting to a particular dimension region such as west. The name and site root parameters are the most required parameters while embedding a view under this method.
Using an iframe or image tag
Another approach of embedding the above view is by using an iframe. The embed URL parameter is most required. However, occasionally you can use parameters that control the toolbar and tab options. Additionally, you can add filters to the URL to make it more appealing to the viewers when loaded. The tableau is restricted to the west region dimension and also specifying certain date.
Whether you adopt any of the above methods, you can further pass additional parameters to the complete view.
Tips and Tricks to follow while embedding a dashboard
Let us have a quick glance at some of the tips and tricks to be followed while embedding the dashboard using TABLEAU.
Date field=yyyy-mm-dd hh:mm:ss (optional)
Although there is no limit on a number of parameter values to pass on an embedded view, there might be a URL length restriction imposed by the end user’s browser.
HTTP Protocol does not impose any limit on URL length as you can notice many modern-day browsers can handle URL length up to 80,000 characters, however internet explorer 8 & 9 have a maximum character limit of 2,083 characters only.
Therefore, you should be conscious of keeping URL’s under this limit to assure compatibility. Note that the complete URL length does not mean to definitely include passed parameters and resulting values from it.
When an embedded view is being accessed, the authentication mode available on the tableau server is used to know the user’s identity. To explain, if your server is constructed for local user authentication, then users must log in through a form provided by the embedded view. This may be a tiresome process for the user if he had already authenticated into the web application.
To overcome this situation tableau server gives an option of the single sign-on method where an already authenticated user needs not log in further into an embedded tableau view. He would be in your active directory and SSPI and would be treated as a ‘licensed tableau server user’. However, in all the other situations, the trusted ticket authentication method is used as an alternative to a single sign-on method.
While using a trusted ticket authentication method, the webserver takes all the responsibility of the authenticated users. Much before embedding the view, web server does two POST parameters to the tableau server:
The web server receives unique_id through the form which is further used in the embedded view’s URL, as shown:
<span style="color: #000080;">HTTPS://YOURTABLEAUSERVER.COM/TRUSTED/UNIQUE_ID/T/VIEWS/MYWORKBOOK/MYDASHBOARD?:EMBED=YES</span>
Once if unique_id is issued, it must be reclaimed within 15 seconds from a machine matching the client_ip specified, or else it would become invalid. As soon as the tableau server receives the request that the user has logged in, then a trusted ticket URL is resolved to that of a standard request.
Even before a web server can make a request for trusted ticket authentication, it must first be on the ‘trusted list’ of the tableau server. This can be achieved using tabadmin command where xxx.xxx.xxx.xxx indicates an IP address for every trusted web server.
Tabadmin set wgserver.trusted_hosts “xxx.xxx.xxx.xxx , xxx.xxx.xxx.xxx”.
List Of Tableau Courses:
Free Demo for Corporate & Online Trainings.