A Microsoft Fabric pipeline runs on a daily recurrence schedule and reads a configuration file whose path varies by run date. The author wants each scheduled run to receive the scheduled run's start time so the pipeline can build the correct dated path automatically, without an operator typing a date each day. How should the schedule pass the run time into the pipeline?
- AHard-code today's date into a pipeline parameter and update that parameter value manually before each daily scheduled run so the path always points at the current file.
- BReference the trigger's scheduled start-time system value in an expression that builds the dated path, so each run derives its own date directly from the schedule. Correct
- CSwitch to a storage event trigger so the arriving file's name supplies the date, then parse the date out of the event's file path inside the pipeline on each run.
- DRead the current system clock with a lookup activity at the start of the run and use that returned value to construct the dated configuration path for the load.
Why A is wrong: Editing a parameter by hand every day is exactly the manual step the requirement removes, and it breaks on any missed or back-filled run, so it does not deliver an automatic dated path.
Why B is correct: The trigger exposes its scheduled start time as a system value that an expression can read at run time, so the pipeline builds the correct dated path automatically for every run without operator input.
Why C is wrong: A storage event trigger changes the firing model from a daily clock to file arrival, which the scenario does not want, and the requirement is a scheduled run deriving its own date rather than reacting to a file.
Why D is wrong: Reading the wall clock works on a normal run but returns the execution moment, so a delayed or re-run pipeline builds the wrong dated path, unlike the scheduled start time the trigger supplies.