"Sends a message to the Tableau logging facility. The log output appears in a dedicated pane in the simulator."
Q: what about in Desktop?
I couldn't figure out where the logs go on the Desktop app, but you can try tableau.abortWithError(). It'll stop the operation, but at least you can output some useful debug info.
Thanks.That is a good suggestion. We can build up a string with debug messages and then display it using abortWithError()
But we really do need a way go also get the debug messages.
You can find the relevant logs in
Documents/My Tableau Repository/Logs
In there, look at log.txt if the error occurred in the UI phase and tabprotosrv.txt if the error occurred in the data gathering phase.
Indeed they are there. Thanks Daniel.
When I first load the URL into Tableau, a message appears stating that the URL points to a website, not a web data connector. It does let me login, though, and gets me to the date range selector, where the "not a WDC" message disappears. At that point, when I click the button to retrieve data,
The table "[TableauTemp].[webdata-direct.1so30rd1780zgp12jhg2h1f455xq]" does not exist.
Can someone help me?
happening to me as well
any WDC, 9.2.7 Windows Desktop
behind firewall, no local admin
Max @ Tableau Support was able to troubleshoot this for me, and create a workaround.
on our corporate network, the following JS files were not being served up properly.
by replacing them with local references (possible if you are hosting or developing your own WDCs) the issue was resolved.