Alteryx Designer Knowledge Base

Calgary Loader (2) PagedFile::Add: keys out of order, sort not supported yet.

Troubleshooting error with Publish to Tableau Server tool: TypeError: Cannot read property ‘token’ of undefined

Snowflake External Tables are not showing in the Alteryx Visual Query Builder tab.

Troubleshooting: Error creating a Snowflake Table

Error: "ORA-00900: invalid SQL Statement" occurs when running a procedure in the Pre or Post SQL Statement for Input or Output Data tools.

Error - There were errors with LOADING please check your ERROR TABLES, when Output to Teradata with French Character data.

Error: "HTTP Error 403: Forbidden", when using Output Data tool to Hive HDFS in an encrypted zone.

This KB is extracted from the Inspire 2019 Tips + Tricks and outlines how to connect to a document library (Sharepoint) via Alteryx.

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.

Connecting to Google Analytics is becoming more and more popular. There are a few things you need in order to use the Google Analytics macro; a Google Account (e.g., Gmail) and authorized access to an existing Google Analytics account. This article will help you get the rest of the way.

Error: "ORA-12592 TNS Bad Packet Error" occurs when running a workflow.

Additional characters such as ! are appearing in emails sent from Designer.

Error: "Oracle driver: You are not licensed to use this DataDirect Technologies product" when connecting to Oracle in Designer.

Not able to clear the In-DB connection string history. There is no option or button to clear it.

Cannot update passwords in the Input Data or the Output Data tool.

Message: "No Lua script" was found explanation.

Error - Unable to find the dll: "telapi.dll", when using the Teradata Bulk Loader option in the Output Data tool.

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.

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

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

Configuring Gallery workflows to use temporary files for e-mail attachments or output   This article will help you configure Gallery workflows to use temporary files in the Engine’s staging directory for e-mail attachments or output.   Procedure   Start by putting the file that will be used as an attachment or output in the same folder directory as the workflow. Then, in Designer, choose the file by browsing to its location on disk. Next, go to Options, Advanced Options, and Workflow Dependencies. The best practice method is to change the output file data source path to a relative path. Select the option to Show Individual Tools, and then choose the Edit button next to the output file.     Click on the Relative button, and this will change the path of the file selected to be relative to the workflow. The path will appear like this:.\Output.yxdb.      Once the workflow is ready to publish to the Gallery, select File, Save As, and then the Gallery. The Save Workflow window appears, choose Workflow Options, and Manage Workflow Assets.     In the Save Workflow window, you have the option to either check or uncheck the file as a workflow dependency. When the file is unchecked, a new file writes to a staging directory each time the workflow runs on the Gallery. The staging directory used for the dynamic output gets removed automatically on a space needed basis.     When sending the output to recipients from the E-Mail Tool, the attachment should have a relative path to the workflow. Note that entering just the file name and extension implies a relative path to the workflow. This is recommended. Also, the use of a Block Until Done Tool will ensure that the output file writes entirely before sending the e-mail.       Similarly, when using an E-Mail Event, be sure the output file is configured with a relative path as well.     Additional Resources   Workflow Dependencies