Alteryx Designer Knowledge Base

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   

How To: Add Exception Handling to Oracle Pre or Post SQL   Exception handling may be needed so that a scheduled workflow continues even if a pre or post Oracle SQL statement has an error. Since PL/SQL currently is not supported in the SQL Editor, you will need to create a stored procedure for exception handling and call the stored procedure in the pre or post SQL section.   This example shows how to create a stored procedure that handles exceptions for a delete table statement when the table was previously removed and does not exist. (Oracle currently does not have an IF EXISTS option.)   Procedure   Adding a parameter for the table name is recommended so that one stored procedure can be reused for any table.   Note: You will need to create procedure permission on the Oracle database, contact a DBA if you are lacking this permission.    Use this format in your SQL editor for the stored procedure. Notice a space is added at the end of the SQL command ‘DROP TABLE ’ followed by || for concatenation and the parameter name used as a place holder for the table name.      Once the stored procedure exists on the database, you can reference it in the Pre SQL or Post SQL sections of the Input Data or Output Data Tool. Click on the Ellipsis button to open the section.      On the Stored Procedures tab, just highlight the stored procedure name on the left, and then in the Value text box, type in the table name surrounded by single quotes.     Alternately, you can call the stored procedure from the SQL Editor tab, using this format:     Additional Resources   Input Data Tool  Output Data Tool   

Tips and tricks on how to output multiple sheets to an Excel file with the Output tool or with Reporting tools. 

The partnership between Alteryx and Tableau is becoming stronger and stronger, and the seamless effortless integration has been made easier through the Publish to Tableau Server Tool. This article demonstrates the use of the Publish to Tableau Server tool, available on the Alteryx Analytics Gallery.

No Lua script was found   When reading in from a database, the following message is seen:   Info: Input Data (n): No Lua script was found for corresponding ODBC driver.   Environment   Alteryx Designer 2018.4+ Windows Operating System ODBC database connection     Cause   This message indicates that you are connecting to a database, and no Lua script was found. This is expected when you are connecting to a database that does not work out of the box with Alteryx. Please note this is a message and not an error or warning; it will in no way prevent your workflows from executing successfully if you are not using a custom Lua script.     Explanation To support new ODBC drivers that Alteryx has not validated/tested, you can create a custom Lua script that will map driver and database data types to Alteryx types.  To learn more about this (and find sample Lua scripts) please see the documentation Customizable ODBC Driver Connections found in: %LOCALAPPDATA%/Alteryx/bin/RuntimeData/ODBC

Hive ODBC can be slow when writing to tables. If you are looking for a faster option to write to Hive and want to create a new table or overwrite an existing table, use the  IN-DB tools   to output your data. 

In a  previous article , we've shown you how you can upload to FTP using the  Download  tool. With the release of Alteryx 10.5, the Download tool now supports uploading to  SFTP . With this addition, we'll take the opportunity to show you some more examples of uploading data to SFTP/FTP and show you how seamless it can be.

How to check for encoding or formatting issues with Excel worksheets   When Excel worksheets are used in Alteryx Designer, sometimes Designer has difficulty reading the data. Viewing the worksheets in XML format is a good way to check for encoding or formatting issues as all of the encoding and formatting is shown.   Prerequisites Product - Alteryx Designer, Gallery, or Server and an Excel file used in Alteryx workflows or applications   Procedure To view in XML, open the Excel worksheets in 7-zip or another application used for .zip files. Use the format C:\folder_path_of_the_workbook\Excel_file_name.xlsx\xl\worksheets. Next, click on the sheet name and the XML for the worksheet is shown.          Notice the type of encoding is listed at the top. Followed by the formatting schemas, and then formatting for the worksheet. If needed you can change the extension of the worksheet from .xml to .txt and edit the encoding or formatting of a worksheet to match a working example, and then change the extension back to .xml.    To edit, right click on one of the sheets, select Rename, and change the file extension to .txt. Edit as a text file, and then Rename again to change the extension back to .xml.                                    Common Issues  If the Excel workbook is created automatically, such as being created by a script, information needed for Designer to open the worksheets may be missing. Excel can sometimes add this information when opening the worksheet, but Designer is not able to add default encoding and formatting if it is missing. If you come across an issue, it is a good idea to try adding example data directly in Excel and saving as Excel should automatically add the needed encoding and formatting. Afterward, you can compare this with the broken file, and update it to match the working example.    There are other possible reasons why Designer may not be able to open an Excel spreadsheet. However, checking for encoding and formatting issues in XML view will catch many of the problems with opening Excel data in Designer, so it is a good place to start.    Additional Resources Character encoding Microsoft Office XML formats Structure of a spreadsheet  

Issue    During run time of workflow, the following error is received:    Error: Input Data (1): Error SQLExecute: [Simba][Athena] (1040) An error has been thrown from the AWS Athena client. Athena Error No: 99, HTTP Response Code: 1759505392, Error Message: Unable to connect to endpoint [Execution ID: e7fe279d-f39b-4872-b37d-8ad49d49f3f5]   Environment   Alteryx Designer Amazon Athena Environment Windows Operating System Amazon Athena ODBC Driver (found here)   Cause   In version 1.0.3 and greater of the ODBC Driver, Result Set Streaming is enabled by default which has extra requirements. More info on the requirements here.   Solution - Connection String (DSN-less) If connecting via a Connection String: Add UseResultsetStreaming=0 to your connection string Example string:  odbc:Driver={Simba Athena ODBC Driver};AwsRegion=[Region];S3OutputLocation=[S3Path];AuthenticationType=IAM Profile;AWSProfile=[YourProfileName];UseResultsetStreaming=0 Use this string with your standard tools (Input Data, Output Data) or with a Connect In-DB Tool. Solution B - DSN Connection  If you are connecting to your Amazon Athena environment with a DSN connection (via ODBC Admin): Open up ODBC Data Source Administrator  Find your Athena connection and select it Hit "Configure..." Hit "Advanced Options..." Uncheck the "Use Resultset Streaming" box Hit OK to save the Advanced Options Hit OK again to save your connection  

Having trouble reading or writing Microsoft Access files? No worries - Client Services is here to help!

Output data as Text File   Within Alteryx there isn't an output option directly to a text file. To achieve this you will need to use a flat ASCII file.   Step 1: Bring in an output data tool and choose the ‘Flat ASCII file (*.flat) option   Step 2: You will then see this below screenshot in the output tool configuration window.     Step 3: You will now need to change the file extension from .flat to .txt, this will chage the flat file to a text format.       Step 4: You can now click on the hyperlink in the results window and open your text file in a supported application.         Example attached.

Connecting to Hadoop HDFS/Hive/Impala/Spark with Alteryx Designer.

  We get quite a few requests asking how to add the current date to Excel spreadsheet file names. The difference in adding information to your file name in Excel and other output configurations is that you have to use the Reporting tools for Excel to accept the new file name.   Why would I have to use the Reporting tools, you ask? Simply put, Excel thinks that when you are adding a prefix or suffix to the file name that you are stating that additional information is the “Sheet Name” and not appending the file name from the Output Tool. The Render tool in the Reporting tab on your palette basically tricks Excel into thinking that you are creating a separate report and is able to append the date.   In order to add the date to the file name you will connect these tools to your workflow in the order, you see below.      In the Formula Tool, create a new field that is a String type.  Go to the DateTime functions and add the DateTimeToday() expression. No configuration of the expression is necessary.      The Table tool will allow you to Group By this new field. In the GroupBy Configuration, choose the Date field you created in the Formula. In the Per Column Configuration, uncheck the new field. This will allow you to group by the new field name in the Render Tool and still remove it from the data so that your new field does not appear in your report.          Use the Render Tool to output your Excel spreadsheet with today’s date in the file name.   Output Mode - Choose a Specific Output File. Output File - Specify the Excel 2007 Spreadsheet (xlsx) and point to where you would like to save the documents. The file name you specify will be replaced with the date in step 5 below. You will then check the box that says Group Data into Separate Reports. Field to Group on - You will choose your new field that you created. Modify Filename By – Replacing Filename With Group. Report Data – You will choose Table and can leave the rest as defaults.  

  When writing out plain text files you have a couple of different options, a popular one being .csv files. CSV stands for comma separated value, which indicates that a comma is used to separate values within the file. The default program for opening .csv files varies but it is Excel on most machines. When opened in Excel, a .csv file will look just like an Excel document with the only difference that all fields are text (strings). When opened in a text editor, you can see the comma separated values:   However, you don’t have to use a comma as a delimiter; Alteryx will let you choose many delimiters including pipe |, tab \t and even no delimiter at all (Indicated by \0 ). You also don’t have to use .csv as the file extension.   In this example, even though the file format selected is csv, the file actually has a .txt extension and will be delimited by pipes | :       Other options when writing out delimited files are:   Max Records Per File – you can limit the number of rows to write out.   First Row Contains Field Names – uncheck if the first row is not to contain field names and Alteryx will ignore the field names.      Quote Output Fields – the options are auto, always, and never. Quotes are used in delimited files to indicate whether a delimiter is to be treated as such or as part of a field. For example, if the address 123 Main St, Apt 2 is quoted and the delimiter is a comma, it will be treated as one field. If the address is not quoted, it will be treated as two columns (This can sometimes lead to problems when reading in delimited files with Alteryx).   Code Page – You can select the code page for your document. The default for CSV is Latin I which completely covers all characters in the English language. Unicode is also available.   Line Ending Style – You can select the line ending style to be used for your delimited files. Available options are Windows (default), Unix, or Mac.

When creating reports within Alteryx, you can name Excel tabs by specifying a column to use in the Layout tool. This is done in a 3 step process. Step One:   Choose your grouping column; below, the Table tool is being used and [DMA_Name] is being used for the Group By field. This would also apply with the Charting and Map tools.         Step Two:   In the Layout tool, change the Layout Mode to Each Group Of Records. Next, choose the column you would like to Group By;  for the example we will use [DMA_Name]. Next, change the Orientation to Vertical with Section Breaks. By doing this, the Section Name option will appear at the bottom of the tool configuration and allow you to choose the column you would like to use to name the Excel tabs.       Step Three:   Update the Render tool to create an Excel spreadsheet. In our example, each of the Excel tabs was named for the DMAs contained in the data.           Keep on reporting!

A user posted on the Forum that the ampersand character (&) was causing an error when importing a series of KML files. The fix? Have a prior Alteryx process replace this character with the word 'and' within all KML files without ruining the rest of the file. To accomplish: Pull in an Input Tool and set the file type to .csv with no delimiter (designation is \0). In the Input Data Source portion, use the wildcard (*) to pull in all of your text files (using KML in the example). For the option Output File Name as Field, select File Name Only. Use a Formula Tool to update the text within the files. Output each file individually with one Output Tool, making sure to set the output to dynamically update based on your file name field. The process is fairly straightforward and should help resolve any text or character issues that may be an issue. For an example, please see the attached workflow.

Is it possible to append to a YXDB instead of having to read in the whole thing, union the new records, and then re-create it? The short answer is, No, but you can accomplish this with SQLITE.

How to use Runtime setting in the Workflow Configuration options to disable output and Browse tools  

You may have a use case whereby you have a large dataset and you want to output it to separate excel files. However, in each of these excel files you would like to apply a template format.

When writing to Excel, have you ever had the need to populate a column with values that come from formulas referencing other cells in your data? You’ve probably noticed that when writing to either .xlsx or .xls Excel file formats that your output still appears as a string, rather than a calculated value, like the below:   .xlsx Each formula cell has the proper cell references and syntax but will need to be interacted with (add or remove a space in the formula and hit enter on your keyboard) to calculate the true formula value.   .xls When expanding on the string you’ll see there’s an apostrophe (‘) preceding the formula and you’ll need to remove each and hit enter on your keyboard for the formula to execute.     In the attached v10.1 workflow, Writing to Excel with Formulas.yxmd, we provide a sample formula expression to build formulas with basic cell indexing (using a record ID field) and the ability to write formulas that can be interpreted by Excel. This is done by leveraging the .csv file format; when excel opens this output file type it automatically recognizes the formula syntax and will interpret it as such – populating each cell with the true formula calculated value: