1 of 1 people found this helpful
The error message "no such column" can occur when information about a data connection becomes de-synchronized between a database and a data extract. Republishing the extract can, in some instances, correct the issue. Please test rebuilding the extract in Tableau Desktop, republishing, and see if the issue persists. If it does we should get this one filed with our support team so they can investigate. If you can provide them a packaged workbook with the data extract included they can attempt to reproduce the issue in-house.
Hope this helps.
Many thanks for your response
It certainly sounds plausible that the extract became de-synchronised (I had thought broken )
As a first step I'll do as you suggest and rebuild the extract in Desktop and republish to Server.
Fingers crossed that corrects the issue, otherwise as you suggest I'll contact support.
Have you got a solution for this?
I am also facing the same issue, I was using Set in my workbook, earlier it was working fine but as I upgraded the server to 9.3.3 I am also facing the same issue.
The workbook works fine in Desktop but as I publish it on server it does not visualize anything but gives the error:-
No such column [sqlproxy.16m675j0nnqu0z13r9jbb03bv9j6].[Set 1].2016-06-30 08:28:57.648, (V3TYRgPr8-AAlQbQgAAAIa,0,1)
Lindy, if you have any solution for this please suggest as I have tried republishing workbook, recreating extract but the issue remains same.
Sorry to hear you have the same problem.
I haven't got around to it yet, but I plan on following Lindy's advice to remake the extract and republish - my suspicion is that something somehow has become corrupted.
And by replacing, I hope to remove the problem.
I will post back on results, but dont wait on me
Re-building the extract should have resolved it based on my research. Please file a case with our support team so they can investigate. If you can provide them a packaged workbook with the data extract included they can attempt to reproduce the issue in-house - that helps speed the investigation along.
Hmm...maybe my server upgrade will be 9.3.1 instead of 9.3.3...
Just take extra care Toby... I don't think its connected to the upgrade (I was amending the extract) but you have been warned
FYI - Tableau Public has had an upgrade... not sure if you use it.