Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Get certified as a Fabric Data Engineer: Check your eligibility for a 50% exam voucher offer and join us for free live learning sessions to get prepared for Exam DP-700. Get started

Reply
edkreuk
Regular Visitor

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.

The expression @pipeline()?.TriggeredByPipelineName
 
The result is not a Guid but a Name, what I've learned from Fabric implementation that you can never rely on names whiles these can be changed all the time and the Guid is Unique.
 
Anyone else have seen this before? Which variable can we use instead.
 
4 REPLIES 4
RDenkewalter
Microsoft Employee
Microsoft Employee

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.

 



Please let me know when rhe UX and the backend are back in sync. 

edkreuk_0-1694352148726.png

 

zeesoft
Microsoft Employee
Microsoft Employee

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., 

pipeline()?.TriggeredByPipelineRunId.
 
@DennesTorres - please comment.
 
Cheers.
 
GraceGu
Microsoft Employee
Microsoft Employee

Pipeline name should be unique. Do not think there is a "GUID" of a pipeline. @Ajay to comment. 

Helpful resources

Announcements
Feb2025 Sticker Challenge

Join our Community Sticker Challenge 2025

If you love stickers, then you will definitely want to check out our Community Sticker Challenge!

JanFabricDE_carousel

Fabric Monthly Update - January 2025

Explore the power of Python Notebooks in Fabric!

JanFabricDW_carousel

Fabric Monthly Update - January 2025

Unlock the latest Fabric Data Warehouse upgrades!