community
cancel
Showing results for 
Search instead for 
Did you mean: 

Alteryx Knowledge Base

Definitive answers from Designer experts.
Upgrade Alteryx Designer in 10 Steps

Debating whether or not to upgrade to the latest version of Alteryx Designer?

LEARN MORE
  Occasionally you may see one of these errors from the Join Multiple tool.  It is a result of Cartesian joins.   A Cartesian join is when you join every row of one table to every row of another table. You can also get one by joining every row of a table to every row of itself. A Cartesian join is very CPU intensive.   For example, if you have four files and each file has the same ID in it twice, that means it will join 2*2*2*2 times on the ID (the field on which you're joining is the key referenced in the error; in this example, it's Field1, and the duplicated value is 12345).  The same can be caused by multiple nulls in each file. After your data prep and investigation, and when you know your data are correct, your choices on how to handle Cartesian joins include:   Allow multidimensional joins: The multidimensional join will occur with no error or warning reported. Warn on multidimensional joins of more than 16 records: A warning will be reported in the Results window that a multidimensional join has occurred. Error on multidimensional joins of more than 16 records: An error will be reported in the Results window that a multidimensional join has occurred and downstream processing will stop.     Happy Alteryx-ing!
View full article
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  
View full article
Platform Product: Fuzzy Matching Issues – Working with Alteryx Customer Support Engineers (for use by CSEs and Alteryx Customers)   To EXPEDITE the resolution of your case, please include the below information.   Fuzzy Matching- Requested Information *** Suggestion: copy/paste the questions below and email the supporting documentation to support@alteryx.com   1. Detailed Description of the Issue 2. Screenshot of Alteryx Version 3. Screenshot of Error  4. What dataset and vintage are you using? 5. Please send a copy of your workflow (*.yxmd or *.yxzp) and sample data if possible.   Fuzzy Matching – Requested Information (Detailed Instructions):   1.  Detailed Description of the Issue – What issues are you having?  Has it worked in the past?  When did the issue start?  Are all users affected or just some?  What are the steps to reproduce your issue?  What have you tried to resolve the issue?  Have you searched the Alteryx Community  using the Fuzzy Match label?     2.   Screenshot of Alteryx Version– Our CSEs need to know the precise version of Alteryx so we can replicate any issues.   In Alteryx, click Help >> About and provide a screenshot.  The screenshot will include whether it is Server or Designer.  In addition, whether it is “Running Elevated” Admin vs. Non-Admin.       3.  Screenshot of Error or Exact Text of Error- Click CTRL-Print-screen to capture the error and paste into your e-mail.  Also include where was the error encountered – Gallery, Designer, Scheduler?   Note: You may wish to Google the error text research the issue. The Knowledgebase is also a great place to search the error text as well!       4.  What dataset and vintage are you using?  From the Allocate Input tool, click the drop down for Choose a Dataset.  What dataset is selected?  If “Most Recent Vintage,” what is the dataset below?  e.g. Experian US 2018A (Q4 2018)       5.  Please send a copy of your workflow (*.yxmd or *.yxzp) and sample data if possible. Either create a .yxzp and include macros and data by clicking Options>Export Workflow.  Or, include the workflow *.yxmd and sample data if possible.         Suggested links: Tool Mastery | Fuzzy Match Keyword Fuzzy Matching Strings: Clean Human Entered Data Tips and Tricks for Fuzzy Matching  
View full article
Platform Product: Connectors Issues – Working with Alteryx Customer Support Engineers (CSEs) (for use by CSEs and Alteryx Customers)   To EXPEDITE the resolution of your case, please include the below information.   Connectors - Requested Information *** Suggestion: copy/paste the questions below and email the supporting documentation to support@alteryx.com   1. Detailed Description of the Issue 2. Screenshot of Alteryx Version 3. Screenshot of Error  4. What is your Connector Type and Version? 5. Screenshot of your Configuration in Connector Tools 6. Additional information for API connectors (user-created custom connectors) 7. Have there been any changes made recently? Update to Alteryx, Server, etc.?   Connectors Requested Information (Detailed):   1.  Detailed Description of the Issue – What issues are you having?  Has it worked in the past?  When did the issue start?  Are all users affected or just some?  What are the steps to reproduce your issue?  What have you tried to resolve the issue?  Have you searched the Alteryx Community  using the Connectors label?     2.   Screenshot of Alteryx Version – Our CSEs need to know the precise version of Alteryx so we can replicate any issues.   In Alteryx, click Help >> About and provide a screenshot.  The screenshot will include whether it is Server or Designer.  In addition, whether it is “Running Elevated” Admin vs. Non-Admin.       3.  Screenshot of Error or Exact Text of Error- Click CTRL-Print-screen to capture the error and paste into your e-mail.  Also include where was the error encountered – Gallery, Designer, Scheduler?   Note: You may wish to Google the error text research the issue. The Knowledgebase is also a great place to search the error text as well!      4.  What is your Connector Type and Version? Do you have Tableau?  Salesforce?  Other?  What is the version?  The version of tool if applicable (right click on the tool)?     5.  Screenshot of your Configuration in Connector Tools- Click CTRL-Print-screen to capture the error and paste into your e-mail.     6.  Please send a copy of your workflow (*.yxmd or *.yxzp) and sample data if possible. Either create a .yxzp and include macros and data by clicking Options>Export Workflow.  Or, include the workflow *.yxmd and sample data if possible.         7.  Additional information for API connectors (user-created custom connectors) What is the URL for the API endpoint that fails? What is the Payload being sent to the API? What are the Postman results for the same API endpoint and payload? What is the link to API documentation?   Suggested links: The 'How to Guide' to Publishing to Tableau Cannot find macro: Publish To Tableau Server The 'How to Guide' to Google Analytics Guide to Creating Your Own Connector Series The 'How to Guide' to the Salesforce Connector Google Big Query Tools Tool Mastery | One Drive
View full article
Platform Product: Engine Issues – Working with Alteryx Customer Support Engineers (CSEs) (for use by CSEs and Alteryx Customers)   To EXPEDITE the resolution of your case, please include the below information.   Engine - Requested Information *** Suggestion: copy/paste the questions below and email the supporting documentation to support@alteryx.com   1. Detailed description of the Issue 2. Is this a Production Issue? What is the urgency? 3. Have there been any changes made recently? Update to Alteryx, Server, etc.? 4. Alteryx Version? Server, Connect or Designer? 5. Engine Logs and ErrorLogs folder from the workstation/server where the failure occurs 6. Copy of the workflow with sample data if possible   *** Engine issues should be strictly failure returned by the EngineCmd process during execution of the workflow/app. If there is doubt you can always consult a member of the team to confirm.   Engine– Requested Information (Detailed Instructions): 1.  Detailed Description of the Issue – What issues are you having? Has it worked in the past?  When did the issue start?  Are all users affected or just some?  What are the steps to reproduce your issue?  What have you tried to resolve the issue?  Have you searched the Alteryx Community ?     2.   Is this a Production Issue? What is the urgency? How many people is this affecting?  Are you able to complete most of your work?  Do you have a time frame that you need to resolve the issue?     3.  Have there been any changes made recently? Update to Alteryx Designer, Server, etc.?  What do you think may have caused the issue?  What have you done to try to resolve the issue?     4.  Alteryx Version – Our Customer Support Engineers need to know the precise version so we can replicate any issues.   In Alteryx, click Help >> About and provide a screenshot or the exact version number.     5.  Engine Logs for the workflow failure (and success if possible) and ErrorLogs folder from the workstation/server where the failure occurs. Logs are the best way for us to get to the root of the problem.  We look at errors and warnings. For the Alteryx logs (Gallery, Service, and Engine), please include the logs that reflect the time of the error/crash (the logs immediately before and after the error/crash).  Before sending the logs, recreate the issue, and then send the latest logs.  Include Alteryx_Log*.log files and Alteryx Engine ErrorLogs   Default Paths:  C:\ProgramData\Alteryx\Engine C:\ProgramData\Alteryx\ErrorLogs\AlteryxEngine (from the workstation/server where the failure occurs)   If you have Server, and do not have logs in the pathways above, click Options >> User Settings >> System Settings, and note the paths that the logs are written to. Then locate and send the logs from that location. If the path is not yet set, pick a path, rerun the workflow to create the error, and then send the logs:   Locating the path of your Engine logs:     If you aren't using Server, you're probably using a Desktop Automation (Scheduler) installation that has logs located in C:\Program Data\Alteryx\Engine.  However, if you have Desktop Automation (Scheduler) and do not have logs in this pathway, click Options >> User Settings >> System Settings, and note the paths where the logs are pointed. Then locate and send the logs.  If the path is not set yet, pick a path, re-run the workflow to create the error, and then send the logs. If there is not a directory, check "Override System Settings", and enter a path for “Logging Directory."  Rerun your workflow to create the error and send the new log files.                 Check out  this resource  for more information on Alteryx logs! 6.   Please send a copy of your workflow (*.yxmd or *.yxzp) and sample data if possible. Either create a .yxzp and include macros and data by clicking Options>Export Workflow.  Or, include the workflow *.yxmd and sample data if possible.         Suggested links: The Alteryx Engine 101 - The Basics  
View full article
Platform Product: Macros/Apps Issues – Working with Alteryx Customer Support Engineers (for use by CSEs and Alteryx Customers)   To EXPEDITE the resolution of your case, please include the below information.   Macros/Apps - Requested Information *** Suggestion: copy/paste the questions below and email the supporting documentation to support@alteryx.com   1.  Detailed Description of the Issue 2.  Screenshot of Alteryx Version 3.  Set to “Show All Macro Messages” on the Workflow Configuration, run workflow and send a screen shot 4.  Please send a copy of your workflow and macro (*.yxmd or *.yxzp)   Macros/Apps – Requested Information (Detailed Instructions):   1.  Detailed Description of the Issue – What issues are you having? Has it worked in the past?  When did the issue start?  Are all users affected or just some?  What are the steps to reproduce your issue?  What have you tried to resolve the issue?  Have you searched the Alteryx Community  for apps and macros? 2.  Our CSEs need to know the precise version of Alteryx so we can replicate any issues.   In Alteryx, click Help >> About and provide a screenshot. The screenshot will include whether it is Server or Designer.  In addition, whether it is “Running Elevated” Admin vs. Non-Admin.       3.  Set to “Show All Macro Messages” on the Workflow Configuration, run workflow and send a screen shot Click the Workflow Configuration>Runtime tab and check “Show All Macro Messages”.  Run the workflow, and send a Screenshot of Error or Exact Text of Error - Click CTRL-Print-screen to capture the error and paste into your e-mail.        Note: You may wish to Google the error text research the issue. The Knowledgebase is also a great place to search the error text as well!      4.  Please send a copy of your workflow (*.yxmd or *.yxzp) and sample data if possible. Either create a .yxzp and include macros and data by clicking Options>Export Workflow.  Or, include the workflow *.yxmd and sample data if possible.           Suggested links: Tool Mastery | Apps and Macros Tool Mastery | Macro Input
View full article
Platform Product: Predictive Issues – Working with Alteryx Customer Support Engineers (CSEs) (for use by CSEs and Alteryx Customers)     To EXPEDITE the resolution of your case, please include the below information.   Predictive - Requested Information *** Suggestion: copy/paste the questions below and email the supporting documentation to support@alteryx.com   1.  Detailed Description of the Issue 2.  Screenshot of Alteryx Version 3.  Version of R 4.  Version of Predictive Tool 5.  Ensure not a data issue 6. Set to “Show All Macro Messages” on the Workflow Configuration, run workflow and send screen shot 7.  Please send a copy of your workflow and macro (*.yxmd or *.yxzp) 8.  For R Tool – work outside of Alteryx? Provide code 9.  Engine Log (if applicable)   Predictive – Requested Information (Detailed Instructions):   1.  Detailed Description of the Issue – What issues are you having?  Has it worked in the past?  When did the issue start?  Are all users affected or just some?  What are the steps to reproduce your issue?  What have you tried to resolve the issue?  Have you searched the Alteryx Community  using the R label or the Predictive label?     2.  Screenshot of Alteryx Version– Our CSEs need to know the precise version of Alteryx so we can replicate any issues.   In Alteryx, click Help >> About and provide a screenshot.  The screenshot will include whether it is Server or Designer.  In addition, whether it is “Running Elevated” Admin vs. Non-Admin.         3.  Version of R – Go to C:\Program Files\Alteryx to find the Version number         4.  Version of Predictive Tool – To find the version number, right click on the Predictive tool, and click Choose Tool Version.         5.  Set to “Show All Macro Messages” in the Workflow Configuration, run your workflow and send a screen shot Click the Workflow Configuration>Runtime tab and check “Show All Macro Messages”.  Run the workflow, and send a screenshot of the error or exact text of error - Click CTRL-Print-Screen to capture the error and paste into your e-mail.        Note: You may wish to Google the error text research the issue, especially since the majority of the errors from the R macros are from R itself, and not Alteryx Designer or Engine. The Knowledgebase is also a great place to search the error text as well!       6.  Ensure that it's not a data issue – Do you have NULL values in your data?  Are there unique identifiers as predictor variables?  Are the data types of variables appropriate?  Do you have enough records?  If we open your workflow and don't see a Field Summary tool, we're sending it back.     7.  Please send a copy of your workflow (*.yxmd or *.yxzp) and sample data if possible. Either create a .yxzp and include macros and data by clicking Options>Export Workflow.  Or, include the workflow *.yxmd and sample data if possible.         8.  For R Tool – work outside of Alteryx? Does your R code work outside of Alteryx?  What IDE are you using (RStudio, Microsoft R Client)?  What is the version of the IDE?  Are you using custom packages? Please provide the code.     9.  Engine Log (if applicable) Engine Logs are a great way for us to get to the root of the problem. We look at errors and warnings. For the Alteryx Engine logs, please include the logs that reflect the time of the error/crash (the logs immediately before and after the error/crash).  Before sending the logs, recreate the issue, and then send the latest logs.  Use Alteryx App - Server Logs the easy way! OR… Default Paths: Engine Logs (\ProgramData\Alteryx\ErrorLogs)   If you have Server, and do not have logs in the pathways above, click Options >> User Settings >> System Settings, and note the paths that the logs are written to. Then locate and send the logs from that location. If the path is not yet set, pick a path, rerun the workflow to create the error, and then send the logs:    Locating the path of your Engine logs:     Suggested links: One Stop Shop for Predictive Resources  
View full article
Having trouble reading or writing Microsoft Access files? No worries - Client Services is here to help!
View full article
The Email Tool is a tremendously useful shortcut when it comes time to disseminate your analyses and other results straight from your workflow. However, in order to do so, it must communicate using Simple Mail Transfer Protocol (SMTP), which is often restricted by IT infrastructure and firewalls to protect organizations from spam. As a result, many users excited to try the tool get the direct, yet demoralizing, error below (among others): “SMTP Failed.”     That’s why we’ve detailed in this article the steps you can take to investigate what, exactly, is giving you trouble: Manually-entered SMTP server   First make sure a colon and port number are appended to the server name: Does this SMTP server use SSL/TLS or require username/password authentication? Unless the SMTP server uses windows authentication you won’t be able to use the Email Tool, as SSL and TLS are not yet supported through the tool. You can, however, look into other approaches to sending emails in the Designer that can accommodate those requirements.   If not, do you have the required ports open in your network firewall? You can check with your IT team for port numbers and statuses, but the default ports you can check yourself are usually 25, 445, 465, 587, and 993: You can check to see if a server and port are open using the Telnet utility; if you have Telnet installed, open the command prompt and simply type telnet.     If you do not see the second prompt above then you’ll have to install a Telnet/SSH third party client like PuTTY.   From either the Telnet prompt or client, you can open a connection to the server and port to test: In Telnet, connect to the server and port using the command below.     In PuTTY, opening the port will look like the following.     Either approach will then send you to the following prompt.     Then use these commands ( <CRLF> is the enter key ) to send a test email that, if received, will indicate that your port is open. HELO <CRLF> mail from:<mail from address> <CRLF> rcpt to:<mail to address> <CRLF> data< CRLF> subject:<email subject here><CRLF> <CRLF> <type the body of the message here> <CRLF> . <CRLF> To send the email, you must end the body by hitting the enter key (<CRLF>), then period, then enter again (please note that after specifying your subject you must also press the enter key twice – not doing may neglect the message body argument). The test should look something like the below:   If the email sends and the mail to address confirms receipt, then your port is open. Otherwise, you should receive an error that should help your IT team diagnose why the traffic is being blocked. Use the steps above to determine likely causes for the error and you’ll be able to take steps to get the Email Tool unrestricted in your network. Once that happens, bid adieu to whatever repetitious emails you might have to send in the future!  
View full article
We are working diligently and intelligently on making connections to databases easier, more secure, and faster in Alteryx. Even when we can make the best possible experience for our users come to fruition, any user may still encounter some issues due to the use of third party drivers and/or the intricate communications between the database, driver, and Alteryx. To help to minimize those issues, Alteryx is tested with an abundance of "supported" databases and drivers that are proven to be compatible but, unfortunately, you just can't test every database and every driver out there. Our technical specifications page found here will show you those databases Alteryx supports, as well as the drivers we have tested and support with respect to each database. This does not mean Alteryx will not connect to a database or driver you do not see on this page (or links within the page), however, Alteryx can not support those databases and/or drivers if troubleshooting or setup is required.
View full article
The improvements in our salesforce connectors have been astronomical over the last year and now it is easier than ever to navigate the UI configuration screen and connect to your Salesforce Data!
View full article
‘Alteryx has stopped working’ - APPCRASH   Scenario: You are running a workflow and all of a sudden Alteryx becomes unresponsive and a windows prompt opens and says ‘Alteryx has stopped working’ with options to close the program. Once you click on problem signature properties it references 'Problem Event Name: APPCRASH'. This error can be due to several factors however there a few troubleshooting steps which have resolved this error for several of our clients in the past.   Are you on the latest version of Alteryx? If possible being on the latest version of Alteryx can help ensure any known bug fixes have been resolved and the software is up to date. To find the latest version of the Designer please click on this link Downloads   Limit the number of Browse tools Every time you add a Browse Tool to the canvas it caches the data locally, therefore if you have a large workflow this can sometimes cause memory issues on your machine (dependent upon your machine environment). This can be adjusted by changing the default sort/join memory, however taking advantage of the Browse Everywhere is highly recommended! Before removing all browses you can also 'Disable All Browse Tools' in the runtime configuration settings to test this theory.        Have you tried the block until done tool? When Alteryx becomes unresponsive it can be due to constraints on the processing power of the machine. More often than not you may receive an error relating to an ‘inbound pipe error’ (also memory related). The Block Until Done Tool (found in the developer category) allows all the pre-processing to occur before passing data downstream (e.g. writing out through an output tool). This often makes it an easier process when writing out to a database.   Adjust your sort/join memory The sort/join memory is one of the most underestimated elements of the designer. Because Alteryx is designed to use all the resources it possibly can, it tries to balance and use as much CPU, memory and disk I/O as possible. There are great tips on how to achieve the right balance here: http://community.alteryx.com/t5/Alteryx-Knowledge-Base/What-is-the-Sort-Join-Memory-Setting/ta-p/1302 Again, as always if this error persists after trying these troubleshooting steps, please do not hesitate to reach out at support@alteryx.com  
View full article
  You may be trying to install the Alteryx Designer or Server and receive an error saying: There was an error downloading "AlteryxInstallx64_VersionX.exe...."      This is due to a proxy blocking the data manager from installing the software.    DO NOT FEAR THE ANSWER IS HERE!   All you need to do is to install the Individual Installs of the Designer/Server/Predictive tools to circumvent the data manager GUI and you will be able to download the designer as normal.    Navigate to licenses.alteryx.com Log on to the downloads portal Download the relevant installer .exe files.     *****Please remember to download the correct bit and admin/non-admin version for your machine!    Once the download has finished it will prompt you to finish and open the designer. This is when you can enter your license key and use Alteryx!   If this fails to resolve your issues please do not hesitate to reach out to Support
View full article
A common error we see in Support is: "The temp drive is getting full. Free up some disk space or cancel." Here's how to fix it!
View full article
This error may occur when using the AlteryxGraph device. The reason for this is that the AlteryxGraph device creates a pipe between Alteryx and R. If creating graphs in a loop, a pipe has to be created for each loop which slows down the processing. As a result, Alteryx ends up trying to create the next graph before the previous one is completed. To avoid this, it is best practice when creating multiple graphs within a loop to keep the AlteryxGraph device statement outside of the loop.
View full article
The day will come.  You are on a deadline, you need some data, and it happens: you cannot open your workflow.     What now?  Your file has been corrupted somehow, and you need to restore it asap to meet your deadline.  Don't fret!  Here are two options:   Check your Autosaved files! It's possible you have a nearly complete version saved from the last time you worked on this module:  File > Open Workflow > Open Autosaved Files (there's even a timestamp!)     Your second option is a great example of what the .bak files are for (in case you were ever wondering). First, check to see if your .yxmd was indeed corrupted.  Right click your corrupted .yxmd in a windows explorer, and open with Notepad (or Notepad++ or a similar program).   At the end of every correct Alteryx workflow will be the tag </AlteryxDocument>     If your module is corrupted, it could end with anything – but the error message will tell you exactly where your file was truncated.  If you do not see that tag, here's what to do:  right-click the .bak file associated with your workflow, and simply rename the extension to .yxmd   Now, go meet that deadline!  Save early, save often, and Happy Alteryx-ing!
View full article
Some users have reported a problem when importing and exporting macros within the Alteryx Designer when the Regional Settings for the machine are not set to English (United Kingdom) or English (United States) (see screenshots below). You may also be unable to see personalized Macro folders within the Designer. They encounter the following error: "Input string was not in a correct format.”   The workaround for this is to switch the Regional Settings to the regions named above and you will then be able to import, export macros and see personalized macro folders within the designer categories.   The screenshots below demonstrate what the users will see when they try to import and export workflows with other Regional Settings than English (United Kingdom) or English (United States).               To find Region and Language settings in Windows 7, please navigate to the Control Panel>>>Clock, Language and Region>>Region and Language. For more information on Localization please see this link: http://community.alteryx.com/t5/Analytics-Blog/Alteryx-Commences-Localization-Endeavors/ba-p/11765.        
View full article
Unable to find the dll: "OCI.dll"   Within Alteryx this error will be prompted due to a mismatch between 32/64 bit drivers and the Alteryx bit version.  This error may also appear if you do not have the drivers installed.     One way to troubleshoot this is to find out what drivers you have installed!   You can use an input tool in the Alteryx Designer, go to Other Databases and select either ODBC/OleDB (64-bit) or 32-Bit Database Connections -> ODBC/OleDB. In the next pop out window it will populate with the available drivers for those connections. If you have no drivers in this pop out window this means you do not have the correct drivers for 32 bit or 64 bit connection dependent upon which one you chose.         Links to drivers are available from within individual data source pages here. This will take you away from the Alteryx website and onto the driver provider’s pages. Please consult with your IT to find the correct drivers for your environment.
View full article
Issue    The Alteryx server is unable to run a workflow that runs properly on the user’s local machine where the workflow was created.    [ODBC Driver Manager] Data source name not found and no default driver specified alteryx This error can be encountered when running an app or workflow on a Gallery:   Or when uploading a workflow during validation:   Users will also receive the following error when opening a shared workflow where the Data Source Name does not exist on the user’s local machine:       Environment   Alteryx Designer Alteryx Server  Version ≥  11.0 A workflow that contains a Data Source Name (DSN) on the Input Data tool.   Diagnosis   Confirm that the data source name (DSN) specified in the workflow is pointing to an existing DSN in your machine’s ODBC Data Source Administrator:   ***You must have the driver installed on the machine prior to using this guide. The download links to many of the drivers can be found here. On your local machine, search for ODBC Data Sources (64 bit) The DSN referenced in the input data tool within the workflow must be listed under either User DSN or System DSN tabs.   Cause   The workflow is not able to successfully run because the input data tool cannot reach the database in the following scenarios: The workflow creator sends a workflow with a database connection to a colleague who does not have the same DSN on their computer. The workflow gets sent to the alteryx server to run on a scheduled frequency where the DSN does not exist on the server machine.   Solution   You must have the driver installed on the machine prior to using this guide. The download links to many of the drivers can be found here. Once confirmed that the appropriate driver is installed, select to add from either the user DSN or System DSN tab. Generally, the User DSN is what most users will have access to and what is commonly used. You can learn more about the difference between User and System DSNs here. In order to resolve the error at the local level or on the Alteryx Server, you will need to set up the corresponding DSN found in the app/workflow. The following Community article will provide you step by step instructions on how to set up an ODBC connection . Once you've established the DSN on your machine, you will now be able to successfully re-run the workflow! 
View full article
In Alteryx Designer 2019.1, after adding Browse tools to all of the output anchors of a tool using Right-click > Add All Browses OR Ctrl + Shift + B, running the workflow returns an Unhandled Exception error. The workflow runs indefinitely until Designer is canceled from Windows Task Manager.
View full article