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

Make Server User a System Constant

There is no good way to get server user credentials into a workflow without asking them for it in an App interface.  It would be great if we could have a built in Constant that could be used to silently pass user credentials into a workflow for things like API's or logging user information.

Alteryx Alumni (Retired)
Status changed to: Comments Requested

@StephenR thanks for posting!  I am marking this as Comments Requested and look forward to seeing others in Community who are interested vote this up with stars and comments.  Thanks again.

11 - Bolide

Actually, there is a way. See I used the solution there, and it works great. It is a little tricky, and not as straightforward as a built-in Constant would be, but it does work.


I am voting up this idea to make this easier.

Alteryx Alumni (Retired)
Status changed to: Under Review

Thanks for posting @blyons - marking this idea as under review so we can investigate this internally and will keep this post updated.  Thanks!

9 - Comet

+1 We would like to be able to use the current userID and extract info from the Mongo like email address so we can email results directly to the current user rather than having them input their email address manually.  There are some workarounds to make this available to our users (extract a subset of the User table and have them use the __cloud:UserId textbox), but this has its own issues including the fact that the __cloud:UserId trick doesn't work in a macro that we could package up (i.e. only works if the text box is in an analytic app).

17 - Castor
17 - Castor

+1 and I agree with @mcarrico's points above. This feature would get a lot of use here.

8 - Asteroid
+1 from me as well, I would like a simple way of auto-emailing the results of a workflow to a user without them needing to enter their email address. This would work really well for us here
17 - Castor
17 - Castor

Similar to Tableau - knowing who the user is makes the application able to pass authentication onward; and allows for richer logging and functionality in Analytical Apps

7 - Meteor

 +100 - this is a no-brainer.  Having looking at the hoops to jump through to implement what should surely be out of the box functionality.....

11 - Bolide

+1 Various Connectors inside the workflow/app need the user's credentials. Being able to connect the Server credentials (LDAP etc.) to the workflow/app would be great! Possibly through Interface controls ...


+10 If we run workflow/app through a non-user account, but rather a team/system account with credentials of their own. There's no way to pass this information to the Connectors. The user can't enter them because it would be security violation to give them to the user. We need to use team/system accounts for scheduled processes as a security requirement, so this is needed.


Could Server store all 'types' of credentials, including the current Data Connections and Workflow Credentials types, in one location, and then provide facility to assign them to users/studios as they do today, and expose the credentials to workflows through system constant or Interface control?

7 - Meteor
+10 from me