Alteryx Designer

Definitive answers from Designer experts.
Numeric values show "[Null]" instead of a blank cell using the Input Data tool.
View full article
Workflow processing can take longer when a large amount of data is streamed in and out of a database. In-database processing can be used to speed up a workflow.
View full article
How To: Create an In-Database Connection
View full article
User is attempting to connect to Hadoop Hive with Active Directory Kerberos (Kerberos SSPI) in Alteryx and getting an error: Failed to get username: Routine Error: Unspecified GSS failure. Minor code may provide more information. The test button in the ODBC DSN is successful.
View full article
Where do you start when you see "An Unhandled Exception occurred"?
View full article
This article contains a list of common causes for being unable to run a workflow on a Gallery and solutions for each cause.
View full article
In-DB tools add a SELECT statement to Common Table Expression (CTE) queries.
View full article
Connecting to an Oracle APPS schema causes Designer to get stuck in "Not Responding".
View full article
This is a workaround for connecting to an Oracle database that uses LDAP authentication.
View full article
Error: "ORA-12592 TNS Bad Packet Error" occurs when running a workflow.
View full article
All the In-DB connections in Alteryx Designer are lost. Where are these settings stored?
View full article
Not able to clear the In-DB connection string history. There is no option or button to clear it.
View full article
Troubleshoot and solve the Hive error message "Syntax or semantic analysis error thrown in server while executing query."
View full article
Error, "Error SQLPrepare: [Teradata][ODBC Teradata Driver][Teradata Database] The object name is too long in NFD/NFC." when connecting to Teradata.
View full article
Select Tool fields show as missing & data types show unknown when querying from a database
View full article
User encounters an error due to invalid character in table name: Data Stream In (6)    Executing PreSQL: "CREATE TABLE table-name¶ROW FORMAT SERDE¶'org.apache.hadoop.hive.serde2.avro.AvroSerDe'¶STORED AS INPUTFORMAT¶'org.apache.had..." : [Simba][Hardy] (80) Syntax or semantic analysis error thrown in server while executing query. Error message from server: Error running query: org.apache.spark.sql.catalyst.parser.ParseException: ¶mismatched input '-' expecting (line 1, pos 18)¶¶== SQL ==¶CREATE TABLE table-name¶------------------^^^¶ROW FORMAT SERDE¶'org.apache.hadoop.hive.serde2.avro.AvroSerDe'¶STORED AS INPUTFORMAT¶'org.apache.hadoop.hive.ql.io.avro.AvroContainerInputFormat'¶OUTPUTFORMAT¶'org.apache.hadoop.hive.ql.io.avro.AvroContainerOutputFormat'¶TBLPROPERTIES (¶'avro.schema.literal'= '{ "type": "record", "name": "Alteryx", "fields": [{ "type": ["null", "string"], "name": "field1"},{ "type": ["null", "string"], "name": "field2"},{ "type": ["null", "string"], "name": "field3"}]
View full article
The message, "Error while trying to retrieve text for error ORA-12705" occurs when using multiple IN-DB tools to different Oracle connections.
View full article
While trying to connect the Oracle DB through Designer, it results in the below error: "Connection Error: Attempt to load Oracle client libraries threw BadImageFormatException. This problem will occur when running in 64 bit mode with the 32 bit Oracle client components installed." You have installed 64 Bit Oracle 11g client in the machine, where you have the Designer.
View full article
How to find the relevant information and configure a Databricks connection through the Manage In-DB Connections window. The Databricks connection includes bulk loading capabilities that allow users to load large data sets faster. 
View full article
Guide to In-DB Connection Files   Introduction In-DB connection files can be used as an alternative way for users to connect to a database. These files are stored as .indbc files and can, in many cases, be the preferred route for connecting to a database. This guide will walk through reasons for setting up a file connection, suggestions on storing the files on a network location, and steps to set this up.   There are many reasons to use an In-DB connection file:   Centralize data connection(s) in one location so that they can be used across multiple workflows and/or multiple users Have a single location where data connections can be modified, or credentials updated Allow access to data connections from multiple systems or server nodes Avoid having to set up ODBC DSNs on multiple Designer machines or server nodes Avoid Designer users needing to know credential information Things to know before you start Nothing prevents users who have access to file share location where File-based data connections are stored from downloading and sharing connection files with others. The passwords will not be visible because they are encrypted, but the connections will work on other Alteryx machines. Permissions will need to be controlled via the standard Windows permissions. These will only work with data sources that support In-DB through Alteryx: See Supported Data Sources and File Formats How to create the In-DB file connection(s) on a file share Whoever is going to create the data connection file will need to be on a machine that has Alteryx Designer installed.   1. Install the data source driver (if it is not already installed). You will eventually need to install the driver on all the machines that may connect to this data source. See the above Supported Data Sources link to see tested drivers and versions.   2. Create a DSN-less data connection. DSN-less connections provide ultimate portability as the connection string specifies the driver, host and authentication parameters and avoids needing to set up an ODBC DSN on all machines that will be connecting.   Example connection formats (notice the driver is part of the connection string):           odbc:DRIVER={SQL Server Native Client 11.0};UID=xxx;PWD=xxx;DATABASE=MyDatabase;SERVER=myserver.somedomain.com; odbc:DRIVER={Simba Hive ODBC Driver};Host=myserver.somedomain.com;Port=10000;UID=hdfs         odbc:DRIVER={SnowflakeDSIIDriver};Server=myserver.snowflakecomputing.com;Warehouse=mywarehouse;Database=mydatabase;Schema=PUBLIC;Role=;Uid=xxx;Pwd=xxx;         *For more information on connection strings, please see ConnectionStrings.com or contact your DBA who can get this for you.   3. Create the connection in Designer. Go to Options > Advanced Options > Manage In-DB Connections 1. Choose your Data Source type 2. Choose Connection Type to be “File” 3. Browse to the file share and name the file. It should be saved to a fully-qualified UNC path i.e.:         \\fileshare.domain.com\fileconnections\oracle.indbc       4. Set Password Encryption to “Hide” 5. Paste your DSN-less connection string in the Connection String area for Read. 6. Paste your DSN-less connection string in the Connection String area for Write. (Note that Read and Write need to be both specified and can be the same string, or different if need be) 7. Click Ok to save the connection file.       4. Build a workflow that uses In-DB tools to connect to your data source using the saved file to test the connection  5. Set the file or directory permissions for the connection file so they are restricted to only allow read access to users that should have access. This would include the Run-As user (if specified in the Alteryx System Settings) or users utilizing Workflow Credentials. More info on this can be found in the following articles:  How Workflow Credentials Work on a Private Gallery Set Required Run As User Permissions 6. Publish the workflow to the server. Make sure the In-DB connection file is not included as an asset.    Note: Credit for this article goes to the Alteryx Solutions Architects team!
View full article