This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
If you see this warning when attempting to collect metadata from your Alteryx Private Gallery, verify that the version of Alteryx Server and the version of Alteryx Connect match. That is a requirement for proper function.
In this article you'll find detailed information about the loader categories and which exact information is extracted by each of the loaders we support. Each type differs in the object hierarchy, structure of the objects, and detail of the objects.
Have you ever wondered what are the limits of Connect? How many entries can you store in Connect? Great questions! In fact, no hard limit on the number of entries is set. The number around 2M entries is the number on which the performance tuning in the 2019.1 release was done.
This article is intended to assist with inserting a certificate to be used to validate a SAML signature from a SAML Identity Provider (IDP) when used with Alteryx Connect. This article will only be needed if your IDP is signing assertions or other traffic with a specific cert that may be self-signed or not trusted by a widely trusted Certificate Authority (CA).
Alteryx Connect is great at finding data assets that exists within enterprises which helps data workers to shorten their journey to data-driven insight. One of the steps to refresh the metadata is to schedule the Metadata loaders. In this process, the data assets can be created, changed or removed. To take a look at this change log, we can take a look the backend of Connect - the H2 database.
We're constantly working to improve your Connect experience. Find out what new features, improvements, and bug fixes we released with this version of Connect! Here is a summary of what has changed in 2019.4.