Forum Discussion
Question about DirectQuery behavior when publishing a report
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.
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?
- AmiraBedh1 year agoSuper User
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_og1 year agoSuper User
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 .- Zhinee1 year agoHelper III
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.
- sergej_og1 year agoSuper User
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.