Forum Discussion
Help Understanding "Direct Query to AS" Datasets
I successfully created a pbix file connecting two previously created datasets using Direct Query to AS. I then created a report using the data from them. However, when I went to publish and test my new report in My Workspace, it said I created a new dataset, not just a report and that I needed to set up a refresh schedule.
This has left me a little confused as to what I just created. It appears I created a new dataset and not just a report. I didn't realize a separate refresh schedule needed to be set up. I assumed that pointing to multiple existing datasets is all I had to do since all the refreshing is done there already.
If that is the case, then what I should have done is published this new dataset and then started another report pointing to it like I would with other "regular" datasets.
Is this logic correct or am I missing something?
Hi arock-well
The reason this happens is because it needs a new dataset to create a way for the different underlying datasets to work together.
In terms of the refresh schedule that is if you got any dashboards linked to this composite dataset(your DirectQuery). When you interact with the report it will always get the latest data from each of the underlying datasets automatically.
2 Replies
Thanks GilbertQ . The scheduled refresh part was the one that confused me the most. But I repointed my report to this new dataset and all seems to be working so far.
Hi arock-well
The reason this happens is because it needs a new dataset to create a way for the different underlying datasets to work together.
In terms of the refresh schedule that is if you got any dashboards linked to this composite dataset(your DirectQuery). When you interact with the report it will always get the latest data from each of the underlying datasets automatically.
