Alteryx Connect Knowledge Base

When running the Alteryx Teradata Metadata Loader in Connect, Teradata schema tables are not produced as expected.

In version 2022.1, we bring you the following enhancements.

Status 403 when running Tableau Loader as an app.

Removed Database servers entries in Data Sources assets are recovered by running Redshift_Loader

There is a known issue (TGAL-6268) with the Alteryx Gallery loader used to download workflows to Connect. When you try to load data from Alteryx Server using the GET admin/v1/workflows API endpoint, you get no results.

Take a look at the new features, fixes, and enhanacements now available in the newest realse of Connect!

When running metadata loader for Connect on Alteryx Server or Designer, an error occurs. This is an issue with versions 2021.2 and 2021.3.

The 2021.3 release brings several features such as the Custom Fields Position option, new metadata loader for Microsoft SharePoint online, and some more.

In this article, you will learn how to use and configure the metadata loaders in Connect. Until now, you probably have used the metadata loaders only from Designer, as described here.

The 2020.4 release brings several features such as Notification Queue, new Custom Field type, the Alteryx Designer Tool Details section for analytic workflows, many improvements for metadata loaders, and more.

Find out what new features, improvements, and bug fixes we released with this version of Connect! The 2021.2 release brings several new features such as expansion of the Health Checks section, option to prevent creating versions for already loaded content, and more.

In order to schedule the Metadata loader, you will need to configure and save the .yxwv file, and configure the ConnectScheduler workflow to run from the directory of the .yxwv file. Detailed steps listed below:   1. Open the Metadata loader in Designer, in this example the Files loader, fill in the information for the "Files to load" and "Alteryx Connect" tabs       2. Click Save button to save the .yxwv file in the default File Loader location - C:\ProgramData\Alteryx\AlteryxConnect\Files_Loader 3. Click Help > Sample Workflow > Alteryx Connect Metadata Loaders > ConnectScheduler 4. Click on the Directory input tool, select the root directory where the yxwv file(s) is saved, for example C:\ProgramData\Alteryx\AlteryxConnect 5. For the File Specification, leave it as *.*     6. Saved locally text   Schedule the loader using Local machine    1. To Schedule using local computer, complete steps 1 - 5 from above  2. Click Option > Schedule Workflow > My computer  3. Select Run the workflow from its original location on disk       Note: When the scheduler runs, it will run every metadata loader with .yxwv file one by one. If you only need to have one of the loaders scheduled, you need to have the Metadata loader moved into a folder other than C:\ProgramData\Alteryx\AlteryxConnect   Schedule the loader using the Alteryx Gallery   Save the ConnectScheduler to Gallery for Scheduling. instructions can be found in https://help.alteryx.com/connect/current/Administration/ScheduleLoaders.htm under Configure and test the Connect Scheduler > Step 6.   Tip: When scheduling loaders on Alteryx Gallery, we recommend to copying the metadata loader and save the .yxwv files into a share drive to avoid the situation where the Alteryx Server machine is unable to access the end user's machine. See steps below:   Steps: 1. Create a Folder called AlteryxConnect in a Share Drive 2. Copy the loader folder, for example Files_Loader from C:\ProgramData\Alteryx\AlteryxConnect to the Share Drive's AlteryxConnect 3. Complete steps 1-2 from above but save the .yxwv file into the share drive under AlteryxConnect\Files_loader 4. Open ConnectScheduler from Help > Sample Workflow > Alteryx Connect Metadata Loaders  5. In the Directory Input tool, select the Path of AlteryxConnect in the Share Drive, make sure it is the UNC path 6. Save ConnectScheduler, and it is ready to be schedule         

While attempting to add your Gallery (Alteryx Server) to your Connect instance you may get an error about related to your SSL certificate. This article provides step-by-step instructions for troubleshooting this issue.