Alteryx One Dataset FAQs

The archive formats supported by Alteryx One (GZIP and BZIP2) allow a ~3-4GB CSV file to be compressed and uploaded within the 1GB Alteryx One File Upload limit. Larger datasets will need to be configured through an Alteryx One connection.

Auto Insights currently supports datasets up to 17GB for ingestion from Alteryx One. Supporting datasets larger than 17GB is being evaluated.

No, only datasets that are created from Alteryx One datasets (or those that are subsequently connected to an Alteryx One dataset) will be available throughout Alteryx One Library, Scheduling, and Plans, and shared via Alteryx One sharing experience.

Existing Auto Insights datasets imported via Admin Portal are still edited, shared, and scheduled within the Admin Portal, until they are connected to an Alteryx One dataset. For more information on connecting to an Alteryx One dataset, go to Replace Dataset.

Yes, existing Auto Insights datasets imported via Designer Desktop or via Admin Portal can be connected to an Alteryx One dataset. For more information, go to Replace Dataset.

Once a "legacy" dataset is connected to an Alteryx One dataset, it becomes managed by Alteryx One and is thereafter available throughout Alteryx One Library, Scheduling, and Plans, shared via the Alteryx One sharing experience. At this point, it also ceases to be administered in the Auto Insights Admin Portal. Users with explicit access to an Auto Insights dataset via Groups in the Admin Portal will retain their access—sharing can then be administered via the Alteryx One sharing experience.

No. While there is a dependent relationship between the Alteryx One dataset and the Auto Insights dataset, they are shared independently. Sharing an Alteryx One dataset will not automatically share the Auto Insights dataset(s) based on it. Similarly, sharing an Auto Insights dataset will not automatically share access to the associated Alteryx One dataset from which it is sourced. This can be managed within the dependencies section of the sharing modal.

You do not need to share the Alteryx One dataset when sharing the Auto Insights dataset for users to be able to use it throughout Auto Insights.

Yes, this will create 2 separate Auto Insights datasets from the same Alteryx One dataset, each of which will not be automatically shared with the other user(s) with access to the source Alteryx One dataset. Each user would have to share their Auto Insights dataset for others to use. The sharing of an Alteryx One dataset and an Auto Insights dataset is handled separately.

In this case, these Auto Insights datasets remain discrete and independent entities within Auto Insights and Alteryx One, even though they are connected to the same source Alteryx One dataset. A single Alteryx One dataset can be the source for multiple Auto Insights datasets.

No, Auto Insights datasets imported via Alteryx One can only have a single owner. However, other users can be granted “Editor” access to edit dataset settings, schedule, orchestrate, and share this dataset just like the owner.

Users can also be granted “Viewer” access, allowing them to use the Auto Insights dataset in Auto Insights Search, Missions, and Playbooks (if enabled).

Datasets in Alteryx One are essentially pointers to where data lives—either a file uploaded to Alteryx One Base Storage or data stored within an external database/storage. An Alteryx One dataset does not contain the data itself. Therefore, when an Auto Insights dataset refresh is triggered, either manually or scheduled, it will take the latest data from the underlying data source and import it into Auto Insights.

No, there can be multiple refresh schedules for an Auto Insights dataset. Each of them, whether they directly trigger an Auto Insights dataset refresh or run a Plan that triggers an Auto Insights dataset refresh, will be triggered at the appropriate time. Protections are in place such that each Auto Insights dataset can only perform one concurrent ingestion at a time (a new ingestion won't start if one is already in progress).