Microsoft Fabric Community Conference 2025, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount.
Register nowGet 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
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.
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.
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 name should be unique. Do not think there is a "GUID" of a pipeline. @Ajay to comment.