Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
The system variables of the pipelines called by an "Invoke Pipeline (Preview)" action are not populated correctly or at least they are not as populated as those called by "Invoke Pipeline (Legacy)".
In particular the following variables are not populated:
Hi @pellitteris ,
I made a similar maneuver to the query you raised.
I think you need to write @pipeline. firstly. After this, it will give you what you want.
Best Regards
Yilong Zhou
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
sorry @Anonymous, the problem is not that I don't know or can't find the variable, the problem is that the runtime value of the system variables @pipeline()?.TriggeredByPipeline* is null using the new "Invoke Pipeline" activity.
Hi @Expiscornovus,
I created two pipelines, a caller and a worker. The caller pipeline calls the worker pipeline using the "Invoke Pipeline (Preview)" activity. Inside the worker pipeline I read the values of the system variables by setting some variables. In this case the variables are always null. If instead I use the "Invoke Pipeline (Legacy)" activity the variables are always populated.
Hi @pellitteris,
Just to double check, can you share how you tested this?
I tried to reproduce this with a set variable activity and I was also getting a null value back in the outputs of that variable activity.
I used the below expression in a Pipeline return value variable type.
@pipeline()?.TriggeredByPipelineRunId
The set variable activity output
The invoke pipeline (preview) activity output