Forum Discussion

JMACND's avatar
JMACND
Regular Visitor
5 years ago
Solved

Pointing data to SharePoint folder instead of a local data source (OneDrive)

We have a user who created a whole PowerBI flow via a connection to data located within their OneDrive for Business folder on their C:\ instead of pointing the data to a Teams SharePoint source where the data actually exists. In PowerBI Desktop, I can rework the queries, but as many of you can imagine, this comes with some headache in terms of making existing parts of the query work with the new data source location. Does anyone have a cleaner way or a recommendation on how to cleanly repoint the PowerBI report to the new data source location? Thank you in advance. 

  • You will have to swap out the first 1-3 lines of each query. You cannot change it using the datasource button. That only changes locations with the existing connector, not changing connectors.

     

    I've done this before, and it is tedious, but doable.

  • Hi JMACND 

    As edhans says you have to change the first few lines of each query to point to the new source location, but once you've done that, and perhaps one or two other lines to make sure you end up with the same table that is then used for the transformations in the query.  None of the transform steps should need adjusting.

    Regards

    Phil

4 Replies

  • edhans's avatar
    edhans
    Community Champion

    You will have to swap out the first 1-3 lines of each query. You cannot change it using the datasource button. That only changes locations with the existing connector, not changing connectors.

     

    I've done this before, and it is tedious, but doable.

    • JMACND's avatar
      JMACND
      Regular Visitor

      This did work. I did have to change the line of code just below the inserted three lines to reflect the new naming convention of the injected source query lines.

  • Hi JMACND 

    As edhans says you have to change the first few lines of each query to point to the new source location, but once you've done that, and perhaps one or two other lines to make sure you end up with the same table that is then used for the transformations in the query.  None of the transform steps should need adjusting.

    Regards

    Phil