New way to schedule refreshes
The current method of setting up scheduled refresh in the Power BI service is clunky and nearly unusable--not to mention an RSI nightmare.
Some better solutions:
--Option for "Refresh every X minutes/hours/days"
--Ability to schedule more frequently
--Powershell to create/update Scheduled Refreshes for Datasets
Todd Chittenden commented
The entire Scheduled Refresh page needs to be re-designed. From a user interface aspect, it has serious flaws.
1) I have an Enterprise gateway installed on my machine. Yet I see this yellow exclamation every time I log in saying, "You have no personal gateway installed". like I'm doing something wrong. The service needs to detect if there is ANY type of gateway installed on the machine, and only if NOTHING is, display the message. AND, give the user the option to dismiss it forever, for the current machine.
2) Why must I specify a Gateway BEFORE I tell it to keep my data up to date or not. I had a case where the Gateway was deleted on purpose. Now I'm going to get failure emails every day until MS decides to stop (takes about a week, I think). I should be able to shut that off at the top, BEFORE I specify a gateway.
I'm actually with Microsoft on the functionality of the 8 refreshes per day, every half hour. In the early days around the time of GA, it was ONCE per day, with no ability to specify the time. Then it was 3 times per day, then 6. Premium will get you 48. I'm thankful for how far it has come.
And have you ever looked at the ACTUAL refresh time compared to the SCHEDULED time? I have seen it vary by as much as 20 minutes. If MS gives you the ability to schedule to the MINUTE, you're going to expect it to be just so, and it won't happen, and you'll be disappointed. Remember, this is NOT SQL Server Agent, a tool many Power BI developers are intimately familiar with.
If you need it more than every half hour, look into streaming datasets, PUSHING data into Power BI via a stored procedure, or connect it to Azure Stream Analytics.
i do not understand why reports, like from exchange online mailbox, which is refreshed in about a minute can only be scheduled 8 times per day. We are checking payments and it does not cover our opening ours.
Greg Guidarelli commented
Agree with all comments. We need more granularity to schedule refreshes for a growing list of customers - so that they're not running at the same time when their data sets are living in the same Capacity. Ideal is 1-minute increment. Anything more frequent than 30 minutes would help.
Nathan Schwinnen commented
This is extremely important. I have several reports to refresh and it is becoming impossible to stagger the schedule for all of them. I would prefer to just choose exact times for refreshes, but even 10 or 15 minute increments instead of 30 would make things much better.
Jon Fortner commented
At least give us 10 minute increments. You are cause issues on the node trying to run too many refreshes at once because you only give us 30 minute increments to choose from. We need to spread the schedules out.
Right now for a 30 hourly refresh I had to add 48 Slots. That is a Lot of wasted efforts
Jeremy Herbert commented
Eight refresh events per day is too restrictive for many reporting requirements and doesn't allow reports to be updated hourly during the business day (which seems a reasonable schedule). Sure we have the push API which is great, but that requires development effort and limits reporting agility.
I understand there are processing overheads so maybe we could have more frequent refresh options restricted to smaller datasets?
Need this option
I agree... 00 & 30 options are very limited in a busy environment!