- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
System Variable Pipeline triggered by pipeline ID is not resulting in a ID but in a Name
When building logging information we need to have the GUID from the Parent Pipeline. We're using the System Variables as input for a Stored Proc.
The name of the variable is called Pipeline triggered by pipeline ID
If you hoover of the System Variable you will see that the defenition is:
ID of the pipeline that triggered this pipeline. Applicable when a pipeline run is triggered by an Execute Pipeline activity; Evaluates to Null when used in other circumstances.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It sounds like you need "pipeline().TriggeredByPipeline".
The UX and the backend are temporarily "out of sync" here, just because of deployment sequencing.
The expression "pipeline().TriggeredByPipeline" will work now, but the ExpressionBuilder might not yet recognize it.
The system variable "pipeline().TriggeredByPipeline" will resolve to the GUID of the triggering pipeline.
The system variable "pipeline().TriggeredByPipelineName" will resolve to the name of the triggering pipeline.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please let me know when rhe UX and the backend are back in sync.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @edkreuk,
You are right, this seems to be a bug in Data Pipeline. I have just tried to reproduce the same error as you. When selecting the 'Pipeline triggered by pipeline ID' system variable, it returns this expression: @pipeline()?.TriggeredByPipelineName, which is wrong. The problem here is the incorrect labeling of this variable. It should be labelled as 'Pipeline triggered by pipeline Name'.
The other similar variable 'Pipeline triggered by pipeline run ID' is returing the correct expression, i.e.,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Pipeline name should be unique. Do not think there is a "GUID" of a pipeline. @Ajay to comment.

Helpful resources
Join our Fabric User Panel
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Fabric Monthly Update - June 2025
Check out the June 2025 Fabric update to learn about new features.

Subject | Author | Posted | |
---|---|---|---|
04-09-2025 02:45 AM | |||
06-04-2023 03:27 AM | |||
11-15-2024 02:35 AM | |||
03-21-2025 02:29 AM | |||
06-13-2024 10:42 AM |
User | Count |
---|---|
2 | |
2 | |
1 | |
1 |
User | Count |
---|---|
2 | |
2 | |
2 | |
2 | |
2 |