Did you get any workaround on that issue ?
I'm currently facing the same problem.
One of my field is being recognized as 'Double-precision floating-point number' instead of 'Unicode Character String'
Can't figure out how to change it...
There are two reasons that the MySQL connection was not representing your field in way that was suitable for incremental extract refresh. First, when you use a Custom SQL query instead of a direct single-table or multi-table connection, MySQL will not preserve the primary/foreign key information in the query result set that it produces. Second, a BIGINT(20) field is one digit too large to represent as a 64-bit Integer, which is why Tableau is forced to treat it as a floating-point value. The largest BIGINT scale that can be natively supported in 64 bits is BIGINT(19), so please consider using that scale instead, if possible. For those who are curious, the formula is FLOOR(19 / LOG10(2) ) + 1 == 64.
Julien Lafont, your issue sounds different and is a bit puzzling. I suggest that you contact Support (firstname.lastname@example.org) and mention this forum thread. They can work with you to collect logs that demonstrate the problem, and this will help us investigate a possible workaround or a necessary fix for the problem.
I hope this helps,
I am also facing a similar problem . my table have date-time as a calculated field. but it is not recognised in incremental refresh. there is no other integer. What is the solution for using incremental refresh ?
is it possible to add a Row ID which is sequential based on number of rows