Forum Discussion

danielpaduck's avatar
danielpaduck
Helper III
2 years ago
Solved

A DirectQuery Connection Is Required - Taking Data Ownership For A Developer Who Left Company

Hi All,    Just wondering what the best approach to handle taking ownship for a Tenant from a developer who left before I started. So essentially, I was brought on about a month ago to help 'enhanc...
  • Anonymous's avatar
    Anonymous
    2 years ago

    Hi danielpaduck ,

    Thank you for question. Based on the two options you presented, I will analyze the pros and cons of both for you:

     

    1. Add the Excel File to the Existing Dataset

        You need to be CAUTIOUS. Please note that adding data to a DirectQuery dataset can be complex and may require changes to the underlying data source or the creation of a composite model.

    Here are the steps:

    1. Connect to the existing dataset using DirectQuery in the Power BI Desktop.
    2. Use the "Import" connectivity mode for the Excel file.
    3. Combine the data as needed using Power Query Editor.
    4. Publish the changes to the service and ensure that the dataset refreshes successfully.

       

      For more information on this you can check out the following links:

      https://docs.microsoft.com/en-us/power-bi/connect-data/desktop-directquery-about

     

    1. Create a Second Workspace

       If you want to avoid any risk to the production environment, creating a second workspace is a SAFER option.

       Here's how to do it:

         1.Create a new workspace in Power BI Service and copy the Semantic model and the report to the new workspace.

    1. Add the Excel file to the dataset in the new workspace.
    2. Make the necessary changes and test thoroughly.
    3. Once tested, you can consider replacing the production dataset with the updated one from the new workspace.

     

    Best Regards,

    Yifan Wang

    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.