Community Spring Cleaning week is here! Join your fellow Maveryx in digging through your old posts and marking comments on them as solved. Learn more 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.

Alteryx Server Ideas

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

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

Submission Guidelines

Data Connection Name Duplication

The gallery shouldn't allow to create data connections with already existing names.

For example, in designer it's difficult to choose which data connection we want to work with if they have the same name, please verify the images in attachment.

5 Comments
CristonS
Alteryx Alumni (Retired)

hi @joanatpsantos thanks for your feedback. I'm curious if this is intended behavior? @JohnPelletier can you weigh in?

JohnPelletier
Alteryx Alumni (Retired)

@joanatpsantos thanks for your interest and feedback. While I think this would be a nice feature to have, we have many other more urgent priorities right now. Maybe we can ask other users how they deal with this issue...will a naming convention help with this?

joanatpsantos
7 - Meteor

@JohnPelletierWe already have a naming convention but if you have 30 or more connections to create you would need to search for each one of them before creating them and in a platform with hundreds of artisans this can take a lot of time. Thanks.

dhovey
7 - Meteor

@joanatpsantos What do you use and/or recommend on naming conventions, please? 

joanatpsantos
7 - Meteor

@dhovey we decided to use the format: Connection type_Protocol_hostname_username