Forum Discussion
Issue with CreateSucceeded Event Detection in Microsoft Fabric Event Stream
Hi Anonymous ,
What content creation do you need to monitor?
Please note that ItemCreateSucceeded in Fabric refers to an event produced when a new artifact is created successfully.
An artifact in this context refers to Fabric content such as Reflex or Eventstream, and not just the creation of a file.
All of the above you can find in this document:
Explore Fabric workspace item events in Fabric Real-Time hub - Microsoft Fabric | Microsoft Learn
Best Regards,
Dino Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
- Anonymous2 years agoNot applicable
Hi,
I would like to monitor the upload of a file to be exact, but I am testing by creating a notebook and dataflow. That event never gets generated for me. The events I can see are ItemUpdateSucceeded, ItemReadSucceeded, and also ItemDeleteSucceeded.
- Anonymous2 years agoNot applicable
Hi Anonymous ,
The Item monitored by Microsoft.Fabric.ItemCreateSucceeded refers to artefacts created in Fabric like Reflex or Eventstream, not to an entity object like a file.If it is possible to get the total number of folders in a given destination, e.g. through a measure (e.g. if there is a table dedicated to dynamically logging all the folders), then you can create a Reflex for that measurement, which will be triggered when that measurement is changed.
If you are unable to implement this approach, I found the following link which may be helpful requiring the use of a data factory:Azure Data Factory: Storage event trigger only on new files - Stack Overflow
Best Regards,
Dino Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.- Anonymous2 years agoNot applicable
Anonymous
Thank you for the information. However, I noticed that when I create an item such as a notebook or a data flow, the Microsoft.Fabric.ItemCreateSucceeded event is not triggered. Do you know if this is a known issue?