why is direct query using scheduled refresh and not scheduled cache refresh

[Anonymous]

Hello,

I'm testing direct query vs import, I have a separate .pbix file for each.

Last week, my direct query was doing a scheduled cache refresh every 15 min and my import was set up to import every couple hours, no issues.

Today I log in and now my direct query wants to do a scheduled refresh, not a scheduled cache refresh. I created a new file, configured it as direct query, saved it under a different name and published it, and it still wants to do a scheduled refresh, instead of cache.

The only thing i can think of, is that the native custom query i have added is flipping it to an import somehow, but it didn't do that last week.

Custom native query underneath Import vs. DirectQuery selection:

SELECT [timestamp]
,[newDATETIME]
,[tagname]
,CAST([value] as float) as [value]
FROM [TurbineValues]

[Anonymous · Accepted solution]

@Anonymous 

You should not see any data is the table view with DQ, if you add any additional datasource to the DQ pbix, it would be a mixed mode become import mode.

You can check the actual mode in Model view > Property > Advanced. 

Paul Zheng
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Anonymous]

That's it, thanks Paul.

The Model view tip is helpful.

I added a .xlsx as a data source in addition to the SQL table and that's what flipped the dataset it to import mode.

Should've noticed it, says in the documentation that Direct Query can only use 1 data source.

Thanks!

[GilbertQ]

Hi there

If you go into your PBIX and into the Table View, what is the properties set to on the table?

Is it set to DirectQuery or Import mode?

It would appear that it is on Import mode.