The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hi to the community !
I have a very interesting opportunity to use the alert functions for a business case.
Scenario of the business case :
I have a data set with around 15k shop in diferent regions when I see have individually how many products has been sold (Consumption of the product) comparing to the average quantity that has been negociated at the beginning of the year.
This idea is having a "Ratio" for each Shop (Ratio = Consumption / Quantity) which helps me to understand if one my shop is selling less than the quantity which has been negociated. In the case my Ratio is <0.33 the Ratio value is red and the situation is critical.
Alert Business Case :
I want to use alert (associated with Power Automate) to send a mail each time one shop has a ratio <0.33 while refreshed
The message that will be received will look like :
"The consumption of the product is very low (ratio) in Shop 1 (Region A). Please see the details on the Dashboard"
Questions around this Business Case :
1) Can we develop an alert at such a detail level (it´s a value from a table) even if it´s not a measure?
2) I saw that Alert could be done only with Measures. So in this case it means that I should create 15k measure for each Shop to have an alert for each case? (obviously it would be crazy)
3) I saw also that we can only create 250 alerts per Dashboard
I don´t know if someone has experience with creating alerts and if I can reach such a level of precision (alert on the 15k shops) or if the best solution would be create 250 measures on an other page and track the "250 most importants shop" which will be valuable.
Thank you for your help ! It will be very appreciated
Christophe from France
Since you are already planning to use Power Automate you can consider running a flow on a schedule (every five minutes, for example), run your DAX queries as needed to see if any thresholds are breached, send the emails accordingly, and add the debounce logic (so as to avoid sending too many messages about the same alert).