There is an error in the syntax of your query.
What is your query?
Please see below query from generate by Tableau for pulled data from FileMaker tables.
SELECT CAST("sample"."class" AS VARCHAR(100)) AS "class",
"sample"."id" AS "id",
CAST("sample"."name" AS VARCHAR(100)) AS "name"
Also i have attached screen shots the same .
Please help on this .
Thanks a lot,
Error1.png 69.1 K
You need to provide details on your filemaker database too. Do you have a table called sample? and fields called ID and name?
Are you familiar with what the SQL query means? EG why is it using the CAST() function?
If you are not familiar with these things it will be difficult to teach you using an outside tool like tableau.
What's best is to write simple queries, like:
SELECT field FROM table LIMIT 1000
And see if those return results. Then work your way up to the complexity that you need.
Yes Mike .
Tables is "sample"
Fields are id,name,class
I am not familier with SQL queries that CAST() function is generated by tableau also fully query with tableau only .
I done only ODBC connectivity with Tableau.
As you mentioned i have ran the query in custom sql but that also getting same error.
Thanks for information .
i have used an older version of Tableau with FileMaker 12- as those where the versions at use on the client's site. We had some success; however utilimately we found it much faster/ better to use ESS and push the tables to MySQL and remap your FM table occurrences to use the External Source.
tableau was built for crazy large datasets and the FM ODBC client doesn't offer as robust support for SQL as MySQL offers.
the pros and cons of an ESS based solution is another conversation, but it's something that works well as long as you are careful in your coding. Certainly some styles/ solutions work better than others; but we find we get much more out of Tableau using native MySQL connected to FileMaker than FileMaker by itself...
i'm not saying it can't be done, but the struggles we had with ODBC into Tableau where much more time consuming than the issues we had with moving our FM solution to use ESS.
Thanks for your valuable Information.
Thanks a lot.