How to assign Variable Value to Parameter

Question

Hi, we need to create a "batch_no" in the format YYYYMMDDHHMMSS within our pipeline as a human-readable job identifier , since system variables like pipeline run ID or trigger ID aren’t easily readable.

The "batch_no" should remain consistent throughout the entire lifecycle of a single pipeline run.

We also plan to pass this batch number to child data flows and use it in other steps (e.g., copy data, etc.).

We tried initializing "batch_no" using a variable expression, but we're unsure how to assign this value to a parameter.

When we directly reference the variable(batch_no) in downstream steps, its value changes, so storing it in a parameter seems more stable.

We’re currently stuck on the setup—any expert advice on achieving this would be greatly appreciated!

@concat(formatDateTime(utcnow(),'yyyMMdd_HHmmss'))

Thank you!

Answer 1

To create a consistent "batch_no" value that can be reused throughout the pipeline run, you need to define a pipeline parameter called batch_no at the pipeline level.

Use a "Set Variable" activity or a "Set Parameter" activity at the beginning of the pipeline to generate the value for batch_no using an expression like:

@concat(formatDateTime(utcnow(), 'yyyyMMddHHmmss'))

When calling child pipelines or data flows, pass the batch_no parameter to them by mapping it in the "Execute Pipeline" activity or the parameters section of a data flow.

Reference the batch_no parameter in subsequent activities (like copy data, conditional checks) to verify that the same value is used throughout the pipeline.

Answer 2

To create a consistent "batch_no" value that can be reused throughout the pipeline run, you need to define a pipeline parameter called batch_no at the pipeline level.

Use a "Set Variable" activity or a "Set Parameter" activity at the beginning of the pipeline to generate the value for batch_no using an expression like:

@concat(formatDateTime(utcnow(), 'yyyyMMddHHmmss'))

When calling child pipelines or data flows, pass the batch_no parameter to them by mapping it in the "Execute Pipeline" activity or the parameters section of a data flow.

Reference the batch_no parameter in subsequent activities (like copy data, conditional checks) to verify that the same value is used throughout the pipeline.