1 of 1 people found this helpful
It's hard to determine without seeing the workbook. If you place the 'result' field on the Rows shelf after 'last_name' what values appear for the 'result'? If you do not see "Success", then the filter is behaving properly.
If "Success" does appear within the list of results, could you provide a packaged workbook that displays this problem? This way folks will have an ability to study how things are configured and provide a more targeted response.
I tried to place `result` on Rows shelf and it was displayed on the view. Workbook in attachment if it helps.
P.S. Can it be a technical problem connected with using Tableau Desktop on VirtualBox-based Windows XP machine on Mac?
UniqueDaysLoggedIn.twbx.zip 1.3 MB
Thank you, Andi, for your help!
Looks like everything is OK when using an extract.
I can see it when I open your packaged workbook.
Is it correct that you have the "zero rows, empty view"
when you connect _live_ to MySQL database?
What is the character set / collation of your table?
Suspect it is something like utf8 / utf8_general_ci.
Then you're "lucky" catching a buggy behaviour
of MySQL ODBC 3.51 driver with utf8 datasets.
I got the same (bad) experience trying to marry
Tableau with Infobright & Cyrillic language data.
No luck so far.
Hopefully waiting for the next Tableau release,
which could use MySQL ODBC 5.x driver instead.
You're completely right.
- When I tried to connect to data with live connection the view was erased.
- All tables in my database are ut8_general_ci
- As for driver I firstly installed original driver from MySQL web site. And could NOT connect to database at all. After that I asked support for help and they advised me to download and install driver from http://www.tableausoftware.com/support/drivers . After installing the driver I started to connect to database. At the moment I have two MySQL drivers installed (see screenshot)
So, you mean that there are no any chances to get working Tableau with MySQL UTF8 tables at the present time, right?
1 of 1 people found this helpful
For "native" MySQL connection Tableau is using 32-bit ODBC 3.51 driver.
And I don't think they will change it to 5.x version soon :-(
So your current combination (Tableau + MySQL ODBC 3.51 + utf8) doesn't work.
Hint: if you're using MyISAM or InnoDB engine as a backend,
you may try to set your database tables to use utf8_bin collation.
This could help with proper filtering, because Tableau would generate
binary sequences instead of characters in their SQL statements.
Please try to set your tables to utf8_bin collation. Tell me if it helps.
(You may change only several char / varchar / text fields if necessary).
Thanks, Yuri, for helping me! I'm not sure I'll be able to use your advice in the nearest future because MySQL database mentioned in the topic is a backend for production system with 100+ users. So thus modifications surely require some preparations to be done not to affect working system. But I'll think of it to manage the problem.
Why are you so sure about not switching to 5.* driver version in short period?
I'm thinking of building an ETL system based on MySQL InnoDB database. But your answers let me change my decision. May be PostgreSQL would be better? Do you have any negative experience using Tableau with PostgreSQL databases?
To share my doubt about Tableau to use 5.x driver, please look at this thread:
http://community.tableau.com/thread/114038 -- No mo' news so far.
If you're considering Tableau anyway, you may re-consider your analytic database of choice.
PostgreSQL is one of many, definitely a good candidate if you insist on using open source
(and have a great DBA in place :-).
If you choose to stay with MySQL variant for analytics, Infobright or InfiniDB are worth to mention.
But this would lead you to either drop Tableau, or use (periodic) extracts as a last resort.
Think it is enough for the discussion here.
You may reach me by email anyway.