Alteryx Designer Knowledge Base

Quick navigation for the Tool Mastery Series!

The TS Factory tools can build time series models and forecasts for multiple sets of historical data groups, without the need to separate them.  This is their relationship to the batch macro.

Alteryx provides product technical support for a period of eighteen (18) months after the Release Date of each Release Version, as outlined in the tables below.   NOTE: You can find product 'Release Version' details for all Alteryx Analytics Platform products by following the steps here.   Alteryx Designer & Server Release Version Detail Release Date End of Support (EOS) 2019.2.7.63499 7/9/2019 1/9/2021 2019.1.4.57073 2/13/2019 8/13/2020 2018.4.3.54046 11/14/2018 5/14/2020 2018.3.5.52487 10/1/2018 4/1/2020 2018.3.4.51585 8/27/2018 2/27/2020 2018.2.6 8/16/2018 2/16/2020 2018.1.6 7/17/2018 1/17/2020 2018.2.5.48994 7/5/2018 1/5/2020 2018.2.4.47804 5/31/2018 12/1/2019 2018.1.4.44311 4/2/2018 10/2/2019 2018.1.3.42973 3/6/2018 9/6/2019 11.8.3.40692 1/19/2018 7/19/2019 11.7.4.37815 11/28/2017 5/28/2019 11.5.1.31573 8/15/2017 2/15/2019 11.3.3.30523 7/14/2017 1/14/2019 11.3.2.29874 6/27/2017 12/27/2018 11.0.5.26351 3/21/2017 9/21/2018 11.0.3.25674 2/15/2017 8/15/2018 10.6.8.17850 7/12/2016 6/28/2018 10.6.6.17413 6/28/2016 12/28/2017 10.5.9.15014 5/5/2016 11/5/2017 10.1.7.12188 2/18/2016 8/18/2017 10.1.7.11834 2/4/2016 8/4/2017 10.1.6.11313 1/14/2016 7/14/2017 10.1.6.60263 11/30/2015 5/30/2017 Predictive Analytics 10/24/2015 4/24/2017 10.0.9.58949 9/26/2015 3/26/2017 10.0.9.58645 9/9/2015 3/9/2017 10.0.9.58529 9/3/2015 3/3/2017   Alteryx Connect Release Version Release Date End of Support (EOS) 2019.2 6/7/2019 12/7/2020 2019.1 2/13/2019 8/13/2020 2018.4 11/14/2018 5/14/2020 2018.3.0  8/27/2018 2/27/2020 2018.2.4.47804 5/31/2018 12/1/2019 3.0.0_0c4cae69 3/6/2018 9/6/2019 2.0.0_05b4e5c2 11/28/2017 5/28/2019 1.0.1.31573 9/12/2017 3/12/2019 1.0.0.31573 8/15/2017 2/15/2019   Alteryx Promote Release Version Version Information Displayed in Product Release Date End of Support (EOS) 2019.2.0 v2019.2.1 - Build cf6851d 6/7/2019 12/7/2020 2019.1.0 v2019.1.0 - Build f8ae666 2/13/19 8/13/2020 2018.4.1 v2018.4.1 - Build 167a0f1 12/4/2018 6/4/2020 2018.4.0 v2018.4.0 - Build 5926960 11/14/2018 5/14/2020 2018.3.1 v2018.3.1 - Build d88f0a6 10/1/2018 4/1/2020 2018.3.4.51585 v2018.3.0 - Build c14dfc7 8/27/2018 2/27/2020 2018.2.4.47804 v2018.2.0 - Build 593b5b29 5/31/2018 12/1/2019 2018.1.3.42973 v2018.1.0 - Build 2bfb396 3/6/2018 9/6/2019   Alteryx Analytics Product Compatibility Policy Alteryx is committed to ensuring that workflows created in legacy versions of Alteryx Designer will continue to work as expected with newer versions of Alteryx Designer. Alteryx will identify any known workflow compatibility issues. With the release of 11.7, a user may convert workflows created in a newer version of Alteryx Designer for use in an older version of Alteryx Designer. In this 'downgrade' scenario, a dialog appears asking the user to confirm or cancel the conversion process. Conversions performed in this manner are not fully tested for compatibility. For Alteryx Designer users who also use Alteryx Server, Alteryx is also committed to ensuring that in an upgrade scenario, legacy versions of Alteryx Designer are able to successfully connect to and use the newest Alteryx Server version. Therefore, it is always recommended to upgrade Alteryx Server first and the Alteryx Designer installations are upgraded thereafter. Alteryx will identify any known upgrade compatibility issues. If you experience any issues with an upgrade, please visit alteryx.com/support.   Alteryx Designer Predictive Tools Compatibility Policy Alteryx Designer users can install predictive tools for use with open source R, or Microsoft R. This table details the versions compatible with each release of Alteryx Designer.   Alteryx Designer Version Standard R Version RRE - Revolution R Enterprise (renamed as Microsoft R Server in 2016) Microsoft R Client (MRC) Microsoft R Server (renamed as Microsoft Machine Learning Server in 2018) Microsoft Machine Learning Server (MMLS) 2019.2 3.5.2 Deprecated by vendor - Not supported 3.5.2 Deprecated by vendor - Not supported 9.4.7 2019.1 3.4.4 Deprecated by vendor - Not supported 3.4.3 Deprecated by vendor - Not supported 9.3 2018.4 3.4.4 Deprecated by vendor - Not supported 3.4.3 Deprecated by vendor - Not supported 9.3 2018.3 3.4.4 Deprecated by vendor - Not supported 3.4.3 Deprecated by vendor - Not supported 9.3 2018.2 3.4.4 Deprecated by vendor - Not supported 3.4.3 Deprecated by vendor - Not supported 9.3 2018.1 3.3.2 Deprecated by vendor - Not supported 3.3.2 9.0/ 9.1 NA 11.8 3.3.2 Deprecated by vendor - Not supported 3.3.2 9.0/ 9.1 NA 11.7 3.3.2 Deprecated by vendor - Not supported 3.3.2 9.0/ 9.1 NA 11.5 3.3.2 Deprecated by vendor - Not supported 3.3.2 9.0/ 9.1 NA 11.3 3.3.2 Deprecated by vendor - Not supported 3.3.2 9.0/ 9.1 NA 11.0 3.3.2 Deprecated by vendor - Not supported 3.3.2 9.0/ 9.1 NA 10.6 3.2.3 8.0 Not supported NA NA     Alteryx Analytics Platform Hardware and Operating System Requirements Product Chip Disk Size Machine OS Processor RAM Designer Quad core (single chip) 500GB - 1TB Minimum: 64-bit, High Performance: 64-bit, 32-bit not supported Microsoft Windows 7 or later (64-bit) 2.5GHz or faster 8GB;16GB Connect Quad core (single chip) 100GB Recommended: 64-bit, 32-bit not supported Microsoft Windows Server 2008R2 or later 2.5GHz or faster 8GB Promote Quad core (single chip) 100GB Required: 64-bit, 32-bit not supported Linux CentOS 7 2.5GHz or faster 16 GB Server Quad core (single chip) 1TB Recommended: 64-bit, 32-bit not supported Microsoft Windows Server 2008R2 or later 2.5GHz or faster 16GB;32GB   Supported Browsers for Alteryx Analytics Platform   Alteryx Analytics is supported on the following versions of Chrome, Safari, Firefox, Internet Explorer and Edge web-browsers*:       Chrome - Windows Safari - MacOS Firefox Standard Release Internet Explorer Edge Alteryx Analytics Platform latest 11 and above latest (60 and above for Firefox ESR) 11 and above latest         *Note: from time to time, the vendor may provide an update to its web-browser that results in compatibility issues with the browser version used by Alteryx in the development and pre-release testing of the Alteryx platform. Alteryx will use reasonable efforts to mitigate against this risk but we also encourage you to be mindful of browser versions used within your organization and to manage your deployment of the Alteryx platform accordingly.   Alteryx Virtual Environment Support Nutanix, Azure, AWS, VMWare, GCP. All of Alteryx's products run in modern virtualized environments that are properly configured. Support also depends on using a supported and properly configured Windows operating system that also meets or exceeds minimum OS hardware environments. Alteryx Server MongoDB Support Policy Alteryx Server users have two options for managing user and instance metadata. 1) Use the version of MongoDB embedded in the server installation 2) BYO (Bring Your Own) Mongo DB instance Alteryx ships a version of MongoDB in product <OR> customers can connect to their own version. In the case of the latter, Alteryx doesn't provide support, but we do ensure that users are able to successfully connect to their own existing instance of MongoDB and the expectation is that users will be able to connect to that MongoDB instance and manage their Server users and metadata from there.   Release Version Release Date End of Support (EOS) Version of MongoDB embedded Certified versions of MongoDB supported to connect to user managed instances 2019.2.7.63499 7/9/2019 1/9/2021 MongoDB version 3.4 MongoDB version 3.0, 3.4, and 4.0 2019.1.4.57073 2/13/19 8/13/2020 MongoDB version 3.4 MongoDB version 3.0 and 3.4 2018.4.3.54046 11/14/2018 5/14/2020 MongoDB version 3.4 MongoDB version 3.0 and 3.4 2018.3.5.52487 10/1/18 4/1/2020 MongoDB version 3.4 MongoDB version 3.0 and 3.4 2018.1.6 7/17/2018 1/17/2020 MongoDB version 3.4 MongoDB version 3.0 and 3.4 2018.2.5.48994 7/5/2018 1/5/2020 MongoDB version 3.4 MongoDB version 3.0 and 3.4 2018.2.4.47804 5/31/2018 12/1/2019 MongoDB version 3.4 MongoDB version 3.0 and 3.4 2018.1.4.44311 4/2/2018 10/2/2019 MongoDB version 3.4 MongoDB version 3.0 and 3.4 2018.1.3.42973 3/6/2018 9/6/2019 MongoDB version 3.4 MongoDB version 3.0 and 3.4 11.8.3.40692 1/19/2018 7/19/2019 MongoDB version 3.0 MongoDB version 3.0 11.7.4.37815 11/28/2017 5/28/2019 MongoDB version 3.0 MongoDB version 3.0 11.5.1.31573 8/15/2017 2/15/2019 MongoDB version 3.0 MongoDB version 3.0 11.3.3.30523 7/14/2017 1/14/2019 MongoDB version 3.0 MongoDB version 3.0 11.3.2.29874 6/27/2017 12/27/2018 MongoDB version 3.0 MongoDB version 3.0 11.0.5.26351 3/21/2017 9/21/2018 MongoDB version 3.0 MongoDB version 3.0  

How to handle metadata with Python tool.

Some time ago, there was a nice writeup: The Ultimate Alteryx Holiday gift of 2015: Read ALL Excel Macro: Part 2. This amazing macro allowed me to read any excel file, regardless of the number of tabs.   Until I start working with users that use diacritics on the sheet names.     For example:   If we try to use the mentioned macro, you will receive an error like this: ‘not a valid name’ I decided to approach this as a macro (2 levels) and use the Directory functionality to read all possible xls files within a folder.   Level 1: Read xls Tabs   This macro will read all the tabs for a single xls file. I used an R tool that includes the library readxl.   This library allows us to read xls files. I used the excel_sheets function to extract the sheet name and compile the sheet name with the name file path. You will receive a column per tab that the xls file has. I cleaned these two values and passed them as Path and Tab.     This data is sent to the Read xls file macro.     Level 2: Read xls Files   This macro gives structure to the full path (Path + Tab) using the structure needed in xls files. It uses the Dynamic Input tool to dynamically choose the data and output its content.       Note: Update the XXXX for your corresponding paths Don’t forget to install the R library readxl under your %Program Files% path g. C:\Program Files\Alteryx\R-3.5.3\library

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

"Unable to find connection 'x' " when workflow is scheduled   When running a workflow via the Scheduler (for Designer with Automation), the following error is observed:   Unable to find connection "x"   Environment   Alteryx Designer Designer with Automation Windows Operating System In-Database Connection   Diagnosis   1. Confirm that you are using Designer with Automation and not Alteryx Server. You can confirm this by opening the Alteryx System Settings from Designer under Options > Advanced Options > System Settings. On the Setup Type page you will see Designer and Scheduler Only selected.   2. Confirm the In-Database connection is setup as a User connection. You can check this from Designer by navigating to Options > Advanced Options > Manage In-DB Connections and choosing the Data Source and Connection name you are using. It will show next to the name of the Connection:     Alternatively, you can check in the drop-down for the Connection Name Connect In-DB tool or the Data Stream In tool:       Cause   The In-Database connection in use is a User connection; scheduling requires a System connection or a File connection.     Solution A - System Connection   Follow the steps in this article to set up a System connection: How To: Create an In-Database Connection This will require admin permissions. Please see the following article for more information: Unable to create System Connection/System Connection type missing   Solution B-  File Connection   Follow the steps in this article to set up a File connection: How To: Create an Alteryx In-DB Connection File The .indbc file will need to be available to the Run As User or the user running the Alteryx Service. To avoid any issues, you can package the workflow, then schedule as follows: Package the workflow by going to Options > Export Workflow, making sure you check the box to include the .indbc file Go to Options > View Schedules On the Workflows tab, click the + icon Navigate to the .yxzp file you created above and set the schedule frequency     Additional Resources   Database Connections: Creating an alias and the advantages of using an alias Database Issues – Working with Alteryx Customer Support Engineers (CSEs)

  The Tree Interface can be a useful way to allow a user to select input values for an app.  Since sometimes setting up the Tree File Data Source can be a little tricky to those new to this interface, this example will step through the creation of the Data Source for a simple Tree Interface.   To use a Custom File or Database as the source for the Tree Interface tool, the source needs to be in a specific format: a table with a Description and a Key field.  It will look something like this:       And result in an interface that looks like this:       Let’s start with our original data, some very pretend pet statistics:         The first step is to determine the fields that will be used in the interface; in this case, we want to be able to select the fields Pet, Breed, and Year in the Tree Interface. These will become the different levels in the interface.           Next, we need to determine the level in which our fields of interest will appear in the tree -- the Pet field being the most general and Year being the most detailed. Sorting in this order will make sure all the data is aligned properly. All the Cat records will be together, then all the Breed records will be together, and finally all year records.       Once the data is sorted, unique identifiers need to be created for each record to establish the hierarchy.    The first level in the hierarchy is the Pet field. To create an identifier for each unique value in the Pet field, the Tile tool can be configured to look for Unique Values on the Pet field.  The unique value for the Pet field will be in the Tile_Num field.       This process needs to be repeated for the Breed and Year fields.  The Tile tool for the Breed field will again be configured to Unique, but this time under Unique Fields Pet and Breed will be selected.         Finally, Year.       For times when there are 10 or more levels in a Tree Tool, please see the Spoiler below: If there are 10 or more levels that need to be created for the Tree one more step will need to be done in order for the Tree Tool to differentiate each level.  For 10 or more levels you will want to apply the PadLeft() function to each level to give a buffer to each value for each level.  After the Tile tools used to create the key for each level use a Select tool to change the values to a string, then add a Multi-Field Formula tool to apply the PadLeft() function to each Tile_Num field: Adding the padding to the front of each level number will allow the concatenated values of all levels to be unique and should not cause issues when working with 10 or more levels in a Tree Interface. An additional workflow is attached that demonstrates adding the Padleft() portion, Tree Data Source 10 or more levels.yxmd (version 2018.4).     A little cleanup was done using a Select Tool. Three things were done: all the Tile_Sequence fields were removed, the Tile_Num fields were renamed to the appropriate Level number to make things a little easier in subsequent steps, and each Level field was changed to a string so they could be concatenated in the next step.   Now we have all the information we need to build a key for each level of our data for each record.  A Formula tool is used to create 3 new fields, one for a key at each level. Our Level 1 Key will just be the value from the Level 1 field.  The Level 2 Key will be the Level 1 Key concatenated with the Level 2 field, and the Level 3 Key will be the Level 2 Key concatenated with the Level 3 field.          Now that there is a key for each level we can construct a table that has the necessary Description and Key fields. Using a set of Select tools, select each Level Key field with its corresponding description field; Pet and Level 1 Key, Breed and Level 2 key, Year and Level 3 Key.             Now Union the three Select tools together by position.  Add a summarize tool and group by Pet and Level 1 Key.  Grouping by these fields will remove any duplicate records. The resulting fields were also renamed to Description and Key in the Summarize tool.      Finally, a Sort tool is added to sort the Key field in ascending order.  The results from the sort can then be saved to a file or loaded into a database and used in the Tree Interface tool.         The entire workflow:         Attached is the workflow used to build the Key list, as well as a very simple app that demonstrates the resulting tree created from the key values.

Handling Null Values in Databases In relational databases a null value is used to represent a missing or unknown value in the column. The ANSI SQL-92 specification defines the handling of the null value in databases.      SQL Ternary Logic SQL relies on a three valued logic. Additionally to true and false logical expressions can also yield unknown.  This is a consequence of SQL's support of NULL to mark either absent or unknown data. Thus, if NULL is part of a logical expression the outcome will be NULL. In more colloquial terms NULL means "it could have any value".   Therefore, in all the below cases the result will be unknown:   NULL = NULL NULL = 1 NULL <> 1 NULL > 1   Please note that the SQL standard does not specify how NULL values should be ordered in comparison with non-NULL values.   Testing for NULL From the above it emerges that a specific SQL command is needed to check whether a value is indeed NULL. SQL has the <expression> is null and <expression> is not null expressions to ascertain an expression is NULL or not.   The SQL standard also defines an expression to compare two NULL values treating them the same. However, not all SQL flavors support it and may instead have their own proprietary alternative. The SQL standard specifies <expression> is not distinct from <expression>.   Where and Having Clauses A Where clause needs to be true for the SQL query to execute.  Therefore if the condition in the Where clause will evaluate to unknown it will reject all rows. For instance   SELECT c_columns FROM t_table WHERE c_columns = NULL   will reject all columns. In order to use NULL in Where clauses WHERE c_columns is NULL should be used instead.   It is important to note that since NULL is neither true nor false, but rather unknown in SQL logic the below query will never return NULL values.   SELECT c_columns FROM t_table WHERE c_columns = 'ANY VALUE'   Additional Resource   Handling Null Values - Microsoft help documentation 

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. 

Issue - Unable to connect to Salesforce Output tool   When connecting to the Salesforce Output tool, the following error is observed and an empty red box appears:   Error: Salesforce Output (8): Tool #92: Error trying to retrieve access token. HTTP/1.1 302 Found... Data from server:<html><head><meta http-equiv="Content-Type" content="text/html;charset=utf-8"/><title>Error 405 Only POST allowed</title></head><body><h2>HTTP ERROR 405</h2><p>Problem accessing /services/Soap/u/34.0. Reason:<pre>Only POST allowed</pre></p><hr /><br/><!-- Body events --><script type="text/javascript">function bodyOnLoad()if(window.PreferenceBits)window.PreferenceBits.prototype.csrfToken="null";;function bodyOnBeforeUnload()function bodyOnFocus()function bodyOnUnload()</script> </body></html><!--............................................................................................................................................................................................................................................................................................................................................................................................................-->       Environment   Alteryx Designer Version 10.5+ Salesforce Output Tool   Cause   Salesforce Lightning URLs are not supported. Lightning URLs take the following format:  https://mycompany.lightning.force.com   Solution   Use a non-lightning URL. This can be provided by your Salesforce administrator and as looks as follows: https://na7.salesforce.com/     Additional Resources   Salesforce Tools The 'How to Guide' to the Salesforce Connector

Python Tool Doesn't Show Any Results or Errors on Run   When running the Python tool in Alteryx, the output is blank, and no results or errors are shown.   Python may have been previously installed by another app (e.g., Anaconda)   Environment   Product - Alteryx Designer   Diagnosis   To ensure the issue is with the Python tool in Alteryx, create a simple 2-tool workflow with test data and code as below. Click Run in the Python tool and verify the tool returns no output and no errors.   Step 1 - Run the workflow with a Text Input Tool and Python code as below   Step 2 - Verify that the Alteryx engine reports no errors     Step 3 - Verify that the Browse tool shows no data available   Cause   The IPython kernel being called by the Jupyter Notebook may be referencing a previously installed or non-existent Python binary, rather than the Python binary installed with Alteryx.    Solution   Open an Administrator Command Prompt and navigate to: Admin Version of Alteryx: C:\Program Files\Alteryx\bin\Miniconda3\PythonTool_venv\Scripts Non-Admin Version of Alteryx: %LocalAppData%\Alteryx\bin\Miniconda3\PythonTool_venv\Scripts Enter the command: jupyter kernelspec list  Navigate to the directory returned in step (2) in a File Explorer. If you have multiple directories, repeat steps 3-4 for each directory. Open kernel.json in a Text Editor and verify that the first item in the argv list references the python.exe in the same directory as the directory from (1) or simply "python" in cases where the directory from (1) is included in your PATH Environmental Variable. To test if you have a valid argument, you can simply try entering the argument in a command prompt and it should open a Python shell.   Additional Resources   Jupyter Troubleshooting

Alteryx has the ability to connect with MIT Kerberos based Impala implementations. With this feature, came the need to tell the Simba Impala driver that you are using Windows Kerberos and not MIT's version.

How To: Create an In-Database (In-DB) Connection   Apart from making standard database connections, which allow for data to be pulled from the database directly into Alteryx, Designer also has In-Database functionality. The In-Database tools allow for the workflow created to be converted into a query which will then be executed on the database, and not locally in Designer.     Prerequisites   Alteryx Designer Windows Operating System   Procedure   In Designer, drag and drop the Connect In-DB tool (located in the In-Database tool palette) onto the canvas Select the “Manage Connections…” option to establish a new In-DB connection The Manage In-DB Connections window should appear. To configure this window: Select the Data Source/Database type from the Data Source  drop-down. Under Connection Type, select User, System or File connection. For file connections, see this article: How To: Create an Alteryx In-DB Connection File If you do not see the System option available, see this article: Unable to create System Connection/System Connection type missing Under Connections, select New. Under Connection Name, enter a name for this connection. Under Driver, select the method of connection to use. Click the Connection String drop-down. You can choose to use an existing connection or create a new connection by clicking the New database Connection… option. You can also paste in the full connection string if you have it available. Repeat steps 5 and 6 for the Write tab. Click OK. If the connection was successful, the Choose Table or Specify Query window should appear.   The connection will now be stored in the Connection Name drop-down.     Additional Resources   Troubleshooting Database Connections FAQ: How Do the In-Database tools Work? Database Issues – Working with Alteryx Customer Support Engineers (CSEs)  

Issue   I am trying to set up a System alias, but the System option is missing.   Standard Connection - System connection is missing from Options > Advanced Options > Manage Data Connections > Add Connection    In-DB Connection - System connection is not an option:     Environment   Alteryx Designer Windows Operating System   Cause   The Designer is not running Elevated (aka running as an Administrator). Alteryx must be run with elevated privileges in order to be able to create a System Connection within Alteryx.      Solution   Right click on the Alteryx program (or on the Alteryx icon on your Desktop) and choose Run as administrator Please contact your IT department if you are unable to run Alteryx as an administrator     Additional Resources   Creating an In-Database Connection Database Connections: Creating an alias and the advantages of using an alias Database Issues – Working with Alteryx Customer Support Engineers (CSEs)

This article details different methods for connecting to an Oracle database from Alteryx. 

How To: Create an Alteryx In-DB Connection File   As users collaborate, the sharing of workflows that connect to databases can be helpful. The In-DB Connection File type allows for this. A database connection is saved as an .indbc file so it can be packaged with a workflow.   Prerequisites   Alteryx Designer   Procedure   1. In Designer, navigate to Options > Advanced Options > Alias Manager > In-DB Connections     2. Select the Data Source from the dropdown (1). For our example we will select Oracle, then pick File for the connection type (2), Click the elipses (...) button to navigate to a folder where the .indbc file will be stored. Please note that the first time you set up a connection file, you will need to name the file and click Open to create the file (4) then provide a name for this file (3).       Then proceed to set up your connection as you would normally do by selecting the appropriate driver and setting up the connection string for Read & Write.       3. Now that your connection file is created, the next step is to connect to your database using this file. Bring a Connect In-DB Tool onto your canvas, click on the dropdown for the Connection name and select Open File Connection and browse to your file     4. You can then select a Table, use the Visual Query builder, or type in SQL directly in the Choose Table or Specific Query window       5. (Optional) If you would like to share this workflow, package your workflow in Designer by going to Options > Export workflow. Notice that the .indbc file is being packaged with the workflow.       At the receiving end, the database drivers/client, data sources for that database should be installed and set up. The .indbc file looks like below, with the password encrypted.   Note: Workflow and all images created in this article are from Alteryx version 2019.2

Sometimes you look at the steaming pile of data before you and wonder how you’ll ever get it in the form you need. Every option seems to require a great deal of manual labor, and as a lazy– er that is , as a data blending professional , that is simply something you will not abide.