Alteryx Designer Knowledge Base

Definitive answers from Designer experts.
This article details on the steps to read/extract password protected excel file in Alteryx Designer using the R code.
View full article
How To: Read XLS files – with several tabs that contain diacritics Information
View full article
Simple fix when receiving an encoding error in a PostgreSQL connection
View full article
The symptoms, diagnosis and solution for the ConnectNamedPipe error associated with McAfee Adaptive Threat Protection.
View full article
Customers using pre 2019.4 Designer and Insights Data need to update to the Mapbox maps or they will see this issue with Digital Globe maps.
View full article
How to collect Wireshark traces to troubleshoot network-related issues.
View full article
Robocopy is a robust Windows Command Prompt utility for copying files from one location to another. Unfortunately, it uses exit code 1 to indicate success which Alteryx interprets as an error.
View full article
When running a workflow via the Scheduler (for Designer with Automation), the following error is observed:
View full article
Troubleshooting error with Publish to Tableau Server tool: TypeError: Cannot read property ‘token’ of undefined
View full article
How to troubleshoot an error opening "[filepath].yxdb": Data at the root level is invalid. Line 1, position 1.
View full article
The cause of this error is that too many delimiters were located in that specified record. For example if I had a text file with the contents below:
View full article
Why did all of my scheduled workflows fail? What does the error “Logon Failure: unknown user name or bad password” mean? Read this article to find out!
View full article
The error above is usually due to a company firewall restriction. If you are receiving the error above when installing, please download run the individual installers from this page:http://downloads.alteryx.com.
View full article
As we transitioned to a new licensing system in the 11.8 and 2018.1 releases, we changed how licenses are authenticated.
View full article
When importing a .xls file using the Input tool, Alteryx produces NULL values for specific cells, why does this happen?
View full article
This article is part of the Tool Mastery Series, a compilation of Knowledge Base contributions to introduce diverse working examples for Designer Tools. Here we’ll delve into uses of the Date Tool on our way to mastering the Alteryx Designer
View full article
Receive "ERROR: The session is read-only" using pre/post SQL option in the Input Data tool when attempting to perform any operation that is not a select statement, such as dropping/creating tables
View full article
Select Tool fields show as missing & data types show unknown when querying from a database
View full article
When importing a delimited file, have you ever run across an error saying ‘Too many fields in record…’ and it’s something like record number 1478254 and you think to yourself, “how the heck am I going to find that record and correct it?”   Well, let us help you with that.   This message is essentially telling us that some particular row of data, when parsed, has more fields that the first row of data (usually caused by an extra delimiter in that row). The first step in identifying the row is to change the delimiter in the Input Data configuration window. Change the delimiter from the current delimiter to \0 (that is a backslash zero, which stands for no delimiter). This will read in your file but instead of parsing, it’ll just read in the data as is.   Current delimiter:   Versus:   No delimeter:   Now just add a RecordID tool and Filter tool so we can filter on RecordID 2 (or 1478254) to find the row that is holding us up.     Now that you’ve identified the row that is causing issues, you could go back to your original data, correct it and try importing it again.    If you were looking closely at the example data, you may have noticed that record 4 also had a different number of fields as row 1.  After correcting row 2 and importing , again, we would get an error for row 4. Just follow the same procedure to correct additional errors.  This could probably be done through an automated/iterative process, but that will have to wait for another time.   (attached is an example workflow created in Alteryx 10.0)  
View full article
Symptoms   My workflow was doing just great, reading in a bunch of stuff and cranking out new data like a boss. But then I saved the workflow, closed down Alteryx, and now when I try to open that file up again, I get the following error:   There was an error opening "C:\my file name.yxmd" There is an unclosed literal string. Line 3042, position 42.   Does this mean anything to you guys? Diagnosis The workflow has likely become corrupted, perhaps after saving it across a network, and has dropped something in the save process.  Solution   Alteryx creates backups of the workflows (same name with a .bak extension). Try to open the .bak file in Alteryx.    Go to File ->Open and change the "Files of Type" to All Files. The .bak files will show up and you can open the one you are having difficulty with.    Another alternative would be to check if Alteryx auto-saved it prior to your last save. Go to File -> Open Autosaved files.
View full article
These methods should work in most versions of Alteryx.    One of the most common issues we see from clients trying to read in a .csv file is that they are receiving an error starting “Too many fields in row x”, and because of this Alteryx can’t read in the file.     There are a couple of different ways you can resolve this error.   First, in the Input Data tool, you can tell Alteryx to treat read errors as warnings to allow the file to be read in.     This will change the Error to a Warning so that Alteryx can read in the file so you can investigate.     The other method is to read the file in with no delimiter. You can do this by changing the delimiter in the Input Data tool to \0.     Once you have your data parsed back out into its fields, you can use the Dynamic Rename tool to correct your field names, a select tool to remove the original field, and a simple Trim() function to remove the extra delimiter from your data.   This process is illustrated in the attached workflow, created in version 10.1.    
View full article