topic Re: Parameters in Schedule Triggers of Fabric Data Pipeline in Pipelines

Parameters in Schedule Triggers of Fabric Data Pipeline

DarshanBabar — Tue, 08 Oct 2024 15:14:07 GMT

Hi,

Currently, we don't see any option to use Scheduled Triggers in Fabric Data Pipeline where we get an oprion of passing parameters.

Any update on this please.

Thanks,

Darshan

Re: Parameters in Schedule Triggers of Fabric Data Pipeline

Anonymous — Wed, 09 Oct 2024 01:11:49 GMT

Hi DarshanBabar ,

As of now, Microsoft Fabric Data Pipeline does not support passing parameters directly when using scheduled triggers. This feature is currently on the roadmap for future updates.

I think you can vote for this Idea under this link: Microsoft Idea

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.

Re: Parameters in Schedule Triggers of Fabric Data Pipeline

jwinchell40 — Fri, 11 Oct 2024 01:47:40 GMT

DarshanBabar - Why would you need to pass parameters to the pipeline as part of a schedule trigger? I'm not saying it wouldn't be useful, just curious as to the use case.

In Fabric/Data Factory if we had a scheduled pipeline that required parameters we would read those values using a Lookup Step and drop them in variables. For example, if we wanted to run the same pipeline for multiple customers the first step in our pipeline was getting our customer list + parameters for that customer. Then we would use those values downstream.

The other option that worked really well for us with one of our Contact Center Dashboard products was using a "Trigger File" which is available in Fabric Pipelines and Data Factory. The pipelines monitor a ADLS Gen2 folder and when a file is created it kicks off the pipeline. You also are then able to read the contents of the file, pull out parameters or config settings and run the pipeline.

Re: Parameters in Schedule Triggers of Fabric Data Pipeline

SivaReddy24680 — Mon, 04 Aug 2025 08:44:23 GMT

Hi,

We have a scenario:

We have a config table in which we store the tables metadata of tables to extract from the source. We pass a parameter called BatchName on which we pull those batch tables especially.

Lets say if we have 10 tables, i need to run the 5 tables(BatchName=DailyBatch) in daily basis and 5 tables for every 2 hours(BatchName=HourlyBatch).

If I can have an option to pass parameters while scheduling the pipeline, It will be easy for me to schedule multiple schedules within the single pipeline. Else I may need to create separate pipeline for each batch

Re: Parameters in Schedule Triggers of Fabric Data Pipeline

GertjanIdema — Thu, 26 Feb 2026 10:01:55 GMT

We have a usecase for passing parameters with the schedule. We use a deployment pipepline to deploy our data pipeline from development to acceptance and poduction. If we want to schedule our production datapipeline, it needs to know that is should run on the production workspace, so we have to be able to set the workspaceId parameter. I know this can be done with a variable library, but out F4 capacity doesn't support that.