Version 1.38 is a feature release for Power Tools: Deployment application
This version has been rebranded for Tableau. The language here reflects this update. For example, “InterWorks Power Tools Deployment” refers to a legacy version, while “Tableau Power Tools Deployment” refers to this new, rebranded version.
This also includes important installer changes and upgrade considerations that you can find detailed below.
- Install Tableau Power Tools Deployment. Do not uninstall your current Interworks version. It needs to be in place for settings to be imported.
- On first run, an automatic upgrade process runs in the background, and attempts to find the previous InterWorks Power Tools Deployment installation. If one is found, then all settings are automatically imported. If an installation is detected but no previous install directory can be found, then you will be is prompted to provide the installation directory.
- Once Tableau Power Tools Deployment installation is complete and you have confirmed it is working as expected, uninstall the InterWorks Power Tools Deployment.
- Beta support for Tableau 2019.2. Minimum support is now Tableau 10.3.
- Rebranding for Tableau.
- Changed installer to reflect Tableau ownership. This means the Tableau-branded version is installed side-by-side with the legacy InterWorks product. Setup will attempt to automatically import the settings and load the settings and recent workbook sources from the legacy install. If the automatic import is not able to locate the legacy install, you will be able to manually select the legacy install directory for settings import and complete the installation.
- Fixed an issue where archiving to a permission-locked project could cause deployment errors.
- Fixed various problems related to deployments when users of the same username but different domains exist.
- Fixed an issue where “Open in Tableau Server” links would not work correctly when using Tableau Server 2019.1 and above.
- Fixed an error where copying refresh extract schedules would choose the wrong schedule on the destination server.
- Changed deployment concurrency to prevent an issue that could cause duplicate tags to be created in Tableau Server.