We are aware of an issue with the Search bar. Please use Advanced search for the time being while we troubleshoot. Thanks for your patience as we work on improving the community!

Alteryx Designer Ideas

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

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

Submission Guidelines

Make it so that renamed tools show these names in ALL output logs

Roughly, in all versions of Alteryx Designer, you can use the Annotations tab and rename a tool.  This is awesome for execution in designer, because you can then easily search for certain tool names, better document your workflow, and see the custom tool name in the Workflow Results.

However, when log files are generated, either via email, the AlteryxGallery settings, or an AlteryxEngineCMD command, each tool is recorded using only its default name of "ToolId Toolnumber", which is not particularly descriptive and makes these log files harder to parse in the case of an error.

 

Having the custom names show in these log files would go a long way towards improving log readability for enterprise systems, and would be an amazing feature add/fix.  For users who prefer that the default format be shown, this could be considered as a request to ADD renames in addition to the existing format.  EG "Input Data 1" that I have renamed to "Load business Excel File" could be shown in the log as:

 

00:00:0.003 - ToolId 1 - Load business Excel File: 1 record was read from File Finished in 00:00:0.004

10 Comments
JoshKushner
12 - Quasar

This makes complete sense. Would it just require that the code generating the log read a different part of the workbook's XML?

Claje
14 - Magnetar

Obviously I don't have any insight into the logging itself, but I believe so.

 

Roughly, inside the XML there is an "Annotation" section which has a tool name.  This is where any tool renames end up.

 

It looks like all of the output logs use the Node, and the ToolID captured there.

 

Circled the section where I believe tool IDs come from, Highlighted the <Name> valueCircled the section where I believe tool IDs come from, Highlighted the <Name> value

Community_Admin
Alteryx
Alteryx
Status changed to: Inactive
 
Community_Admin
Alteryx
Alteryx

The status of this idea has been changed to 'Inactive'. This status indicates that:

 

1. The idea has not had activity in the form of likes or comments in over a year.

2. The idea has not reached ten likes.

3. The idea is still in the 'New Idea' status. 

 

However, this doesn't mean your idea won't be implemented! The Community can still like and comment on this idea. With enough renewed interest, this idea can be brought back into the 'New Idea' status. 

 

Thank you for contributing to the Alteryx Community and the Alteryx Product Idea Boards!

marcin_p
6 - Meteoroid

KylieF
Alteryx Community Team
Alteryx Community Team
Status changed to: New Idea

This idea is being returned to the New Idea status, as it has reached the required number of likes to be brought to our product teams attention. Please note it may take time for our product team to provide a response. However, we will do our best to insure this idea is updated accordingly.

 

Thank you for posting and contributing to the product idea boards!

 

SriKoka
7 - Meteor

Alteryx has so many intuitive features. I am surprised renamed tool names are not appearing in logs. Alteryx please implement this feature..

KylieF
Alteryx Community Team
Alteryx Community Team
Status changed to: Under Review

Thank you for your feedback!

 

Currently our product team is reviewing the technical requirements and timeline required to potentially implement this idea as there is a concern of breaking backwards compatibility for certain existing use cases. Once they have completed the review we'll update this idea again to reflect if or when we can implement this idea.

idariis
5 - Atom

Are there any updates on this idea? 

Williamkim990
5 - Atom

Hi there Alteryx team. Are there any plans to have this in the next update? Would love to have this for diagnosing my workflows!