'pipeline().TriggerName' is not a supported system variable ?

[amthog]

Hi,
When using pipeline scope variables I get an error for pipeline.TriggerName as not supported:

This is despite it being documented here:
https://learn.microsoft.com/en-us/fabric/data-factory/expression-language#pipeline-scope-variables

All other variables in the documentation work as expected.
I can see posts circa 2023 discussing issues with various pipeline scope variables not being available, returning incorrect info etc. but would have thought this was behind us now.
Does anyone know if TriggerName is meant to be supported, if this is a bug etc ? 

cheers

[Asmita_27]

@pipeline().TriggerName isn’t supported in Microsoft Fabric yet.
It works in Azure Data Factory, but Fabric doesn’t expose this system variable today.
Workaround: Pass the trigger name into the pipeline as a parameter from the trigger.

[amthog]

Hi Asmita,

Thanks for your response. 
> @pipeline().TriggerName isn’t supported in Microsoft Fabric yet.
Seems odd given it is listed in the pipeline scope variable table the MS Fabric documentation. 
Also if I capture the whole pipeline() object then it is there as a member:

So are we sure this is not a bug in UI i.e. this member _is_ supported but  the UI validation is (incorrectly ?) blocking its use ?
BTW, there are other mismatches here.
For instance the documentation only lists two TriggeredBy members, with the triggered by pipeline ID oddly missing, but the intellisense and reference in the UI shows three TriggeredBy members as it does list the pipeline ID.  (??)

So if TriggerName really is not supported how do we tell that ?
Is that documented somewhere ?
And if it is not supported, how can we tell when or if it will be supported e.g. something in roadmap ?

cheers
If it really is not supported (yet ?) then MS should remove it from the documentation or 

[Asmita_27 · Accepted solution]

Hi @amthog ,
Thanks for the detailed explanation, makes sense.
Based on what you’re showing, it does look like the variable is present on the pipeline() object, so it could very well be a UI validation bug rather than the variable being unsupported.
Also agree on the inconsistencies, the docs list fewer TriggeredBy members than what the UI / intellisense shows, so something is definitely out of sync.

[v-menakakota]

Hi @amthog ,

Thanks for reaching out to the Microsoft fabric community forum. 

I would also take a moment to thank  @Asmita_27 , for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
For now, the reliable approach is to pass the trigger name into the pipeline as a parameter. Any future support will be reflected in release notes and updated documentation.

Best Regards, 
Community Support Team

[v-menakakota]

Hi @amthog ,

I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you

Best Regards, 
Community Support Team