Forum Discussion
Disabling "Include in report refresh" not working
Anonymous,
" These PBIX are published in the Cloud and are scheduled to refresh themselves overnight as well as during the day."
"Include in report refresh" option only works for Power BI Desktop, it doesn't impact the refresh process in Power BI Service.
In Power BI Desktop, when you disable "Include in report refresh" option, data will not update in report view of Power BI Desktop after you click "Refresh" button in Desktop.
Regards,
Lydia
Not a very smart solution, I agree. But the most likely solution would be to provide a never changing datasource like an Excel and always load static data from there. You'd have to create an additional gateway data source though and might have a lot of unnessesary network traffic...
SokonSorry, but that's known as 'defect support system'
What happens if the location of that static data moves? You don't NEED to refresh it, but Power BI Service FORCES you to, and then FAILS because it's not there.
<rant>
This is a horrible design spec, where the desktop tool does something different than the service.
<\rant>
Sorry, but it's just my opinion.
Actually, there is a better work-around now that DataFlows are up in GA:
Configure each Source in a DataFlow, and each DataFlow can have its own refresh schedule. So DataFlow1 can be static data. Refresh it once and never again. DataFlow can be the transactional data that gets refreshed regularly.
Then create a Power BI model that uses BOTH DataFlows.
ToddChitt: When the data really IS static, I don't care if the source moves, do I?
However, you are absolutely right with dataflows: I can put my data there once an load it in all my datasets without the need to setup and maintain an extra gateway data source for it. That makes things a lot easier!
I'd say it solves the problem, even when it hurts me to think about that data nevertheless being loaded into the datasets without need during every refresh...
SokonYes, I think you DO care as Power BI Service WILL try to refresh that data even if you don't need it to. So it always needs to be where the service can find it.
That's the beauty of Data Flows. You can refresh them once, and NEVER set up a Refresh Schedule, yet you can still reference them (and the cached data) in Power BI Desktop designer.
- Great idea. But many will overlook this possibility.
All:
Apparently, the July '20 Desktop update should fix this, but I think you need to open the model in that version (or later), save, then re-publish. FYI the July update is 'V3' and included the "enhanced metadata format" that is needed for this setting to be visible and usable by the service.