Forum Discussion

Zhinee's avatar
Zhinee
Helper III
1 year ago
Solved

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 data...
Need Help
  • sergej_og's avatar
    sergej_og
    1 year ago

    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 .

sergej_og's avatar
sergej_og
Super User
1 year ago

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's avatar
    Zhinee
    Helper III
    1 year ago

    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?

    • AmiraBedh's avatar
      AmiraBedh
      Super User
      1 year ago

      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's avatar
        sergej_og
        Super User
        1 year ago

        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 .

    • sergej_og's avatar
      sergej_og
      Super User
      1 year ago

      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.