Bizzare Data source credentials issue

[Anonymous]

Hi,

I have attempted to connect to an Excel file on Onedrive using the recommended "Web" option. As usually, it failed on the first time as I wasn't sure which one to choose. Since then, I have lost the privilige to change the credential. I have tried to clear or edit permission in the data source. But sarcastically, it doesn't even appear in the data source list, not in the local and not in the global. So I am really stuck - need to clear permission but no item to clear however the credential does get stored but just hidden. Please make Power BI a more sensible product to use.

[v-eachen-msft]

Hi @Anonymous ,

You can click "Edit Query" option in the home navigation bar to open the data source settings.

Then you could edit/remove your permissions in current file or global desktop.

If you think this option is too hidden, you could post an idea here to improve Power BI.

[Anonymous]

No, it's not the option is hidden. I have no difficulty finding it. It's the file not shown in the data source list but the credential has already been cached. So you see the dilemma. You can't clear permission because it's not recognised as a "data source" but it does get cached. I have even tried "clear all permission" but it simple removed existing one not the hidden one. What can I do? 

[v-eachen-msft]

Hi @Anonymous ,

Do you mean that you could't find the data source you have configured in these two lists?

You could try to re-install Power BI and check if this problem will happen.

[ToddChitt]

Any solution to this? I too am facing the same issue. I tried to hit a web data source, and failed after entering my credentials. If you click EDIT, you can edit ONLY the web URL, and NOT the credentials. 

There are no entries in Data Source Settings, either Global or Current File. 

I have tried signing out of Power BI Desktop, re-launching the tool. Nothing.

This is a BUG, pure and simple.

[Anonymous]

Unfortunately, no solution and yes, it's a bug, 100%.

[Anonymous]

Yes, the first attempt failed due to some wrong selection and that's probably why it didn't make the list. But it didn't stop the credentials being cached. Never mind, I have reverted to SQL server to store the tiny dataset.