Different parameter for Pipeline Validation vs Execute Pipeline

Is there a way to define default values (parameters, mapper, elsewhere) based on the run mode of the pipeline? During pipeline development I wish for some parameter to default to X during validation runs, but have it default to Y during Execution runs?

In my particular case I resort having to test an incoming parameter for null to avoid trying to parse a value not provided during validation, but I don’t want to actually deploy that code.


Parameters cannot take different values based on the type of run. You can use the expression property pipe.flags.is_suggest to check whether it is a validation run and use different defaults within the pipeline.

1 Like