community
cancel
Showing results for 
Search instead for 
Did you mean: 

Alteryx Designer Knowledge Base

Definitive answers from Designer experts.

Upgrading versions 9.5 to 10 - Understanding Compatibility

Creative Director
Creative Director
Created on

With the release of 10.0, people are naturally interested in compatibility with workflows they have developed in 9.5. Additionally, many users will be in a “mixed version” environment as their company transitions to 10.0 and are interested in what options are available to them.

 

Applications developed in 9.5 can certainly be opened and run in 10.0. We perform a lot of testing and technical work to ensure that Forwards Compatibility is fully functional. Anything that was built in 9.5 should continue to work in 10.0.

 

Undoubtedly, the recommendation is to perform the 10.0 upgrade across the organization when all users are ready for the change. This eliminates any issues with “backward compatibility” and makes it easier and seamless to share applications - workflows, macros, etc.

 

If you do find yourself operating in a mixed environment, there are some things to be aware of:

 

  1. A 9.5 app that is opened in 10.0, then saved in 10.0, will no longer be accessible via 9.5
  2. If you publish apps to a server, you will want to make sure that the server version is compatible with the apps you will be publishing. If you have 9.5 apps then you can leverage both a 9.5 server, as well as a 10.0 server. However, if you’re developing in 10.0 then the server will also need to be 10.0
  3. If you need to support both environments for a period of time, it is possible to install two versions of Alteryx on a single machine. Admin and Non-Admin versions can be installed side-by-side. (e.g. If a user has the Admin version of 9.5, they can install the Non-Admin version of 10.0 and switch between them.) Recognize that if you publish apps to the server, you will need to be running the Admin version of the same version as what is running on the server.
Comments
Asteroid
Asteroid

Thanks, @TaraM! I needed this post today as we try to manage dual-version machines during our enterprise-wide upgrade to 2018.1.