Join the Alteryx Community’s Maveryx Summer Cup event! Compete, network with others, and earn your gold through a series of challenges from July 24th to August 11th. Learn more about the event here.
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.
community Alteryx IO Alteryx.com
alteryx Community
Search
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Close
Free Trial

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

The field X was renamed conflicting with an existing field name

Status: Accepting Votes Submitted by on ‎10-20-2022 07:21 AM
1 Comment (1 New)

For years, Alteryx would gracefully rename conflicting field names. It would issue a warning and that's it.

 

We recently upgraded from 2019.4 to 2022.1.1.30961 and now an error is produced:

Oops!

The field X was renamed conflicting with an existing field name

 

I searched for "rename" in every release notes version applicable and I do not see this. Is it a bug? Is it a feature?

 

We have an Alteryx server with thousands of workflows built by dozens of users with varying skill levels. This is a tremendous amount of work to go through and fix all the failing workflows.

 

Please help me understand this change because there was seemingly no warning and now we are scrambling.

See more ideas labeled with:
Labels