Forum Discussion
Pipeline Trigger Type
Hi Anonymous ,
Thanks for reaching out to the Microsoft fabric community forum.It appears that Fabric pipelines may not support PipelineTriggerType in the same way Azure Data Factory does, as there is no mention of it in the official documentation. This suggests that the functionality might not be currently available in Fabric.
These are the system variables that are supported in Fabric pipeline
Reference article: Expressions and functions - Microsoft Fabric | Microsoft Learn
As a workaround, to reliably capture the trigger type in a Microsoft Fabric pipeline, it's recommended to pass it explicitly as a parameter from the trigger to the pipeline. To do this, start by defining a pipeline parameter named TriggerType. When setting up your trigger—such as a scheduled trigger—assign a value to this parameter, for example "ScheduleTrigger". Inside your pipeline, you can then access this value using @pipeline().parameters.TriggerType. Finally, use this value in your SCRIPT activity to log the trigger type into your PipelineOrchestrator_Bronz_Execution_Logs table. This method ensures consistent and accurate tracking of how your pipeline was initiated, whether manually or by schedule.
If you find this post helpful, please mark it as an "Accept as Solution" and consider giving a KUDOS. Feel free to reach out if you need further assistance.
Thanks and Regards
Hi Anonymous ,
Thanks for reaching out to the Microsoft fabric community forum.
It appears that Fabric pipelines may not support PipelineTriggerType in the same way Azure Data Factory does, as there is no mention of it in the official documentation. This suggests that the functionality might not be currently available in Fabric.
These are the system variables that are supported in Fabric pipeline
Reference article: Expressions and functions - Microsoft Fabric | Microsoft Learn
As a workaround, to reliably capture the trigger type in a Microsoft Fabric pipeline, it's recommended to pass it explicitly as a parameter from the trigger to the pipeline. To do this, start by defining a pipeline parameter named TriggerType. When setting up your trigger—such as a scheduled trigger—assign a value to this parameter, for example "ScheduleTrigger". Inside your pipeline, you can then access this value using @pipeline().parameters.TriggerType. Finally, use this value in your SCRIPT activity to log the trigger type into your PipelineOrchestrator_Bronz_Execution_Logs table. This method ensures consistent and accurate tracking of how your pipeline was initiated, whether manually or by schedule.
If you find this post helpful, please mark it as an "Accept as Solution" and consider giving a KUDOS. Feel free to reach out if you need further assistance.
Thanks and Regards