Forum Discussion
No data in report when using direct query
Hi all,
Having a rather strange problem. Normally I use import query option for data but this time I'm going in direct as I need to display information on TVs so need is as close to real time as possible. It's a simple query of projects with key dates. I can see my data well when in Query Editor but once I put it on my report canvas all is blank. I published into my testing workspace...also blank there. Waited for refresh and also blank. Am I being really silly and forgetting something? Not enableing a setting?
In Power Query Editor my table is set to 'Include in report refresh'
Has this happened to anyone else before?
Thanks,
Kasia
There are advantages and disavantadges in both scenarios, depend what what you need to do, when the dataset is huge for sure best option is the directquery because of refresh times, but you then have performance issues on the refresh of the vizualizations.
It may seem a strange advice but in some cases is a trial and error approach of checking logs and verify what are the best results.
3 Replies
Hi kasiaw29 ,
When using the Direct Query you do nont have access to the change the data settings, that is why the data is not present altough you can see it in the query editor if you try to make some change adding an additional step immeditaly the model asks you to change to import mode.
Basically you can only change the information by adding measure.
Altough I don't understand why there is no data presented in the model view, I believe it's because of size limitations because if you connect to a database is terabite of rows presenting the full information would freeze, in the query editor it's only a part of the model 1000 rows or similar so it presents the data.
Check the post below about advantages and disavantages
https://docs.microsoft.com/en-us/power-bi/connect-data/desktop-use-directquery
Thank for reply, it looks like for what I need it I'm probably best switching to import mode.
Thanks again!
There are advantages and disavantadges in both scenarios, depend what what you need to do, when the dataset is huge for sure best option is the directquery because of refresh times, but you then have performance issues on the refresh of the vizualizations.
It may seem a strange advice but in some cases is a trial and error approach of checking logs and verify what are the best results.
