Showing results for 
Search instead for 
Did you mean: 

alteryx connect Knowledge Base

Definitive answers from Connect experts.

New in Connect 2019.1

Created on

The 2019.1 release of Alteryx Connect brings several new features worth mentioning and explaining in a bit more detail.


New Configuration Options


Customize the Number of Live-Search Results

You can now specify how many results you want users to see in the live-search. The default value is 7, but if you have a large screen, why not get 15? You can change this value in Administration > Connect Configuration > Instance Settings.


Adjust the Maximum number of child objects in the Nexus diagram

The Nexus diagram that shows the lineage and relationships of assets can be really greedy for machine resources, so there is a limit of 50 objects. You can now change this limit if you want to, and show more objects in the Nexus. Please handle this setting with care. You can modify this value in Administration > Connect Configuration > Instance Settings.


Schedule an Automatic Purge of Inactive Entries

As of version 2018.2, removed assets are not deleted from the system and are instead inactivated. Inactive assets can be purged from your system using the Inactive entries option in the Administration menu. If you don't want to purge them manually, you can specify the period (e.g. 30 days) after which the inactive assets are purged automatically. You can change this value in Administration > Connect Configuration > Instance Settings.


Configure Search Boosting Weights

This one is probably one of the best enhancements in this release. When there are multiple results for your search query (which is almost always), Connect has to determine an order to present the results to the user. For this purpose, there is a boosting mechanism in place which adds scores to each result based on several conditions. The most important one is the type of asset. This mechanism allows you to specify simple rules like "Terms are always higher than Reports". But what if you want it another way? With 2019.1, you can now specify exact results weights in Administration > Connect Configuration > Search Boosting.

The weights are part of the search index, so in order to have the changed weights applied, you have to perform the full re-index of the system, which can take a long time if you already have a lot of content in Connect.

In this release, the mechanism was also modified to boost results which have a full or partial match of the search query with the asset name.


Configure SSL using the User Interface

The Connect installer has a new option to configure SSL and make Connect run using the secured https protocol. Say "Hello!" to convenient, user-friendly SSL configuration, and "Goodbye" to importing certificates using the command line and modifying configuration files manually.


You can set up SSL as either a part of the standard install/upgrade procedure or independently. You can upload your standard CA-issued certificate, or let the installer generate a self-signed certificate by itself (Note: a self-signed certificate will not be trusted by end machines by default).


Metadata Loaders

All of the database metadata loaders have been modified to use a new version of Connect tools, which come with Alteryx Designer and Alteryx Server 2019.1. It is necessary to upgrade your Designer and Server instances if you want to use the database metadata loaders included with the 2019.1 Connect release.


Microsoft Azure SQL DWH Metadata Loader

The current MS SQL metadata loader has been modified to support the load of metadata from SQL server in Azure.


Workbook Descriptions are Now Pulled from Tableau


Previously, you could find only the description of a Tableau report in Connect. With 2019.1, you can find also the description of a Workbook.


Macro Files are now Included in the Lineage of a Workflow


The macro files on the shared file system are now visible as a separate object in the lineage of an Alteryx workflow.


Fixed issues


In addition to all of these new features, some of the known issues have been resolved!


Resolved: Windows Authentication Disabled Unexpectedly


If you are using the Windows Authentication method to authenticate users, you may have encountered a situation when this option would become disabled unexpectedly. This was caused by an improper saving of another configurations, which lead to overwriting the Windows Authentication setup. This issue has now been resolved. If you are using Windows Authentication, we recommend upgrading to 2019.1 to avoid this issue.


Resolved: New Assets Saved as Version 2 from the Beginning


If you perform any audit reporting of your content in Connect, you have probably noticed that some of the assets are saved as "Version 2" immediately after the first time they are loaded. This is caused by the attachment, which is uploaded separately and triggers an update event right after the create event. This behavior has been changed in 2019.1. Now your assets should be labeled as "Version 1" until there is an actual change made to the asset.


Resolved: Value too long

Another issue solved in 2019.1 is the too long strings that cause an error during the load of the metadata. To avoid this situation, we have increased the size of the CATALOG_ENVIRONMENT, the Table Attribute STRING_VALUE, and the Tableau Relations EXPRESSION fields.