We are able to pass parameters in the Pipeline Trigger in Synapse and ADF.
We really need this feature in Microsoft Fabric.
18 Comments
We need the schedule times and frequency to be dynamic so we can easly change them accross enviroments wiht value sets. I a deployment pipeline the schedules are typically different for different workspaces, without being able to parametrize schedules you have to implement all sort of work arounds to enab/disable schedule after deploying, and even so the deployment pipeline will still show that as a change, without clearly highlighting that is schedule change (you have to open each object and compare manually), please help!
mrbartussAdvocate II
Wait... did this literally just drop silently? I was checking my pipeline schedules today and the "Parameters" section is finally available in the trigger UI! Looks like it might be rolling out now- Where is the priority to get these quality-of-life simple features out. This has been planned and I see other comments about being worked on and year go by and nothing.
- Any update on this? Or are there alternatives?
- Any update on this? Or are there alternatives?
- Just went to Fabcon a couple of weeks ago and was excited to get back to working in fabric, then I find out this is thing. Come guys, fabric has so much potential. Let's at least get basic functionality going!
- We really need this feature in so many cases. I feel there should be at least the possibility to get the schedule ID in the pipeline as for triggers. But even this is not possible at the moment. We may get the type but the ID does not match the schedule.
- We need an update. Such a flaw is unacceptable in a product like Fabric.
- Can we get an update on this?
- Any update on this?
