Azure Synapse: 'triggerBody' is not a recognized function

Question

We have a pipeline in Synapse which is triggered by a Storage Event Trigger whenever a new file is created in a specific directory.

We recently get errors when using the function '@triggerBody().fileName' to pass the file name to a pipeline component. The official guides still have references to this function call, can anyone tell me what the problem might be? I am at a loss..

Answer 1

I got it working thanks to a support ticket with Microsoft. The issue is that we cannot access the trigger-output from inside the pipeline but need to pass it ahead of time to a parameter.

Solution: create a parameter in your trigger, e.g. called "file_name" and set it to "triggerBody().fileName" and then reference the parameter in your pipeline (e.g. inside a look-up activity).

My StorageEventTrigger:

My look-up activity:

Answer 2

Hi Victor Seifert ,

Thankyou for sharing the resolution with the community. I understand that the workaround for using 'triggerBody' function is to parameter in the trigger named as "file_name" ,reference the same in the lookup activity and provide "triggerBody().fileName" expression in the trigger for the parameter.

Requesting you to kindly accept this answer since your issue has been resolved. Accepting answer helps the community to get visibility on the resolution. Thankyou.

Answer 3

Duplicated.

Answer 4

Any update on this issue, this is preventing us from implementing critical functionality.

Answer 5

Hi Victor Seifert , Thankyou for using Microsoft Q&A platform and thanks for posting your question here. I understand from the query that the pipeline is failing when you use @triggerBody().fileName in Azure Synapse. Kindly let me know if that is not the correct understanding. According to the official documentation: System variables supported by Azure Data Factory and Azure Synapse Analytics @triggerBody().fileName has been deprecated in Synapse. Refer the note section.

Kindly replace the expression with @trigger().outputs.body.fileName instead of @triggerBody().fileName .

Hope it helps. Kindly accept the answer and mark it as helpful if the above information helps. Thankyou