Alteryx Designer Desktop Knowledge Base

Use Designer to capture the first available value from a set of fields in two ways: if-statements, data manipulation

Scenario: You monitor the mileage of multiple trucks as they deliver shipments over the course of a week and record additional information regarding each truck in a file (Truck Metrics).  Each truck’s cumulative mileage per day is recorded in a separate file (Truck Mileage).  Your goal is to update the mileage-related fields in Truck Metrics with the values recorded in Truck Mileage.  Note: today is Tuesday so only fields for Monday and Tuesday will be updated in in the Truck Metrics file.         Methods:  Manually Select Fields to Update Whether the data is uniquely identified by a Truck Number (or Record ID) or identically ordered in both files, data from Truck Metrics (the table to be updated) and Truck Mileage (the data used for updating) can be Joined together.  Then, using the Select functionality within the Join tool, I can manually choose the fields from Truck Mileage that I want to use to replace the fields that need to be updated (Figure 1).       Figure 1: Fields from Truck Mileage (Yellow) replace fields from Truck Metrics (Blue).  Note that fields in yellow are selected while fields in blue have been deselected.  Fields that need to be included from Truck Metrics (Red) remain selected.    Fantastic!  A simple, straightforward way to update fields!  But, as any analyst knows, working with data is rarely simple or straightforward.  What if you’re dealing with 20 fields that need to be updated, not just 2?  In that case, manually selecting fields to update is not only tedious but also error-prone.  For these types of situations, I recommend a process that allows for a more dynamic approach.       'Verticalize' the Data to Dynamically Update Fields Transposing, or ‘verticalizing’ data, allows for a more dynamic workflow when you have unknowns in your processing.  In a scenario such as this one, you may have an unknown or changing number of fields that will need be updated in Truck Metrics.  Using this approach, we’ll first Transpose both data sets to configure the Field Name and its associated value in a single row (Figure 2).    Figure 2: The data is transposed from Truck Mileage and Truck Metrics.  The highlighted fields in Truck Metics indicates which fields will be updated, as the same field exists in Truck Mileage.     Then, we’ll Join our datasets based on two fields: Truck Number AND Name.  This ensures that fields in Truck Mileage will match to the correct fields in Truck Metrics, assuming the fields names in both tables are named in the same way.  The only selecting we’ll have to do is to make sure all fields from the Right data source (in this case, Truck Metrics) are deselected (Figure 3).  This allows that, in the situation of matched Truck Numbers and field names, the updated values will be used.   Figure 3: The Joined fields indicate the fields that exist in both Truck Mileage and Truck Metrics.  Fields in yellow (Truck Mileage) are selected to reflect updated values in downstream tools.  Fields in blue (Truck Metrics) are deselected.    Note that any unmatched fields have fallen out of the Right side of the Join:     To add them back into the data stream, simply Union the Center and Right Joins together, setting the tool to “Auto Configure by Name”.  Then, to rearrange the data into its original format, use the Cross Tab tool (Figure 4).  And, voila!  Your data is updated!   Figure 4: The updated fields are highlighted in yellow.  All other fields originally included in Truck Metrics are included the in the final results as well.              

counting records in a dataset

using the “Sequence Polyline” Build Method to visualize and analyze data

The example below will provide the distance between every store in a dataset to every store in that same dataset. Here's how we did it.

locating the nearest retail location to a customer using Designer tools

When using Excel spreadsheets in Alteryx, sometimes there may be difficulty in reading the data. Viewing the spreadsheets in XML format is an excellent way to check for encoding or formatting issues.

In some cases Designer is very slow when working from home. This can have several root causes.

Error connecting to Office 365 using the Sharepoint Input tool - "The sign-in name or password does not match in the Microsoft Account system", when the user tries to connect to Sharepoint from the Alteryx Designer

Quick Connect: Internal-Error-Unable-to-add-new-Alias-to-the-Alias-Manager

Troubleshooting the Error: The sheet "[sheet_name]" already exists in file "[file_path]". Select a new sheet or file for output, or select an overwrite output option for the current file.

The error message appears when using System Settings in Alteryx Designer.

Use a constant to simplify your production moves, minimize the effort to making updates to your workflow tool configurations

"No table chosen; Please select a Table from data source".

The Sequel Viewpoint software is breaking Designer from loading.

Troubleshooting the error: Data source name not found and no default driver specified when connecting to a database in Designer.

If you are unlucky while rendering a map in Alteryx with a Carto base map, you may encounter the error message Error: AGG error loading font (C:\WINDOWS\fonts\C:\Program). This article explains the cause of this error, and how to resolve it. 

This article details how to enable the logs for the installation of tools written with Python SDK.

How to get rid of annoying "Cache entry deserialization failed, entry ignored" error during YXI installation

What happens when one installs the YXI file of a Python-based tool in Alteryx Designer.