This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
The Remove Null Rows feature added to the Data Cleansing tool is really nice, however it doesn't work for a common use case for us where we have key metadata field(s) added to the data stream that make rows not null so we'd like to be able to ignore or exclude one or more fields from the Remove Null Rows output.
Here's a use case starting with an Excel file with multiple tabs where each tab holds the records for a different Province:
Note that the 2nd record in Southern is entirely empty, so this is the record that we'd like to remove using the Data Cleansing tool.
Since the Province name is only in the worksheet name (and not in the data) I'm using a Dynamic Input tool with the "Output File Name as Field" to include the worksheet name so I can parse it out later. So the output of the Dynamic Input looks like this:
With the FileName field populated the entire row is not Null and therefore the Remove Null Rows feature of the Data Cleansing tool fails to remove that record:
Therefore what we'd like is when we're using the Remove null rows feature in the Data Cleansing tool to be able to choose field(s) to ignore or exclude from that evaluation. For example in the above use case we might tick the "FileName" checkbox to exclude it and then that 2nd row in Southern would be removed from the data.
There are workarounds to use a series of other tools (for example multi-field formula + filter + select) to do this, so extending the Data Cleansing tool to support this feature is a nice to have.
I've attached the sample packaged workflow used to create this example.
Data Cleansing - Remove Null Rows filename issue.yxzp
I would like to request that the Python tool metadata either be automatically populated after the code has run once, or a simple line of code added in the tool to output the metadata. Also, the metadata needs to be cached just like all of the other tools.
As it sits now, the Python tool is nearly unusable in a larger workflow. This is because it does not save or pass metadata in a workflow. Most other tools cache temporary metadata and pass it on to the next tool in line. This allows for things like selecting columns and seeing previews before the workflow is run.
Each time an edit is made to the workflow, the workflow must be re-run to update everything downstream of the Python tool. As you can imagine, this can get tedious (unusable) in larger workflows.
Alteryx support has replied with "this is expected behavior" and "It is giving that error because Alteryx is doing a soft push for the metadata but unfortunately it is as designed."
Lately I've used the 'Add Prefix to Field Names' option in the Select tool. It works great, however when you click the button to add a prefix, the new window pops up and the focus is on the checkbox. I think when this box pops up, the focus should be in the text box so the user can start typing right after they click the button. This is the same case for the Add Suffix option, too.
We often get the following error message from the download tool
"00:00:23.555 - Error - ToolId 106: Error in libCURL: You have found a bug. Replicate, then let us know. We shall fix it soon."
Unfortunately this seems to be a transient error so we've not been able to replicate this in a useful & repeatable way. However - we see this happening at least a few times per week on one of our servers, so this is a continuing issue.
Please could you provide more detailed error messaging on the download tool so that this error can be debugged and/or replicated?
Any python user will tell you that one of the reasons why python is so powerful is the ability to access values using their indexes. It would be great if alteryx had such a system in place too, where you can access values or loop over them using their index, which can then be applied in creating new columns or calculations.
P.S - I know we can use the python tool but I would rather see this ability built in the formula tool.
When we edit formula tool, only first expression is expanded. I prefer all expressions are expanded as a default. When I want to shrink them, I want to 'expand all' icon like attached snap shot. This icon is toggled same as each expression's expand icon('expand all' <-> 'shrink all')
The email tool, such a great tool! And such a minefield. Both of the problems below could and maybe should be remedied on the SMTP side, but that's applying a pretty broad brush for a budding Alteryx community at a big company. Read on!
What I said the first time I ran the email tool without testing it first.
1. Can I get a thumbs up if you ever connected a datasource directly to an email tool thinking "this is how I attach my data to the email" and instead sent hundreds... or millions of emails? Oops. Alteryx, what if you put an expected limit as is done with the append tool. "Warn or Error if sending more than "n" emails." (super cool if it could detect more than "n" emails to the same address, but not holding my breath).
2. make spoofing harder, super useful but... well my company frowns on this kind of thing.
Today when we install custom tools that use DLLs, the DLLs must be placed in the Plugins folder inside the Alteryx installation directory. This requires a second step after the YXI installer runs. I would like to be able to package the DLL with the YXI installer and Alteryx will search for the DLL inside the tool's directory, just the same as what happens with custom Python tools. This will allow custom tools that use DLLs to be installed just as easily as the 1-step installation process for Python tools.
For example, this today does not work, but I want it to:
The following idea might not be as valuable as some of @SeanAdams posts, but it would save this user precious fractions of time. When I leave the canvas with my mouse (point A) to go up to the pallet I select and drag the tool down to the canvas. Sometimes I do right-click and go through the menus to add the next tool, but generally I go through that labor only when I'm inserting in-stream the tool. So here is my idea:
Double-Click your NEXT tool and it "Alteryx-ly" appears on your canvas in proximity to the hi-lighted (last) tool. Better yet, connect it! Now I can move from the pallet to the configuration panel directly without having to move my mouse down to the canvas and then over to the configuration panel.
Hopefully, my friend @Hollingsworth will find this time-saving idea worthy of a star. Speed demons like @NicoleJohnson and @BenMoss might not need this turbo boost, but at my age it is worth the ask.
I love this tool, but think it would be improved by including an option to create a column per delimiting character. This could be added in the number of columns selector box. In the case where 1 row has more delimiters than another, null columns can be created. Without this option you have to Regex count the delimiters, select the max and then embed the Text to columns tools in a macro and then pass the max columns as a param. Would be nice to resolve all this in the main tool.
The only thing I have ever found that Excel can do that Alteryx can't is creating a pivot table that allows the user to drill up and down levels of aggregation by collapsing or expanding levels in the data hierarchy. (like this).
Can you add an interactive table to the new interactive charting tool that can provide this level of functionality? It's embarrassing to have to tell Excel users they can't do this in Alteyrx, and likely leads many of them to stick to Excel--and miss out on all the other great things Alteryx can do.
Version 2.0 of the publish to Tableau tool does not work for the initial authentication if Tableau Server has CORS enabled.
This only impacts the UI for the tool that completes the sign in to Tableau Server and provides back the list of projects, data source names, etc.
When CORS is enabled, a 403 error is received with a response of invalid CORS request.
If the XML on the tool is manually edited and the tool is run, it works fine to publish to Tableau, with or without CORS enabled.
version 1.0.9 also works with no issues, but is not the ideal solution when users are on newer versions of Alteryx designer
Additionally calls to the REST API from a local desktop using postman or python work with or without CORS enabled.
Based on conversations with Alteryx support, the tool was not tested with CORS enabled, thus the bundle.js file completing the authentication for the GUI must not account for Tableau Servers with CORS enabled.
For those who build solutions with Tableau Server that utilize the REST API (e.g. like custom portals) CORS must be enabled to function, but it limits the ability to use version 2.0 of the publish to Tableau tool.
Have you ever used a Join tool with several (or many) Join fields, looked at the the L and R outputs and wondered, why didn't these records join? When there are many columns in your data, this can be a hard question to answer. It would be very handy if Alteryx could somehow report the Field(s) that each record failed to join on (perhaps as an optional added field to the L and R outputs).
It would be helpful to differentiate between annotations that have been automatically generated, vs those that have been manually entered. This would help speed up "reading" workflows, and reduce any confusion that occurs when annotations have been manually amended - but might look like auto-annotations.
E.g. auto-annotations appear Grey, whilst manually edited annotations appearing Black?
It would be helpful to have the same options for App chaining as Events in cases where there is user intervention required to correct input parameters, etc. This would also create continuity between a scheduled workflow and a Gallery app when you are upgrading a workflow for ad-hoc cases and interactivity.
Event Run Options- Multiple scenario optionsApp Run Options- Only one scenario option