Where is it used?
Identifies the recipe step or Split Flow branch, such as 3. filter.
MorphoGrid VBA · editable inputs
Generated VBA creates a MorphoGrid Parameters sheet so filters, row counts, replacement values, output names and other inputs can change without generating and importing a new BAS file.
The simple rule
The other columns explain where each value is used and preserve the generated default. The internal key column is hidden because it belongs to the macro.
Identifies the recipe step or Split Flow branch, such as 3. filter.
Column, Operator, Value, Row count, Output filename, Format, or Enabled.
Change this yellow cell. The macro reads it when processing begins.
The original exported value. Restore defaults copies it back when requested.
Worked example
The saved recipe keeps open claims. This month you need identical cleanup and output logic, but only for closed claims.
The generated default stays visible.
The next run keeps closed records. No new BAS is required.
Safe update sequence
Filter
Change Condition · value. Keep operator names such as equals, contains, between, or greaterOrEqual.
Remove rows
Change Row count from 3 to 5 when the actual header moves from row 4 to row 6.
Replace or fill
Update Find, Replacement, or Value without rebuilding the surrounding cleanup.
Split Flow
Change a branch value or filename. Unique splits also expose column and format.
What the table is not
Tune existing inputs and turn generated steps on or off. To add, delete, reorder, or restructure steps and nested groups, update the workflow in MorphoGrid and export a fresh BAS.
Troubleshooting
The Column value must match a header available at that point in the recipe. Check spelling and earlier rename steps.
Enter digits rather than words: use 5, not “five rows.”
That is expected. Set Enabled to No to skip it; the row remains so it can be enabled later.
Click Restore defaults and confirm. Editable values return to their generated defaults.
No. MorphoGrid preserves the Parameters sheet during normal reset-and-rerun operations.
No. Add the condition in MorphoGrid and export again so the matching procedure is compiled.
One module. Many routine variations.
Use MorphoGrid again when the workflow structure itself needs to evolve.