Alteryx Designer Desktop Ideas

In a short workflow, this might not be necessary as the information related to each tool is spelled out in the progress windows.  However, in a complicated and lengthy workflow, tracing such msg can be a tedious task. In addition, using a tool with multiple outputs and only one output is selected while the residual outputs may be used to validate the result in the selected output; for example, joint tool where left or right output should be zero, a visual queue could be a quick way to alert operator on any potential problem.  Certainly, a browse tool can be added but in a big workflow, couple with a large data set, it might be a drain to the system resource. What if there is a tool that would activate a visual alert, like a light bulb, based on a preset condition to tell user that something is wrong and perhaps additional work needs to be done to either remedy or to account for the residual data. As in the case of a joint where 100% match is desired, any unmatched row would require an update to the reference list which maybe an additional adhoc process outside the current process. Certainly, an additional steps can be added to first explore the possibility of unmatched data and to update the reference list accordingly.  The workflow would in hold until 100% match is achieve. This would require additional system resource in order to hold; especially with large set of data and lengthy workflow.  If the unmatched situation rarely occurs, just a lightweight visual queue that 'pop' while allow the process either to break or to go through might be a sensible solution.  Just a thought.

In the Configuration section of the Formula tool, the “Output Column” area is resizable.  However, it has a limit that needs to be increased.  Several of the column names I work with are not clearly identifiable with the current sizing constraint.  I do not think the sizing needs to be constrained. 

After the upgrade to Alteryx 2018.4, the publish to tableau server tool no longer has the feature to get the authorization header to make subsequent calls in the workflow.This feature was present in the older versions of the tool i.e Publish to tableau server 1.09,1.08.1 but not in the new version 2.0.0

I think this feature should be present in all the versions of the publish to tableau server tool.

Cheers

Hey Alteryx Devs - 

Simple fix that would keep me in the flow sometimes, is if I could hit F2 and get to a place where I could tweaky tweaky the annotation.  I keep on finding myself hitting F2 and then am annoyed that I have all these extra clicks to annotate meaningfully.  Easy fix and you don't have anything else attached to F2.  

Thanks!

brian

edit:  Had wrench palette, needed pencil palette!

Some Alteryx tools, like Select, update when a field name or data type is changed upstream.  Sometimes it causes an error, but often Alteryx can self-adjust and be OK.  However, other tools such as Union and Summarize, don't recognize the change - they don't self-adjust or throw an error until runtime.  It would be great if these other tools (there must be others besides Union and Summarize) could recognize changes at design time.  Even if they just threw an error, it would be better than current state.

I collaborate with a team using Git. We commit all of our work automatically with the exception of the Alteryx Alias file. It must be moved manually into the repository and then other teammates must move it out of the repository manually into their local folder and overwrite the old file. This is not an enterprise-friendly solution. If we could configure the location of the Alias file in Designer, we could set it to live in the repository. That way, everyone could automatically have the latest file with tracked changes. Please create this functionality. Thank you.

Hi All,

Currently the FUZZY MATCH tool supports only Latin characters. It would be great if this tool could also support other characters, such as Hebrew letters and signs.

Thank You!

Issue: Even though the Send Email event is configured for the After Run Without Errors setting in the Workflow Configuration it still sends an email when the execution of workflow is cancelled. I think only the Before Run event should be allowed to trigger in this case.

App: Alteryx Designer x64
Version: 10.5.9.15014

Workflow Configuration Error

Email Screenshot

Hi there,

Just a quick note on a really small improvement that could be made on the Data Cleansing tool but that could help a lot.

Actually this tool allows us to convert input data with NULLs to either blank or 0 values depending on the datatype.

It would be really appreciated to be able to do the opposite, converting blank or 0 values to NULLs.

One of the common methods for generalization of different types of normal and beta distributions is triangular.

Though Alteryx doesn't have a function for this, even excel doesn't have this but

• SAS (randgen(x, "Triangle", c)) and
• Mathematica (TriangularDistribution[{min,max},c]) like tools include one.

Can we add something like randtriangular(min,mode,max)?

I have my solution attached, but this will ease the flow...

Best

Would it be possible to change the default setting of writing to a tde output to "overwrite file" rather than the "create new file" setting? Writing to a yxdb automatically overwrites the old file, but for some reason we have to manually make that change for writing to a tde output. Can't tell you how many times I run a module and have it error out at the end because it can't create a new file when it's already been run once before!

Thanks!

The Field Summary tool is a very useful addition for quickly creating data dictionaries and analysing data sets. However it ignores Boolean data types and seems to raise a strange Conversion Error about 'DATETIMEDIFF1: "" is not a valid DateTime' - with no indication it doesn't like Boolean field types. (Note I'm guessing this error is about the Boolean data types as there's no other indication of an issue and actual DateTime fields are making it through the tool problem free.)

Using the Field Summary tool will actually give the wrong message about the contents of files with many fields as it just ignores those of a data type it doesn't like.

The only way to get a view on all fields in the table is using the Field Info tool, which is also very useful, however it should be unnecessary to 'left join' (in the SQL sense) between Field Info and Field Summary to get a reliable overview of the file being analysed.

Therefore can the Field Summary tool be altered to at least acknowledge the existence of all data types in the file?

SQL and Tableau both support a CASE function with the syntax

CASE

  WHEN Condition 1 THEN Result 1

  WHEN Condition 2 THEN Result 2 ...

  WHEN Condition N THEN Result N

ELSE Default Result

END

I'm thrilled that I can now use this with the In-DB tools, but I'd love to have this available in the regular function tools so I can stop nesting my IFs!

It would be great if I could save a tool and its configuration for future use. I'm sure this could be done now with a macro, and that's possibly how I'll do it.

The scenario is that we have numerous data inputs that require some finessing to import. Because the field headers are not in the first row, they aren't recognized accurately as comma delimited. But some of our fields also contain commas within the field, so the solution is to add a multi-field formula to replace things like ", Inc." with " Inc." and ", Ltd." with " Ltd."

But on occasion I find new text strings that need to be added to the formula, like ", Inc" (without the period) for instance.

I use this replacement technique with several workflows, so it would be great to change it just one time and have the other instances updated automatically.

Maybe in addition to our Favorites toolbar we could have a Custom or User toolbar where we could save tools along with their configuration.

Hello All,

During my trial of assisted modelling, I've enjoyed how well guided the process is, however, I've come across one area for improvement that would help those (including myself) overcome any hurdles when getting started.

When I ran my first model, I was presented with an error stating that certain fields had classes in the validation dataset that were not present in the Training dataset.

Upon investigation (and the Alteryx Community!) I discovered that this was due to a step in the One Hot Encoding tool.

Basically, the Default setting is for all fields to be set to error under the step for dealing with values not present in the training dataset, but there is an option to ignore these scenarios.

My suggestion:

Add an additional step to Assisted Modelling that gives the user the option to Ignore / Error as they see fit.

If this were to be implemented then it would remove the only barrier I could find in Assisted Modelling.

Hope this is useful and happy to provide further context / details if needed.

Salesforce Input tool throws a conversion error if labels are longer than 40 characters:

Could the the size of the field be increased to whatever the the Salesforce maximum is, or at least be configurable from the tool configuration. 

Particularly annoying is that the conversion error cannot be ignored (as seen in the Union tool) but will continue to show the result as yellow in the Scheduler. We like to keep a green board! 

It will be really useful if the Microsoft Query (aka MS Query, aka Excel Query) can be incorporated in the formula tool. This can make the workflow small and make the tool more powerful

One idea that could help a lot of users while preparing dashboard solutions where we might need to attach artifacts for proof or references that might have helped us in developing the dashboards. 

Dear Alteryx Gods,

Please hear my plea and add these beloved excel functions into the formula tool, using 3 Alteryx tools to do this simple task is ridiculous.

Thanks!