Alteryx Designer Desktop Knowledge Base

This article discussed about the Alteryx Connectors deprecation, for initial set of connectors, and clarifies the questions around the Connectors deprecation.

Guide on configuring and capturing a Fiddler trace for Troubleshooting issues.

How to install two versions of Designer on the same machine.

There may be a time when there is a need to gather more information on why the Alteryx installation/uninstallation fails. This article will show you how you can enable the installer log.

When using the CASS tool on the canvas it gives the error: "You have found a bug. Replicate, then let us know. We shall fix it soon."

How to improve performance when reading from or writing to Snowflake.

Information to know about connectors not connecting when a endpoint has Zscaler installed.

How to add a custom domain within the Salesforce Tools.

Instructions on how to disable the AMP Engine feature.

This article helps connect to Azure Data Lake (ADLS) Gen2 using ADLS connector

How to collect Wireshark traces to troubleshoot network-related issues.

One of the most underrated tool groups, the Documentation Category is full of gems that can help you improve the aesthetic, organization, and shareability of your workflows. Chief among them is the Tool Container Tool – in addition to better aesthetic this tool has the ability to disable all the tools within it, lending itself to a handful of functional applications as well:

This article addresses the replacement of PDF Input tool with the Image Input tool starting from 21.2 version of Alteryx Designer

The new authentication and encryption settings allow IT departments to have much greater control over the email tool. The settings in themselves are a big step towards preventing spoofing, but there is one step that must still be done on the SMTP server itself.

Procedures on how to configure Designer for input of large, zipped text files for processing.

The Tool Container is a tool that allows you to organize your module by placing tools inside of the Tool Container.  Because the Tool Container can be opened and closed without impacting the behavior of the tools they contain, you can effectively minimize sections of your module so as to bring greater clarity to the overall picture.  From a visual perspective, the Tool Container encourages object-oriented design! Another feature of the Tool Container is the ability to disable/enable an individual Container.  An example application for this is a module where you need to do some design/testing, but you do not want to write the Output file until everything is working properly.  By placing your Output tools inside of a Tool Container, and then disabling the container, you will be assured that no files will be generated.  Re-enabling the Output tools is a piece of cake; just uncheck the “Disabled” checkbox. This feature allows you to easily control the generation of Output files or the processing of portions of your module.  For users developing complex modules, the Tool Container delivers a powerful time-saving tool for the module design process.  

You can house an internet window or file location within your workflow - additional files, embedded help videos, etc.

Now everyone loves to talk about their workflow masterpieces, however the notion of documenting them doesn't always hold the same appeal. The Comment Tool would be happy to help and can make documenting and structuring your workflow easy and straight forward.  Whether you want to include images, text descriptions or categorize parts of your workflow, the Comment Tool can act as a great refresher when revisiting workflows and make it far more intuitive for work colleagues to follow along. This article provides a few examples on how.

The is a known defect where the Adobe Analytics tool is not referencing the parent directory where the macro is stored.

Now you can use the Email tool with G-Suite!