It would be great to be able to set Refresh scheduling for Dataflows and Data Models at minimum to be on the 00, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55 minute increments instead of just 00 and 30.
Currently when we do a dataflow and data model refresh, data can be delayed by 1 hour to display in PBI reports which is impactful to our business for critical processes that communicate information to our PBI Users. If the dataflow has already started and changes are made in SharePoint, the user will not be able to display those changes until the next 30 minute refresh for the dataflow and the next 30 minute refresh for the data model which is at minimum a 1 hour delay and not ideal.
Even if we are not using SharePoint as our source, there is a 30 minute delay and would be much more beneficial if that could be limited to more like 10 minutes, understanding that the refresh needs to be able to complete before it displayed.
1 Comment
GianfAdvocate I
Yes!! My customers also feel very much the need of scheduling at least with 15 minutes granularity. This does not mean to increase the 48 refreshes per day limit: we just need the ability to schedule refreshes at least at 15 minutes apart (better yet, give us the capability to freely choose refresh times) - always with the 48 refreshes/day limit, of course.
Recent ideas
Support Automatic Connection Variable Mapping for Lakehouse Shortcuts Across Deployment Pipelines
When using Deployment Pipelines to promote Lakehouses containing shortcuts that use Delegated Identity, the connection variables defined through a Variable Library are not consistently retained or au...
