This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
At present, Alteryx allows for users to run 2 versions of Alteryx at once - one installed using the "Admin Installer" and one via the "non-admin installer"
However, in corporate environments, only the Admin Installer can be used (all installers are repackaged for corporate environment / endpoint management)
This leads to a situation were we cannot run two or more different versions of Alteryx on one machine (like you can with Visual Studio or other platforms). This also prevents us from participating in the BETA program because the BETA version would overwrite the users's current version. Finally - this also makes version upgrades more risky since we cannot run the new version in parallel for a period to evaluate and identify any issues.
Request: Please can you change the installer for Alteryx to default to parallel install per version - so that a user can run 2019.1; 2019.2; and 2019.2 BETA on one machine in a way that is fully isolated (i.e. no shared components - have to be able to uninstall one instance cleanly and leave the others in a fully functional state).
When upgrading to 2019.1, the content of my Python tool was deleted. Although this may be a bug in the 2019.1 version, or just a bug in the upgrade process. Either way, it is problematic that details of a canvas would be deleted at all.
My guess is if the content of the Python Tool could be reliably stored in the canvas XML this issue could potentially be resolved.
As a Server 2018.4 admin, I need granular control of Server/Gallery defaults including:
1.) Pre-allocate AD users and groups (under Permissions) to specific Studios
2.) Control defaults for scheduling/priority/worker settings on Users
3.) Control defaults for workflow download/no-download at Gallery or Studio level
4.) Control defaults for notifications. Currently I have to check each notification template individually to disable it. Change template tile colors (or whatever) to provide visual queue as to which are enabled or disabled.
Above all, the tiled approach to displaying users, groups, studios simply isn't scalable. A simple data grid type display will allow higher information density allowing settings like: sharing, download ability, scheduling, credential type settings (studio default, artisan specified, runtime entered etc) to be easily reviewed. Basic server governance relies on easy visibility (reporting) of settings to ensure consistency...
As a system admin, I need a simple, reliable way to back up the Alteryx Server without shutting it down first. A hot-backup (and restore) utility that includes a consistent copy of MongoDB plus any other server config files would allow me to do this.
I just upgraded to the new Alteryx 8.6 which I'm looking forward to using, however, it is quite frustrating that none of my customized user settings are maintained during the install process. I make a few customizations:
Showing the grid and the XML
Turning off the "module complete" pop-up
My 'panes' where I put them
A few favorite tools in the "Favorites" toolbar
And there are so many other customizations that I don't go near (but might if they were maintained during upgrade), like:
Default temporary path and Logging
Startup page & Distance units
Please implement a way of maintaining these settings!!
The silent install for the census data I not completing successfully. It appears that it can't create folders. When attempting to run the command: DataInstallcmd.exe /s /install all /log "C:\temp\logs\alteryx.txt"
I received an error in the log: Install failed: Directory: C:\Program Files (x86)\Alteryx\DataProducts\ does not exist
I received this error regardless of how I attempted to run this command, as a user with admin permissions, as a user with admin permissions running the command as an administrator, from an elevated command prompt, etc. It was not until I manually created the directory via the following command that the silent install ran successfully.