Sunteți pe pagina 1din 2


1. How to create calculation in Tableau to ‘does not contains’ or exclude some

values of a given column.


CONTAINS([Column Name],’V’),’Yes’,’No’)

This works well to fulfill such requirement

2. To create a fiscal quarter format as 2014 Q 2 within tableau using default

fiscal quarter coming from warehouse.

Left([Fiscal Quarter],4)+ ” “+
left(right(replace([Fiscal Quarter],”-“,””),2),1)+” “+
right([Fiscal Quarter],1)

3. To create a rolling quarter using a date field/ column available

DATETRUNC(‘quarter’,[DEFECT_SUBMIT_DATE])=DATETRUNC(‘quarter’,TODAY()-90)) then ‘Y’
else ‘N’

Best Practices for Tableau development

A very beginning step before you start working on building the visualization based
on available data for you is that make sure what is the purpose you of your
visualization. Also clarify the problem statement that we are trying to solve and
all interactive features required in visualization.

Design of tableau was usability in mind, ease of use interface and powerful
components to create multiplex data visualizations at lightning speed. Below are
some of the questions ask your business users/ End users who are requesting

Who are actual end users of these visualizations?

What are the capabilities they are looking for?
Are there any specific charts/ visuals they like to see and reason why only those
What kind of insights they are looking for in visualizations?
In Process of building visualizations we might use/create variables left and right
without following some best practices and while doing so performance is not
considered. While we perform performance stats on whole workbook to see how fast
charts/visuals are rendering in browser, might come across some facts that lot of
place best practices are not followed.

Here are few points to make workbook performance excellent

Only bring required data for analysis

Remove unused columns
Avoid using “Only relevant values” and more quick filters
Avoid using Custom Sql in extracts( For Initial analysis use custom Sql.. once have
proper understanding of data vs requirements provided for dashboards)
Avoid using parameters in custom SQL
Use of calculated fields carefully – Think about the data types as you
code/calculate the calculations/variable. Number and Boolean > Date > String
calculations when it comes to performance
Limit blended calculations – They require sequentially querying multiple data
sources and can be time-consuming. Where possible, create a view on the database
Marks count should be less – More marks = long rendering time
Use of less size(< 50KB) images in dashboards
Use PNGs instead of JPGs as custom images/shapes