Currently, ownership changes work fine only between admins. If you are trying to change ownership of a workbook to a non-admin on the server, it gives an error.
Earlier when I contacted tableau support on this, I was informed that this was a known issue with the current version of tableau server and is likely to be fixed in version 9.0.
I am a system admin and the workbook owner itself a system admin and both cant change the owner to any other user including system admins. This issue with one workbook alone.
Same here. I am a system admin replacing a system admin. I have successfully changed ownership on most projects, data sources, and workbooks, but some fail.
The currently understood issue is best described like this:
When trying to change owner of the workbook on Tableau Server, if that workbook includes external data files or uses a published data source, a yellow error message occurs at the top of the screen:
Could not change the owner of any of the selected workbooks to '<USER>'.
The ownership of 1 workbook was not changed. View details
Clicking "View Details" displays a white alert in the center of the interface:
The ownership of 1 workbook was not changed.
An error occurred while changing ownership of workbook '[NAME]'
The above errors do not occur in beta releases of 9.
Answers my questions. Thanks Rick.
Any intel on a workaround or solution for 8.x? We are seeing this on Tableau Server Version 8.3.1 (8300.14.1212.0958) 64-bit
I don't anticipate an immediate upgrade to 9.0, and would like to be able to create and communicate an effective security model, which includes allowing users to effectively transfer ownership, when necessary.
I suppose the obvious (and rather poor) workaround would be to download the workbook and republish?
Hi, Zach. I am not sure if the fix is portable to the 8 line.
The best way to pursue this question is with a support case. What I would do is open a case, reference this thread, and ask that we find out if a backport to the 8 line is possible.
Please include information about your use case, impact, and urgency. If backporting is possible, we use that information to make decisions about feasibility and prioritization.