Alteryx Designer Desktop Knowledge Base

How to Input .txt Files and Other File Types as Plain Text

I know I set this right, but it's not doing what I want it to!

Some Excel files, particularly those created by third-party programs, are encoded differently than Alteryx expects. In many cases, such files can be opened in Excel and then saved, resulting in files that Alteryx can open. Please refer to Designer Knowledge Base article entitled "How to check for encoding or formatting issues with Excel worksheets" for diagnosis tips.

Error: Can’t find the file: “[path\FileName]”. Make sure the file path is correct. Error text being revised from Error: File not found "[path\FileName]"

Querying a date from the Alteryx Server Persistence MongoDB using the MongoDB Input tool can be tricky since Alteryx Server dates are stored as string values. Here is how to use regex in the criteria section of the MongoDB Input tool.

When connecting to a DB2 Database via ODBC in Designer, some Date datatype from a column are coming up Null

Error: "FATAL: password authentication failed for user" when PostgreSQL or Greenplum credentials contain special characters when connecting in Designer.

This KB explains how to query views with the Google BigQuery Input Tool

Set yourself up for success with excerpts from the 2017 Tips and Tricks Book for bringing data into your workflows!

The Visual Query Builder window can take a long time to load because it always loads all column metadata for all tables for all schemas, even if a default database is selected in the database connection. This article will walk through using the In-Database tools as an alternative to using the Visual Query Builder.

A Calgary Database is a proprietary Alteryx format that allows users to query against a file of millions of records quickly without having to read in all the data.

Snowflake did an upgrade which results in an error message for both the data input and data stream out tools: Result download worker error: Worker error: [Snowflake][Snowflake] (4) REST request for URL #URL failed: CURLerror (curl_easy_perform() failed) - code=91 msg='SSL server certificate status verification FAILED'.

User gets a Win32 Exception when trying to connect to a database or edit a query

Exception handling may be needed so that a scheduled workflow continues even if a pre or post Oracle SQL statement has an error.

Characters that are not on a standard English keyboard may need translation into Unicode or a language-specific code page for Designer and database drivers to read them correctly. Characters with incorrect encoding will often appear as boxes or question marks in the Designer Results screen and error messages. Unicode characters take more bytes than English ASCII characters. Changing the column type and increasing the column size may be needed. In Designer, the column size is the number of characters, not the number of bytes.

When importing data from an SAP HANA database, a conversion error from VARCHAR1 to ASCII may occur. 

FieldID does not match FileHeader

Error: "Cursors are not supported" or "Cursor support is not an implemented feature" when running a workflow against SQL Server or Azure Synapse.

Not able to select a different database for existing Gallery connections for SQL Server within Designer.

Error: "Query timeout" when running a workflow connected to Amazon Athena.

Spatial Data from SQL Server shows up as "None", "Null", or other characters in the Input Data tool.