Forum Discussion
'pipeline().TriggerName' is not a supported system variable ?
- 6 months ago
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.
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
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