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.
Modifying this idea from another post to keep the topic fresh (I hope previous posters won’t mind!).
Alteryx has just released version 10.6. Making Alteryx compatible with older versions comes up on the Community a lot when answering questions and a user doesn’t have the latest version of the designer. The below serves as a guide to ensure your workflow versions correspond to the designer release you have installed.
If you get an error message that looks like this one:
This means the workflow you are attempting to open was created on a version of Alteryx that is more current than the one you're using. Alteryx is forward compatible, meaning if you developed a workflow in version 10.5 for example, it will run in version 10.6. However, Alteryx is not backward compatible. A workflow developed in version 10.6 will not run in version 10.5.
You have a couple of options at this point. You can download and install the most current version of Alteryx (availablehere). Alternatively, you can change the versioning of your workflow to be compatible with your current version.
There are various different file types Alteryx uses:
Standard Workflow file
Macro Workflow (all types)
Analytic App (wz stands for wizard I believe)
The top three are all basically the same format – they are the XML configuration of the workflow. You can view this within Alteryx Designer in the XML View (Options >> User Settings >> Edit User Settings >> Advanced >> Display XML in Properties Window). The first section of the XML looks like:
In Windows Explorer, navigate to where you've saved the file. Right mouse click and select 'Edit with Notepad' option.
Look for ymdVer = "XX.X" and change the version to your version. Afterwards, save the file.
The AlteryxDocument node is the same for Workflows, Macros and Analytic Apps. The yxmdVer attribute is the part of the file which tells Alteryx which version this came from. If you want this file to be able to be opened by an older version you can change the number. The table below gives the version number you need for different Alteryx versions:
So what are the risks? Alteryx doesn’t guarantee the serialized tool format and configuration will be consistent from version to version– though it normally is. The universe of tools that exist is continually growing. If Alteryx can’t find the tool the designer will add an unknown tool:
This can generally be resolved by finding the missing tool and replace the unknown with the known. If the unknown tool happens to be macro, use the same process to change the version for the .yxmc XML. After you save it, you can replace your macro.
What about packages? These are actually just zip files with a .yxzp extension. If you change the extension to .zip you can take a look inside. It’s just a case of updating the files inside the zip and then saving renaming it back to yxzp.