Why Azure data factory does not show any system variables & functions for trigger parameters as it shows in case of pipeline parameters such as date formatting functions and system output variables etc ?

Muhammad Umer 20 Reputation points
2023-09-08T10:03:55.5533333+00:00

It becomes difficult to find the system variables and functions and this also increases the chance of errors.
For example, @{formatDateTime(trigger().scheduledTime, 'yyyy-MM-dd HH:mm:ss')}

In my case, it was not easy to know how I can get the start time of trigger by ADF itself.

Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
11,624 questions
{count} votes

Accepted answer
  1. Subashri Vasudevan 11,226 Reputation points
    2023-09-10T03:29:29.3233333+00:00


    Muhammad Umer

    Thanks for your confirmation about my understanding.

    Right now, we dont have the flexibility to use dynamic expressions on pipeline parameters and its hard to understand which properties we can use in the parameters field.

    In order to know about the properties of triggers, we can use the properties icon in the monitor tab and trigger runs. Below is a sample for a scheduled trigger execution.

    Screenshot 2023-09-10 at 8.35.30 AM

    If you click on Properties, we will get to see all the properties like below.

    Screenshot 2023-09-10 at 8.36.07 AM

    From the above screenshot, we can infer that, below properties can be used with the @trigger() method, like, @trigger().<property_name> where property_name could be name, startTime, endTime, scheduledTIme, trackingId, clientTrackingId, code and status.

    {
      "name": "Trigger_12348CAF-BE66-42CF-83DA-E3028693F304",
      "startTime": "2023-09-05T18:00:22.4180978Z",
      "endTime": "2023-09-05T18:00:22.4180978Z",
      "scheduledTime": "2023-09-05T18:00:22.507Z",
      "trackingId": "1234a112-7bb9-4ba6-b032-6189d6dd8b73",
      "clientTrackingId": "12346637084630521889360938860CU33",
      "code": "OK",
      "status": "Succeeded"
    }
    
    

    For an storage event trigger it will be like below where we can see\use folderpath, filename properties as well.

    {
      "name": "Trigger_12348CAF-BE66-42CF-83DA-E3028693F304",
      "outputs": {
        "headers": {
          "Host": "prod-1234.westeurope.logic.azure.com",
          "x-ms-client-tracking-id": "1234c153-fc96-4b8e-9002-0f5096bcd744",
          "Content-Length": "52",
          "Content-Type": "application/json; charset=utf-8"
        },
        "body": {
          "folderPath": "data",
          "fileName": "myFile.csv"
        }
      },
      "startTime": "2018-09-25T18:22:54.8383112Z",
      "endTime": "2018-09-25T18:22:54.8383112Z",
      "trackingId": "07b3d1a1-8735-4ff0-9cc6-c83d95046101",
      "clientTrackingId": "56dcc153-fc96-4b8e-9002-0f5096bcd744",
      "status": "Succeeded"
    }
    

    Coming to your question, I recommend you to please submit your detailed feedback in IDEAS forum here :

    All the feedback shared in this forum are actively monitored and reviewed by respective product owners.

    Hope this helps. Feel free to let us know for any further question on this,

    Appreciate your feedback.

    Thanks.

    1 person found this answer helpful.
    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.