Automated migration results
When Import detects an Alteryx Multi-Field Formula tool:- It generates a MultiColumnEdit gem.
- The Alteryx expression is converted into a an expression template that uses Prophecy’s placeholder variable (
column_nameorcolumn_value). - The import process applies this template to each selected column, matching Alteryx’s behavior.
- Field overwrite or “create new field” options are preserved when possible.
Manually replicate in Prophecy
To manually recreate Multi-Field Formula behavior in Prophecy:- Add a Multi-Column Edit gem.
- Select the columns you want to transform.
- Enter an expression that refererences the placeholder
column_nameorcolumn_value. (Prophecy automatically substitutes each selected column at runtime.) - Choose whether to overwrite existing fields or create new fields with a naming pattern.
- Validate output in the Data Explorer.
Configuration options
In Alteryx:- Select multiple fields using the UI.
- Define one formula referencing
_CurrentField_. - Choose overwrite vs new-field creation.
- Optional renaming rules for new fields.
- Select multiple fields inside the Multi-Column Edit gem.
- Write a single SQL expression using
column_nameorcolumn_valueas placeholders. - Choose whether to 1) apply to original columns or 2) maintain original columns and add prefix or suffix to new columns.
Output behavior
- Alteryx evaluates the formula in the Designer engine.
- Prophecy evaluates the SQL expression inside the Databricks SQL Warehouse, generating one derived expression per selected field.
Known caveats
- Some Alteryx functions do not map directly to SQL and may require adjustments.
- Expressions that don’t generalize across fields may not convert cleanly.
- Type behavior may differ when applying one expression across multiple columns.
Example
Alteryx Multi-Field Formula example
Goal: Trim whitespace from[Name], [City], and [State].
Alteryx expression: Trim([_CurrentField_])

