This comment is coming a bit late, but I was wondering how you deal with automating the removal of users that own projects or collections? Those content types still stop the removal of users, but wasn't included in the video. As far as my research has taken me, there is no way to transfer ownership of projects and can't find anyone asking about collections. Your video was great and I really appreciate any response to my questions.
Fantastic. I'm a beginner in using the Tableau REST API and I learned a lot from your videos. It's the time I searched for how to use python connect to metadata API that leads me here. Keep going!
Where can I find this Python file? The article in the link shows a user input for old and new owner. The video shows it automagically changing the owner and removing the user. I have a large server, and it wouldn't be prudent to go through all the users one by one.
Hi Elliot , Thanks for awesome tutorial! I have one quick question , when I am using this function & pass only 3 parameters , it does not work as expected connection.update_data_source_connection( datasource_id, connection_id, server_address=None, port=None, connection_username=None, connection_password=None, embed_password_flag=None, ) In our use case we only need to change the server name , as one database connection would be rename connection.update_data_source_connection( datasource_id, connection_id, server_address= 'new_server_name') the api call works , name changes to 'new_server_name' but connection does not work until & unless all arguments are passed i.e 'user name etc ..." , is there any way it will work without credential parameters , thanks in advance!
This gets very messy, as I believe it requires downloading the datasource, extracting the .tds file (XML), manually updating the server connection details, re-zipping the .tds file, and then publishing. And if I remember correctly, when I experimented with this I needed to manually specify credentials when republishing. In the end, I never went to production with that use case because it was simply not reliable enough. Too many weird edge cases would get in the way of clean, seamless migrations. You may find some use in Tableau's Document API (if it still exists) or in their Content Migration Tool (CMT).
