The Product Idea boards have gotten an update to better integrate them within our Product team's idea cycle! However this update does have a few unique behaviors, if you have any questions about them check out our FAQ.

Alteryx Designer Desktop Ideas

Share your Designer Desktop product ideas - we're listening!
Submitting an Idea?

Be sure to review our Idea Submission Guidelines for more information!

Submission Guidelines

save as / open as Version

When saving an alteryx module (yxmd, yxmc, yxwz, yxzp), can we have a simple "SAVE AS" function that allows us to choose the version number?  Conversely, could we open a newer version module with a warning message rather than an error?

 

In either case there would be the logical CAVEAT that certain functions or features may not be compatible with the save/open function.

 

Thanks,

Mark

14 Comments
Tomasz
6 - Meteoroid

Great Idea Mark!

I would also add to that - ability to upload downgraded workflow to older server (from higher version of Alteryx Designer).

 

Best Regards Mark,

Tom

The_Data_Loop
8 - Asteroid

update?

Okutof3
7 - Meteor

https://help.alteryx.com/current/product-activation-and-licensing/version-support-policy

With the release of 11.7, a user may convert workflows created in a newer version of Alteryx Designer for use in an older version of Alteryx Designer. In this 'downgrade' scenario, a dialog appears asking the user to confirm or cancel the conversion process. Conversions performed in this manner are not fully tested for compatibility.

 

Designer is different from 2019.3 and 2018.4 depending on the member. Alteryx Server is 2018.4.

yxmd created in Designer 2019.3 fails when trying to save to Alteryx Server.

Even if I rewrite the version to 2018.3 in the editor, when I open it in Designer 2019.3 and try to save it to Alteryx Server, it fails.

We strongly hope to provide the'downgrade'scenario at the above URL.

KylieF
Alteryx Community Team
Alteryx Community Team
Status changed to: Not Planned

Thank you for your feedback!

 

We were able to include the caveat for certain functions when moving workflows between versions back in 11.5. However, our engineers have reviewed the request for the capability to save as a specific version, and at this time we're unable include that function on the near future roadmap. Though this idea may be returned to the Under Review status should we be able to revisit the capability in the future.