Community Spring Cleaning week is here! Join your fellow Maveryx in digging through your old posts and marking comments on them as solved. Learn more here!

Alteryx Designer Desktop Knowledge Base

Definitive answers from Designer Desktop experts.
Not able to clear the connection string history. There is no option or button to clear it.
View full article
As of the release of version 11.0, the Alteryx Designer supports reading in single and multiple input files in a zipped archive file (.zip).  Now, multiple files of the same file type in a zipped archive can be read into the Designer in a standard Input Data Tool.
View full article
UPDATE 11/20/2017: Microsoft released a fix for the XLS issue described below, this fix is included in their November 14, 2017 Monthly rollup. For your convenience, this is the link to the fix for Windows 10 https://support.microsoft.com/en-us/help/4048954/windows-10-update-kb4048954 And this is for Windows 7 and other OS https://support.microsoft.com/en-us/help/4048957/windows-7-update-kb4048957 We’ve been made aware of an issue connecting to .xls files with the File Format: Microsoft Excel 97-2003 (*.xls). The behavior manifestsin two ways. As an error pop-up box: 'InvalidArgument=Value of '0' is not valid for 'itemIndex'. Parameter name: itemIndex' Within the Results - Messages pane of the Designer or on the Annotation associated with the impacted tool: ‘Error: Input Data (2): Error opening connect string: Microsoft JET Database Engine: Unexpected error from external database driver (1).\3275 = -535434136’ The error box appearswhen an Input Data tool is configured to open an .xls file for the first time ever (if there are cached tables, then the error box will not appear). TheAnnotation and Results pane errormessage occurswhen an .xls file is dragged directly onto an Alteryx designer canvas or when a workflow containing an Input or Output tool that connects to an .xls file using the above format is run (within the designer, a server, or on a schedule), respectively. The error and experience are discussed in this Alteryx Community post, though you can also read about the issue on this external forum and here, documenting this is a widespread experience across many platforms. Towards the bottom of the external forum post, you can see a comment from a Support Engineer on the Microsoft SQL BI team stating that Microsoftrecommends not using the Microsoft JET engine drivers as the current solution to the issue. We detail below how to follow that directive within Alteryx. Theroot cause of the errorcomes from Microsoft’s October Security Update (links below). If you have already had the update installed, must remain using the update, or choose to proceed with the update, you will experience this behavior. In those situations, here are a couple options available to you. For new or existing workflows: Within Excel, manually save the .xls file as a .xlsx file and within Alteryx update tools pointing to the old file to point to the new file or Browse to the new file within an Input Data tool For existing workflows: Within Alteryx, manually change the File format to ‘Microsoft Excel Legacy (*.xlsx)’ within the affected Input Data or Output Data tool (described below) For new workflows/new Input Data tools you will not be able to manually Browse out to the .xls file and read it in as you will receive the pop-up error message desribed above. Your options are: Drag and drop the desired .xls file from the Windows explorer box onto the Designer canvas and then manually change the File format to 'Microsoft Excel Legacy (*.xlsx)' Drag an Input Data tool onto the canvas and paste the full path of the desired .xls file into the Connect to a Database box within the Configuration pane and then manually change the File format to'Microsoft Excel Legacy (*.xlsx)' Option 2 and 3 Step-by-Step Determine if you have the “Microsoft Excel Legacy (*.xlsx)” option available within your Input Data tool. You can determine this by loading any file into an Input Data tool, and then clicking the “File Format” drop-down. If you have this option, you can skip to Step 7. Determine the “bitness” of your Office Installation. The file you download will depend on whether you are running a 32-bit or 64-bit version of Office. https://support.office.com/en-us/article/About-Office-What-version-of-Office-am-I-using-932788B8-A3CE-44BF-BB09-E334518B8B19?ui=en-US&rs=en-US&ad=US In this screenshot, I’m using a 32-bit copy of office. Browse to the Microsoft Access Database Engine 2010 Redistributable page and click “Download” https://www.microsoft.com/en-us/download/details.aspx?id=13255 Select the download that matches your Office “bitness” from before, then click “Next”. The file will begin to download. Save the file to a location that you can run it from. Run the previous installer you downloaded. You can simply click “Next” or “Install” through the installation utility, as options do not need to be changed. Once you receive the dialog that the setup has completed successfully, you can click “OK” and continue to the next step. If Alteryx Designer was open prior to the installation, you should close the program fully, saving your work, and then re-open Alteryx Designer. Otherwise, if Alteryx Designer was not already open, you can open it now. Within Alteryx Designer: Open the workflow with the issue in Alteryx Designer. b. Click on your Input Data or Output Data tool that is experiencing the issue. (Refer to Option 3 above if you are receiving the pop-up error box while connecting to an .xls file for the first time) c. Click the “File Format” drop-down and choose “Microsoft Excel Legacy (*.xlsx)” d. Data should now display in the preview window and the error should no longer appear if you click off the tool or run the workflow. We understand this is likely to be a frustrating experience for our users and we are investigating what can be done from the Alteryx side to produce a fix for the issue. We are also following the Microsoft posts to understand what their response will be and if they will take any action toward resolution. Please contact Customer Support to report your experience with this issue, as that will allow us to contact any impacted users directly if and when there is a fix made available. Updates associated with the error: Windows 7, Windows Server 2008 R2 - https://support.microsoft.com/en-us/help/4041681/windows-7-update-kb4041681 Windows Server 2012 - https://support.microsoft.com/en-us/help/4041690/windows-server-2012-update-kb4041690 Windows 8.1, Windows Server 2012 R2 - https://support.microsoft.com/en-us/help/4041693/windows-81-update-kb4041693 Windows 10 Original - https://support.microsoft.com/en-us/help/4042895 Windows 10 1511 - https://support.microsoft.com/en-us/help/4041689 Windows 10 1607, Windows Server 2016 - https://support.microsoft.com/en-us/help/4041691
View full article
How do you Input Excel files which may already be open?
View full article
Why can't we read an Excel file when it's open?
View full article
Error while connecting to a database, from the Input Data Tool - Error: Input Data (13): Error SQLDriverConnect: [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application.
View full article
SQL Server read performance is slow in Designer.
View full article
How to download and install SQL Server ODBC drivers.
View full article
Error: "ORA-12170: TNS:Connect timeout occurred" when running a workflow.
View full article
Error: "Incompatible with the Client software" when connecting to Teradata in Designer
View full article
Error: "Must declare the scalar variable '@var_name'" when running PL/SQL in Pre or Post SQL Statement Section.
View full article
This KB outlines the workaround for DE18888 where Cyrillic characters from DB2 are not displaying in Designer
View full article
Error: "Login failed for user ' '" when connecting to SQL Server with Azure Active Directory.
View full article
Receiving timeout errors when attempting to use the MultiSubnetFailover=true parameter in a SQL Server Availability Group with a multi-subnet listener.
View full article
Error: "CURLerror (curl_easy_perform() failed) - code=35 msg='SSL connect error'." when connecting to Snowflake.
View full article
How to connect to SQL Server Analysis Services (SSAS) and extract data in Alteryx Designer.
View full article
Alteryx doesn't read some unicode characters correctly
View full article
Error: "ORA-00900: invalid SQL Statement" occurs when running a procedure in the Pre or Post SQL Statement for Input or Output Data tools.
View full article
Error: "The account is locked" when running a workflow after a database password has changed.
View full article