Question about DirectQuery behavior when publishing a report

[Zhinee]

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!

[AmiraBedh]

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.

[Zhinee]

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.

[sergej_og]

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.

[Zhinee]

But in the new report, I did connect to the existing semantic model (status_model_DQ)
Will the serviec create a new sematic model in this case?

[sergej_og]

Yes, because this connected (existing) DQ model is now your data source for your new report.
Similar thing will happen while using DF Gen 1 as a source. Just to give you a comparison.

[AmiraBedh]

Logically it won't create a new semantic model if the one you are connecting you is already existing even in a different workspace.

[sergej_og · Accepted solution]

Just tried to create a new report an publish it with existing DQ model as a source.
-> Only a new report appears in the WS.

Thx @AmiraBedh for the hint.

So you're doing something else with your approach @Zhinee .

[Zhinee]

I think I figured out why I am seeing this issue.

When I download the report, it was using a live connection. 
Then I change it to Direct Query connection( When I click on transform data, It asks me to add a local model and I choose the Direct Query)
Don't do this ^
just go to Option and Change Data Source
This will avoid creating a duplicate data model.

[AmiraBedh]

Glad to help ! 😄