Execution properties - Data360_Analyze - 3 - 3.12

Data360 Analyze Server Help

Product type
Software
Portfolio
Verify
Product family
Data360
Product
Data360 Analyze
Version
3.12
Language
English
Product name
Data360 Analyze
Title
Data360 Analyze Server Help
Copyright
2023
First publish date
2016
Tip: If you are not yet familiar with how you can use derived property values across your data flows, see Using derived property values.

The "Execution" prefixed property values are derived from the start time of an execution of a data flow, or part of a data flow.

When running a data flow from a scheduled task, the execute time will be the time when the data flow actually begins executing. Therefore, if multiple data flows are being run by a single scheduled task, the execution time may be different for each data flow. To get a consistent value across all data flows run by a scheduled task, use the "Run" prefixed properties.

When a data flow, or part of a data flow, is run outside of a scheduled run, for example from the data flow Designer, the property values will be based on the time that you clicked the run button.

The "Execute" prefixed properties are not visible on all data flows. You can use the values in expressions, but in general you should not explicitly set values for these properties, as the values will be automatically generated by the system.

The values of the following properties are in the local time of the Analyze server, unless otherwise specified.

The Date, Time, and TimeZoneOffset suffixed properties are the ISO 8601 Extended formats of date, time, and time zone offset. The DateTime suffixed properties are NOT ISO 8601 compliant for backward compatibiilty reasons. An ISO 8601 compliant datetime can be created by using substitution expression with the data and time values, for example {{^RunDate^}}T{{^RunTime^}}.

The _PathSafe variants of the properties are all in the ISO 8601 Basic formats. These formats are generally safe for substituting into file paths.

Execution property

Format Example Description
ExecutionDate YYYY-MM-DD 2019-05-04 The date (year, month, day) that the execution of the data flow started.
ExecutionTime HH:mm:ss 14:34:56 The time (hours, minutes, seconds) that the execution of the data flow started.
ExecutionDateTime YYYY-MM-DD HH:mm:ss 2019-05-04 14:34:56 The date and time that the execution of the data flow started.
ExecutionTimeZoneOffset [+/-]HH:mm +05:00 The offset of the local time zone in hours and minutes from UTC.
ExecutionDate_PathSafe YYYYMMDD 20190504 The date (year, month, day) that the execution of the data flow started.
ExecutionTime_PathSafe HHmmss 143456 The time (hours, minutes, seconds) that execution run of the data flow started.
ExecutionDateTime_PathSafe YYYYMMDDTHHmmss 20190504T143456 The date and time that the execution of the data flow started.
ExecutionTimeZoneOffset_PathSafe [+/-]HHmm +0500 The offset of the local time zone in hours and minutes from UTC.
ExecutionDateTime_UTC_MS nnnnnn 12345562242 The milliseconds since the UTC epoch (1970-01-01 00:00:00 UTC).

Deprecated properties

The following "Current" prefixed properties have been deprecated:

  • CurrentTime
  • CurrentDateTime
  • CurrentDate

Please use the corresponding "Execution" or "Run" prefixed properties. For example, "CurrentDate" is equivalent to "ExecutionDate".

Note: It is recommended that you use the "Run" prefixed properties where possible to ensure that when data flows are run in a scheduled sequence, the value will be consistent across data flows.