Forum Discussion
Enable load/Include in report refresh - Bug or Feature?
HI zenisekd,
I don't think you can use these 'data load' options to achieve historical data effects.
AFAIK, M query tables have displayed the snapshots that preview of M query function processing result. They haven't really been stored in the data models. (normally this operation will proceed when you apply and submit these changes to save back to the data view)
So if you turn off the 'enable loading' option, these table records will not load/process to generate corresponding data tables into power bi data models.
So it means you can use this to store some cold data but it is trouble to achieve historical and current data effects. You need to manually refresh on the power query side and publish the report to replace old version data. (Also, the query tables refresh cannot be processed at the same time or the query table which is used to store history data will also get the latest data)
Managing query refresh - Power BI | Microsoft Docs
In my opinion, I'd like to suggest you create multiple tables with different DB 'queries' to limit the data loading ranges to achieve your requirement. (this should not suitable for the database which will replace the history records values)
Regards,
Xiaoxin Sheng
Anonymous I am not sure I follow, could you please try to explain on the example I have posted?
Based on Managing query refresh - Power BI | Microsoft Docs one would say, that if I Exclude the query from the refresh, it would mean that B will stay static even in the appended and merged queries, but it doesnt.
Does it mean, that there is no way to append two queries, where A query would use scheduled refresh and B would be without refresh, static? BTW, query A is from a different database then query B.
What about scheduled refresh, could I use scheduled refresh at the appended query (A+B) to refresh data only from A?
I am really confused here. I just want to connect (append) old database (with some transformations) to new database and reduce the traffic, disable refresh of old database.
Similar problem here: https://powerusers.microsoft.com/t5/Power-Query/Append-2-Queries-turn-off-refresh-on-only-1-of-the-queries/td-p/1265980https://www.reddit.com/r/PowerBI/comments/s97tc7/refresh_only_current_year_data_set_on_appended/
HI zenisekd,
'Include in report refresh' option will disable the refresh request so that the target data model table will keep current data without refresh.
'Enable load to report' option will affect the backend and front data model table transform. If you turn off it, this target query table will keep the preview snapshot of query table steps and its M query code did not process to generate the corresponding data mode tables.In addition, scheduler refresh also works on the dataset instead of detailed data tables. If you want to accurately control the refresh of each table, you can take a look at the following blog to use TMSL(Tabular Model Scripting Language) to config the refresh.
Trigger a single table to refresh in the Power BI Service – Data – Marc (data-marc.com)
Regards,
Xiaoxin Sheng
When I disable 'Include in report refresh' for a table from my DWH (with historical data) and then append it with my SAP database (current data table), and I use a refresh button, it refreshes both DWH and SAP data in the appended table. And it pulls data from my DWH. This makes no sence.
Since we are not using a premium account, the XMLA endpoint solution is not suitable for us plus I am really not sure if that would be working in case of an appended table again.
So far the only solution I found is to load both tables separately (DWH and SAP table) and then use UNION to create the appended table in DAX. This is however not the most effective solution...
