Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started

Reply
rjb2232
Frequent Visitor

Fabric workspace item events - alert creation failed

Hello, 

 

First, a little background on what I am trying to accomplish. We created a Workspace to land all of our SAP data (tables, CDS views, extractors) and it is organized in the bronze/silver/gold medallion archatecture. The SAP data is being extracted using a 3rd party software and is landing in the Files section of the bronze lakehouse under the subfolder "in", with each SAP table getting its own folder ex. Files/in/LFA1. 

 

I have a pipeline that finds all child folders of "in", and passes the folder names as a parameter to a notebook which handles the merge into our silver lakehouse as delta tables. 

 

I would like to have this process triggered by an event as opposed to scheduling the pipeline. I created a Fabric Workspace Item Event as shown below, but when I click create I get the error message "Request failed with status code 500."

 

Did I setup the alert incorrectly, or is there an issue with Data Activator? Any suggestions on the configuration of the alert or our design in general would be greatly appreciated. 

 

rjb2232_1-1717528949940.png

rjb2232_2-1717529021241.png

rjb2232_3-1717529127485.png

 

 

1 ACCEPTED SOLUTION

Hi @rjb2232 ,

If you can get the total number of folders in your specified lakehouse via a method such as measure (e.g. if you have a datasheet dedicated to dynamically logging all the folders), you can create a Reflex for this measure, which will be triggered when this measure changes. If you can't implement this method, I found the following link It may help you to know that this method requires 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.

View solution in original post

6 REPLIES 6
v-junyant-msft
Community Support
Community Support

Hi @rjb2232 ,

Error code 500 generally refers to an internal error, not an error in your operation.
I noticed that someone else has already reported the ICM and our engineers have noticed the issue and confirmed that it is a known issue, they are doing their best to resolve the issue, please be patient and I will let you know as soon as there is any progress.

Best Regards,
Dino Tao

Thanks @v-junyant-msft glad to hear that its a known issue and is being worked on. 

 

Once this is resolved do you think my setup will accomplish what I am trying to do? Will event type Microsoft.Fabric.ItemCreateSucceeded with filter data.itemKind StringContains Folder trigger the alert when a new folder is added to Files/in in my lakehouse? Also, is there a way to set this alert for only a specified lakehouse, or will it trigger whenever a folder is created anywhere in the workspace?

 

Thanks

Hi @rjb2232 ,

The “Item” in “Microsoft.Fabric.ItemCreateSucceeded” does not refer to a physical item such as a folder, but rather to the item that you created in the Fabric Event The “Item” in “Fabric.ItemCreateSucceeded” does not refer to an entity item such as a folder, but rather to an action you perform on a resource in a Fabric Event, such as creating a new artifact, which is not triggered by adding a new folder to the data source (i.e. lakehouse).

Best Regards,
Dino Tao

Thanks for the clarification. Any recommendation on how I could trigger a pipeline based on a new folder being added to the files section of a lakehouse? 

Hi @rjb2232 ,

If you can get the total number of folders in your specified lakehouse via a method such as measure (e.g. if you have a datasheet dedicated to dynamically logging all the folders), you can create a Reflex for this measure, which will be triggered when this measure changes. If you can't implement this method, I found the following link It may help you to know that this method requires 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.

I'm having the same issue with Azure Blob Storage events. Also tried the Fabric workspace item and got the 500 error there too. Is this an issue affecting creation of all event triggers/alerts?

av_fm_0-1717577433514.png

 

Helpful resources

Announcements
FabricCarousel_June2024

Fabric Monthly Update - June 2024

Check out the June 2024 Fabric update to learn about new features.

July Newsletter

Fabric Community Update - July 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors