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
AlexWuhoo
Frequent Visitor

Data Activator Power BI Report Alert Refresh Rate

Hello,

 

I have a Power BI Report setup with a table that reads from an Azure SQL table which gets refreshed in real time from a Synapse pipeline run with logging data. I have an alert set to listen when New Data Arrives, which should be only a handle of rows at a time. But currently there are two issues or limitations which I wanted to clarify.

1. The Reflex is triggering for every row of data in the table within the report every single hour, instead of it triggering for only the new rows. How can I set up the data to only trigger for the new data, or is there an issue here being that we're in preview?

AlexWuhoo_0-1718326480950.png

AlexWuhoo_1-1718326630683.png

2. The refresh rate for Data Activator reading data from Power BI Reports is defaulted to 1hour? Is there anywhere I can get this closer to real time or making any changes. I know that when this was first introduced last year the option to select refresh rate was there however it isn't anymore? Ideally I want a way for the Data Activator reflex to trigger in real time as soon as the Power BI report gets refreshed and there's new data there.

AlexWuhoo_0-1718327018690.png

 

2 ACCEPTED SOLUTIONS
jameshutton
Community Admin
Community Admin

Hello @AlexWuhoo 

I'll answer your 2nd question first: yes, Data Activator checks Power BI data hourly at present; we are looking to allow more frequent updates in a future release.

Regarding your 1st question: If your table has a timestamp column, then Data Activator will use the timestamp as the event time for each event. It will use that timestamp to remember which rows it has already seen, and then it will only look at new rows each time it polls the table. I can see from your screenshot that your table does indeed have a timestamp column, called "SubmissionDateTime", but it appears that Data Activator hasn't recognized it as a datetime column. Are you by any chance doing some string conversion on the column that is precluding Data Activator from recognising it as a datetime? If so, try removing the conversion and see if that fixes it.

View solution in original post

3 REPLIES 3
AlexWuhoo
Frequent Visitor
jameshutton
Community Admin
Community Admin

Hello @AlexWuhoo 

I'll answer your 2nd question first: yes, Data Activator checks Power BI data hourly at present; we are looking to allow more frequent updates in a future release.

Regarding your 1st question: If your table has a timestamp column, then Data Activator will use the timestamp as the event time for each event. It will use that timestamp to remember which rows it has already seen, and then it will only look at new rows each time it polls the table. I can see from your screenshot that your table does indeed have a timestamp column, called "SubmissionDateTime", but it appears that Data Activator hasn't recognized it as a datetime column. Are you by any chance doing some string conversion on the column that is precluding Data Activator from recognising it as a datetime? If so, try removing the conversion and see if that fixes it.

Hi James,

 

I have fixed the issue with the datetime not being recognised properly but now when it is recognised, data activator interprets it as UTC time when the time is actually in AEST. Is it a bug that its not recognising it properly?

AlexWuhoo_0-1719382641129.png

Because this is being recognised incorrectly if something had a time stamp  at 12pm AEST(2amUTC) , it will think its 12pm UTC and then you basically have to wait till the actual 12pmUTC time which is a 10hour delay AEST before it triggers.

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