Skip to content

Commit e93ff33

Browse files
authored
Merge pull request #113758 from djpmsft/docUpdates
timestamp parameters
2 parents 5fc677f + 84d5d7e commit e93ff33

File tree

2 files changed

+8
-0
lines changed

2 files changed

+8
-0
lines changed
68.3 KB
Loading

articles/data-factory/parameters-data-flow.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -64,6 +64,14 @@ If data flow parameter `stringParam` references a pipeline parameter with value
6464
- If expression is checked, `$stringParam` evaluates to the value of column1 all uppercase.
6565
- If expression is not checked (default behavior), `$stringParam` evaluates to `'upper(column1)'`
6666

67+
#### Passing in timestamps
68+
69+
In the pipeline expression language, System variables such as `pipeline().TriggerTime` and functions like `utcNow()` return timestamps as strings in format 'yyyy-MM-dd\'T\'HH:mm:ss.SSSSSSZ'. To convert these into data flow parameters of type timestamp, use string interpolation to include the desired timestamp in a `toTimestamp()` function. For example, to convert the pipeline trigger time into a data flow parameter, you can use `toTimestamp(left('@{pipeline().TriggerTime}', 23), 'yyyy-MM-dd\'T\'HH:mm:ss.SSS')`.
70+
71+
![Setting a Data Flow parameter](media/data-flow/parameter-timestamp.png "Setting a Data Flow parameter")
72+
73+
> [!NOTE]
74+
> Data Flows can only support up to 3 millisecond digits. The `left()` function is used trim off additional digits.
6775
6876
#### Pipeline parameter example
6977

0 commit comments

Comments
 (0)