I know the majority of folks that read this blog find it through a Google search when troubleshooting a problem and that’s great. We are so happy this resource has been helpful in that way.
Small sample sizes can make fools of us all. You see them hinder analysis all over the place.
For example…
A small sample size of votes leads to prematurely declaring the winner of a political race.
Summary tiles are a great way to quickly communicate a few meaningful measures to your end users in a dashboard. Adding indicator arrows and allowing the colors of the summary tile to change can make them even more impactful.
I was recently working with a client when we hit a roadblock. We came across a situation where we needed to create a multi-row formula and Tableau Desktop is not equipped to do that. Let me walk you through the situation.
LISTAGG is a powerful SQL command to denormalize rows data.
But, what if you don’t have access to SQL or just need a quick way to accomplish this?
If you are coming to Tableau from Excel you are probably familiar with nested if statements. Nested IF statements occur when you have multiple criteria that need to be satisfied to return a certain output. Tableau’s if statements are a little different than other tools.
If you use Tableau and work for a public facing agency, it’s likely you need to create some content that is available for public consumption. In many circumstances, it’s unlawful to display data for sample sizes below a certain headcount.
I was recently faced with a challenge when working for a client. We needed a simple way to provide row-level permissions to hundreds of Tableau Server users for 4 million+ rows of data. The data took place over 300+ sites. Some sites might only have a handful of users that needed access to view while others might have 40.
Tableau is a great data visualization tool that has some data manipulation capabilities. To get the most out of Tableau, it's helpful to have some SQL skills to prepare data. Join us for the 30-minute recording of our recent webinar below to learn how SQL can improve your Tableau experience!
When teaching, I often get asked some variation of the question, “How many rows of data can Tableau handle?”. It’s a well-intended question but it’s incomplete. Tableau technically doesn’t have a row count limitation, but row count is one of the factors that can impact performance.
You probably know that you can only set one number format per field in Tableau. That means that if you create a dynamic measure driven by a parameter (check out this blog post for details) you have to choose a number format. You could choose percent, decimal or currency, but you can’t get the format to swap.
Tableau is a fantastic tool because of its flexibility, but it takes some time to master. Nowhere is this more evident than date calculations. Many of our most read blog posts deal with topics like comparing Month to Date vs. Previous Month to Date.
I teach classes on visual best practices so I know that it’s a bad idea to include more than 5-7 colors in a single visual display. Our short-term memory generally only allows us to keep track of up to 7 variables at a time. Ever had someone tell you their phone number only to immediately forget what they said or mix it up?
If you’ve been reading the OneNumber blog for a while, you likely saw a post last year about using the Set Action feature to create asymmetric drill downs.
I’ve gotten asked by multiple students if it’s possible to create a currency formatted field where the unit at the end of the number can be a K or M depending on the size of the value. Let’s imagine we are working with a chart like this…
One of the exercises I’ve been facilitating in my Tableau classes lately is asking students, “What is something of personal interest you’d like to visualize?”. That open-ended question leads to interesting ideas around entertainment, sports and finances to name a few common themes.