Forum Discussion

zenisekd's avatar
zenisekd
Super User
4 years ago

Enable load/Include in report refresh - Bug or Feature?

Our customer migrated to SAP, but couldn't load all historical data, so we kept it in the data wareshouse. Therefore for BI reports I did some merging and appending (of SAP and DWH) and I was hoping, that if I disable "Enable load" and "include in report refresh", I will be able to load some tables from the DWH, merge or append it, and then disable load and refresh. This way I would get all data (historical and current). 

I was wrong.


To simulate what I found out, I have created two excel tables - List A and List B each in a separate document. 

 

 

 

Imagine, that list B isold data from DWH. I don't need them to be refreshed (in reality it is about 120k rows). So to demonstrate what will be happening, aside from loading List B, I have created copies, where I disabled Load and disabled load and refresh (you may notice it in the table names. 

I have also appended and merged List A with List B that was disabled for load and refresh. 

 

 

 

Next I created a report. So far, so good. 

 

 

 

But look, what happens, when I have the data in the excel sheet List B:

 

 

For some reason, if the query with disabled refresh is included in some other query then it refreshes anyway...?!!

Does anyone know some workaround? Thanks. I dont need 120k rows to refresh every day without any reason.





7 Replies

  • zenisekd , Once one disable - Enable load, I doubt the table will be even loading and available. Are still able to use that?

  • As presented, if you disable "Enable load", it won't load, but if it is included in some merged or appended query, the data are there and what is very wrong, is that it also refreshes. Test if yourself. 

    Now I am looking at ways how to get the data there so they would not refresh, even if used in append or merge. 

  • Anonymous's avatar
    Anonymous
    Not applicable

    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