Skip to content
PlaidCloud

Package Alteryx Dependencies

PlaidCloud imports Alteryx workflow files from Document and uses Document paths for dependencies and artifacts. You can upload files into Document, ask an MCP-connected agent to organize files for you, or connect Document directly to shared storage such as OneDrive, Google Drive, SharePoint, S3, Azure Blob, or SFTP.

Upload Or Connect Shared Storage

Section titled “Upload Or Connect Shared Storage”

Choose the source location that best fits your migration:

  • Upload the package to a Document account.
  • Connect an existing shared storage location as a Document account.
  • Ask an MCP-connected agent to copy, move, rename, and organize files already available in Document.

Shared storage connections can reduce migration prep because the team can keep files where they already collaborate:

Section titled “Recommended Folder Shape”

For each migration batch, use a folder shape like this before importing:

workflow-package/
  workflows/
  macros/
  inputs/
  expected-outputs/
  reports/
  spatial/

This structure is optional, but it makes review and validation easier.

Workflows And Macros

Section titled “Workflows And Macros”

Place workflow files and macros in predictable folders:

  • Put .yxmd and .yxwz files in workflows/.
  • Put .yxmc files in macros/.
  • Keep nested macros with the rest of the macro library.
  • Keep duplicate macro names out of the same package unless they are intentionally versioned.

PlaidCloud uses macro source files to create PlaidCloud macro workflows and connect macro calls from converted workflows.

Input Files

Section titled “Input Files”

Put input data under inputs/:

  • CSV, TSV, fixed-width, JSON, XML, Excel, Access, YXDB, SAS, SPSS, Stata, Avro, Parquet, and HDF files.
  • Lookup files used by formulas, dynamic replace, fuzzy matching, or joins.
  • Folders referenced by Directory and Dynamic Input tools.

When PlaidCloud imports the package, converted steps point to the selected Document locations.

Spatial Files

Section titled “Spatial Files”

Put spatial files under spatial/ and keep sidecars together:

  • Shapefiles: include .shp, .shx, .dbf, and .prj.
  • MapInfo files: include .tab, .map, .id, and .dat.
  • Include projection files and lookup layers when present.
  • Keep KML, GeoJSON, and other spatial inputs in the same dependency package.

Do not split spatial sidecars across folders. PlaidCloud needs the full group to materialize geometry correctly.

Report And Artifact Assets

Section titled “Report And Artifact Assets”

Put report assets under reports/:

  • Images used by report composer tools.
  • PDF inputs.
  • HTML fragments or templates.
  • Map layers used by report maps.
  • Example generated reports when artifact validation is required.

Converted report steps create PlaidCloud artifacts that can be reviewed from Document and workflow run history.

Expected Outputs

Section titled “Expected Outputs”

Put validation fixtures under expected-outputs/:

  • Trusted Alteryx output tables.
  • Expected reports, PDFs, maps, images, or charts.
  • Notes about accepted row ordering, numeric precision, and date handling.

Expected outputs are optional for structural validation and are the best evidence for output parity validation.

External Connections

Section titled “External Connections”

For database, API, and cloud-source workflows, capture:

  1. Source system name.
  2. Connection type.
  3. Database, schema, table, endpoint, or bucket names.
  4. Credential owner or secret name.
  5. Snapshot date when output parity depends on a point-in-time source.

Use PlaidCloud connections or credentials for repeatable production runs.

Section titled “Related Guides”