Alteryx Designer Desktop Knowledge Base

One of the best things about Alteryx is the ability to read in multiple files very easily and automatically combine them into a single dataset. This becomes a bit trickier when dealing with files that have different schemas or Excel files with multiple tabs. Adding both multiple excel files with multiple tabs, and having the schema change within each tab takes it to another level.

This article is part of the CS Macro Development Series. The goal of this series is to communicate tips, tricks, and the thought process that goes into developing good, dynamic macros.

"I have a bajillion files that I need to bring into my workflow... wayyyyyy too many for me to use individual Input Data tools! What's the best way to do this?"                    - every Alteryx user ever

Engine logs are captures of your Results Window and so much more. They can be profoundly useful for troubleshooting, but you have to know how to enable them and how to use them.

This article is part of the CS Macro Development Series. The goal of this series is to communicate tips, tricks, and the thought process that goes into developing good, dynamic macros. In this part, we demonstrate how to read in multiple files with different schemas using a Batch Macro.

Error “The Designer x64 reported: InboundNamedPipe GetOverlappedResult: The pipe has been ended” when both Use AMP Engine and Enable Performance Profiling is enabled in the Workflow Configuration Runtime tab

Runner tool is not able to run workflow which is stored in a path containing double-byte characters.

These macros allow you to convert IP addresses to DWORD formatting and vice-versa for IP validation. These can be used to determine if an IP address was part of a range and, if it was, create two new ranges on either side of it.

This article is written to provide an idea to output an excel sheet per data stream within one workflow using a batch macro.

The article explains why a batch macro only runs only.

How Alteryx Designer and Server use file paths

This article is part of the Client Services Macro Development Series. The goal of this series is to communicate tips, tricks, and the thought process that goes into developing good, dynamic macros.

Data Cleansing tool metadata is not completely retained, following a macro, when the workflow is saved and re-opened.

When publishing a workflow to Gallery or Scheduler (Designer + Desktop Automation) or when packaging a workflow for export, checking the boxes for what to include and what to exclude seems to work inconsistently as of Designer 2020.2. The workaround will tide you over until you can upgrade to 2021.2.

Error "Timestamp is not close enough to the current server time" when running a workflow that contains an Oauth Macro in Alteryx Designer.

Designer crashes when a forward slash (/) is used in the Output Name field of the Macro Output tool.

Custom tool not showing in tool pallette after installation.

Rather than copying and pasting this process from workflow to workflow, I decided to create a macro (and this macro doesn’t require any configuration!) and make it available to a wider audience with the hope that it will save time and energy by eliminating the need to recreate the process of translating a date week number, quarter, etc.

This article is part of the CS Macro Development Series. The goal of this series is to communicate tips, tricks, and the thought process that goes into developing good, dynamic macros.

Suppose you have a datetime stamp in a dataset for the timezone where you are. This dataset includes data for locations in timezones other than the one you're in and you want to convert your datetime stamp to reflect the local time zones of the locations in your data.

Sometimes large amounts of data can 'overwhelm' a tool or process in your workflow and make it appear like it is stuck or frozen.  This was the case recently when a user attempted to pass 7 million rows of data to a CASS tool.  Splitting these records into smaller chunks makes the process run much quicker.