1 of 1 people found this helpful
Interesting question. I tend to work with Tableau Public a lot, whose users seemingly at times care much more about the actual presentation of their vizzes (unsurprisingly since they're publishing these to the web to share publicly). So on a personal note, I don't know if Tableau has missed the balance between data and visualization as you've defined them, but I do wish there were more "visualization" to it. Everything you mentioned is something I've struggled with many, many times (layout containers crush me on a near-daily basis).
The good news is we know about these concerns and we're actively working to improve them. If you'd be willing to share an example of some of the if/then/case statements you've written to produce your vizzes, and how you'd like to see it implemented, our teams to do read the forums, and what you'd like may just make it in (if it's not already being worked on).
Daniel, one of the really cool aspects of the Tableau culture is you folks don't have that 'fortress' mentality (think Microsoft).
Everything you mentioned is something I've struggled with many, many times (layout containers crush me on a near-daily basis).
Thanks for sharing this. I obviously share your pain . As to your question about field calculations, I have just finished a viz with a simple example. I'll start with what I wanted to write:
IIF([Parameter].[Primary Segment] = [Measure Names], [Measure Values], NULL)
Instead, I had to write this (with a big assist from Alex!):
It goes on for 72 lines. I am currently revising this so the results will be filtered to > user-defined index number. That statement looks like this:
And then on the Differential page I (the client) wants a filter that to show only attitudes above and below a user-defined index. That statement will look something like this:
This one has more measures, and goes on for 102 lines. It also executes slowly. Each time a different parameter is chosen, I get the 'calculating' warning box. Again all of these calculated fields would be much easier to generate/read/test if we had access to the Measure Values/Names variables.
I attached a workbook for you (or anyone) to look at and see if I am torturing myself needlessly! Is there an easier way to do this? Any suggestions?
Attitudes Study Sample.twbx.zip 252.9 KB
Unfortunately I think what you have is the only way to do what you want (though I'd love to be proven wrong). And you touched on why--you currently can't use 'Measure Names' or 'Measure Values' in calculated fields.
I'll forward this along as an idea for us to change. Thanks for sharing!