Forum Discussion
Question about DirectQuery behavior when publishing a report
If I download a report and rename my report, and connect to DirectQuery dataset that already exists in Workspace A, and then I publish that report back to the same workspace, I notice that a new dataset gets created (with the same name as the report I renamed).
For example,
I renamed my report to Status_Monitor_Dev, and it somehow generated a Status_Monitor_Dev data set when I publish it
Is this expected behavior?
I was hoping the report would just connect to the existing dataset without creating a duplicate. ( Which should just use the status_model_DQ)
Thanks in advance!
9 Replies
Not sure I got you right...but if you create a new sematic model (report) with a not existing naming yet Service will create a new semantic model.
When you download a PBIX that is connected via DirectQuery to an existing dataset in a workspace, rename the report file and then Publish it back to the same workspace where the original dataset
Power BI assumes you're uploading a new report
You don't need to re-publish the PBIX file that contains a live DirectQuery connection unless it was originally created with "Connect to Power BI semantic model" from that workspace.
so when I first downloaded the a PBIX, it did not use a Direct Query ( It was using a live connection)
Then, I change the data source to a Direct Query that exists in the workspace.
Then, when I publish, I am seeing the new DirectQuery dataset.
