Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredJoin us at FabCon Vienna from September 15-18, 2025, for the ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM. Get registered
I've created event-streams, objects, and reflex triggers (NOT using the 'Add Trigger' button from the Pipeline) to fire a Fabric object. There's currently no ability to define parameters in the Action itself, and I can't believe no data is passed to the Fabric object via this flow.
Does any reflex data get sent as part of the resulting call and how should it be referenced in the pipeline since TriggerEvent is not present in this flow?
Hi - at the moment there's no way to pass parameters to the pipeline/notebook you invoke. For Azure storage events -> pipelines we pass the file path and type as hard-coded parameters but you can't yet customize them. We've got it on our plan though, aiming to complete it in Q1 CY2025. Thanks!
Hello WillT
It is now 31 of Marts 2025 and I still see no way to do this.
Can you please make an update on this situation? I don't see how we can utilize events in any meaningful way until there is a way to pass parameters properly to a pipeline from a stream.
@gpalsson thanks for your patience on this. Totally understand the importance of this functionality. As you note it has taken longer than expected but please be assured we still intend to do this and it is still one of the top items on our backlog. We currently aim for this to be available within the next 3-4 months.
Thanks for the update. The current workaround we use is to have an azure function ingest event and start a pipeline via the API using the service principal and pass the payload to the pipeline that way but it's quite clunky.
Hi @PhilBrown ,
(1)In the Eventstream, select reflex and click “open item”.
(2) Click "new property".
(3) Create a rule. On the rule page in Design view, scroll down to the Act section.
In the Act card for the trigger that's monitoring your chosen condition, select Fabric item.
In Additional information, select up to five fields to monitor. When Data Activator starts a job, parameters are passed to the pipeline.
For more details, please refer: Trigger Fabric items - Microsoft Fabric | Microsoft Learn
Assign data to objects in Data Activator - Microsoft Fabric | Microsoft Learn
Best Regards,
Neeko Tang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thanks for the detail @Anonymous part of my problem may be the difference in cards. This seems to differ from your screen shots and MS documentation. Instead of 'New Property', I see 'New Object'.
On the theory that this was just labeled. I've done the same by creating an Object, but the Action card doesn't show Additional Properties.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.