Forum Discussion

majort's avatar
majort
New Member
11 years ago
Solved

Remove existing DataSource

Hi,   if i change a data source for example from one database to another database by editing the M Script, the previous used database connection still exists because when i publish the pbix to powe...
  • jeremyfirth's avatar
    jeremyfirth
    11 years ago

    had this same issue when I created a link to a file on a mapped network drive initially, then later changed it to the full network path to the file.

     

    Both data connections were showing up when I either published it to PowerBI.com or when I went to PowerBI.com and tried to pull the file instead. 

     

    I ended up deleting it from PowerBI.com, re-downloading and installing Personal Gateway, then pulling the file into PowerBI.com using Get Data.

     

    Kind of a pain, but it worked. It was a solution offered by a Microsoft employee in another thread.

andylitics's avatar
andylitics
Regular Visitor
8 years ago

We recently moved a SQL server, and I updated the location in Data Source Settings screen succesfully in the query.  Everything works fine when i refresh locally from PBI Desktop.

 

After publishing to Powerbi.com though, similar to the OP, the old data source still shows up in the Data Source Credentials screen, even though i've confirmed my data model doesn't reference it at all.

 

Tried everything outlinded here, I've deleted the data model, uninstalled and reinstalled the personal gateway, and uploaded the data model via both "get data" as well as "publish" and nothing seems to work.

 

Now my refreshes can't be scheduled since it thinks there is still some kind of reference to it, but if there was, how could the file refresh locally with no issue?

 

Any input/suggestions would be appreciated.

  • Anonymous's avatar
    Anonymous
    Not applicable
    8 years ago

    Facing the same issue but it only affects some reports.

     

    Looks like this happens when you have a query that references another query (that was originally using the old data source).   The referencing query appears to maintain some link to the old source.

     

    Workaround:

    1. open report in Power BI
    2. SAVE AS to new report (this step is critical – wont work from the original report)
    3. In Advanced Editor, make some minor change to the query string(s) (I generally use custom SQL in my queries). 
    4. SAVE and SAVE AS to original report name
    5. Publish original report.   Should be ok now.
    6. Edit report to undo minor change and republish.
    • Anonymous's avatar
      Anonymous
      Not applicable
      8 years ago

      True Solution Found!!

      1. Got to Query Editor
      2. Open Data Source Settings
      3. Select the source to be removed
      4. Select "Change Source"
      5. change the source to be the same location as one of your other sources. 
        My situation was one source was a local copy of a Sharepoint file, the other was the sharepoint URL.
      6. Click OK to accept the change. 
      7. Power BI recognised the duplication and removed the duplicate entry. 

      I hope this works for you. 

    • Anonymous's avatar
      Anonymous
      Not applicable
      8 years ago

      True Solution Found!!

      1. Got to Query Editor
      2. Open Data Source Settings
      3. Select the source to be removed
      4. Select "Change Source"
      5. change the source to be the same location as one of your other sources. 
        My situation was one source was a local copy of a Sharepoint file, the other was the sharepoint URL.
      6. Click OK to accept the change. 
      7. Power BI recognised the duplication and removed the duplicate entry. 

      I hope this works for you. 

      • gilderoylockhar's avatar
        gilderoylockhar
        Regular Visitor
        4 years ago

        This has done it!

    • Anonymous's avatar
      Anonymous
      Not applicable
      7 years ago

      I have been trying for 1 week to get a previous link removed from the datasource.  This workaround works - Yippe

      Anonymous wrote:

      Facing the same issue but it only affects some reports.

       

      Looks like this happens when you have a query that references another query (that was originally using the old data source).   The referencing query appears to maintain some link to the old source.

       

      Workaround:

      1. open report in Power BI
      2. SAVE AS to new report (this step is critical – wont work from the original report)
      3. In Advanced Editor, make some minor change to the query string(s) (I generally use custom SQL in my queries). 
      4. SAVE and SAVE AS to original report name
      5. Publish original report.   Should be ok now.
      6. Edit report to undo minor change and republish.

       

      • sfmike99's avatar
        sfmike99
        Icon for Advocate II rankAdvocate II
        7 years ago

         

        Well I didn't do the "save as" trick but I did delete the old report and dataset from Power BI Service, then re-uploaded it again. New version works fine, however I had to recreate permissions (a pain) and I still have the old data sources listed. Even if "save as" works, it still seems like a bad solution because it is effectively a new report. All this to change a file pointer?

         

        Please add 'delete' options for data sources to Power BI Service!