1 of 1 people found this helpful
Did you get this fixed?
I just encountered this issue today with datasources located in a Sharepoint library and on a network drive. Each time I connected to the data source it created a file in the temporary folder on the C: drive even though all the data was retrieved from the source file correctly and available in the vis.
My original URL for the Sharepoint data source looked like this and kept being lost into a temp file:
Howver as soon as I changed it to the following it retained the direct connection to the data:
I was also playing around with the connections for files located on one of our network drives and had a similar problem. It was easily resolved by using the full network path instead of the locally mapped settings.
For example, my drive mapping is something along the lines of Z:\exec\hris\xxxx
But if you change the data connection to reference the full server name (in my case this meant the drive became ausyd01mf610\exec\hris\xxx) it will be retained whenever the dashboard is opened in Desktop.
Thanks very much for the feedback.
At a first try, it seems that version 6.1 will retain the true network path, yet 7.0.2 is not keeping it/ still pushing a localized version.
Any thoughts on this?
Thanks again for sharing your findings!
Message was edited by: Erik Ford The latest is, that 7.0.2 does not necessarily bear challenges to the path as inferred above. What we are finding is that when packaged as a Tableau Packaged Workbook, it always creates a localized version instead of calling on a data source remotely.
A packaged workbook should always be local - that's the point of it being packaged - so that it can be worked with off line or without the access rights normally needed.
Why are you saving it as a tbwx?
Thanks for the response.
The reason for saving as a tbwx is because our account team only has reader. We do not support giving non-analytics team members full tableau access. We want them to read and manipulate the data only.
Hope this helps clarify-