Skip to main content
Alteryx .yxmd workflows describe a directed graph of tools. Planasonix maps each tool to a node or subgraph where semantics align; formula tools, joins, and unions translate more reliably than spatial, predictive, or macro-driven patterns.
Consult Import and convert for uploading batches of .yxmd files and interpreting conversion reports.

​
.yxmd file parsing

1

Collect workflows and dependencies

Gather .yxmd files plus any macro .yxmc dependencies and data connections exported according to your governance policy. Remove embedded credentials from files before upload; rebind secrets in Planasonix.
2

Upload and choose options

In the Alteryx import profile, select whether to inline macros on first pass or preserve macro boundaries as subgraphs when supported.
3

Review tool coverage summary

Open the coverage section of the conversion report to see counts of supported, approximated, and unsupported tools.

​
Tool to node mapping

Alteryx tool (examples)Planasonix direction
Input Data / Connect In-DBSource nodes with SQL or driver metadata
Formula, Filter, SelectColumn and row transforms
Join, UnionJoin and union nodes
SummarizeAggregation node
Output DataDestination node
Browse (developer)Ignored or converted to preview annotations
Rename ambiguous tool containers in Alteryx before export (Join Customers to Orders) so generated Planasonix nodes carry meaningful labels out of the box.

​
Formula and data types

Alteryx Formula expressions use Alteryx-specific functions and type coercion rules.
Functions like DateTimeParse, IFNULL, and string cleaners may translate to SQL or native expressions. When no direct mapping exists, the importer inserts a placeholder SQL block—replace it with tested logic.
Date, fixed decimal, and string width behavior can differ from your warehouse. Run preview steps on representative samples after conversion.

​
Macro handling

Standard macros encapsulate reusable tool chains.
Planasonix may expand macros into nested subgraphs or reusable pipeline components depending on product version. Keep macro inputs documented so you can map control parameters to variables.
Predictive, R, and Python tools are not guaranteed to convert. Treat them as explicit manual work: either embed Python nodes in Planasonix or push modeling to a dedicated ML platform and ingest results.

​
In-database vs standard workflows

In-DB streams should map closer to warehouse-native SQL. Standard workflows that mix local temp files and engine execution may need restructuring for cloud runtimes without local disk assumptions.
Dynamic inputs (wildcard paths, directory tools) should become parameterized sources or file triggers in orchestration rather than hard-coded samples.

Row transforms

Filters, sorts, and sampling after import.

Advanced nodes

Python and extension points for complex Alteryx logic.