Item has already been added. Key in dictionary: 'NavigatorBase_3803694d-dbc2-442b-aff5-fb75dfd09447'

[friely47]

Have 5 stored tables in SQL. I am trying to connect to a new table in the same area and it keeps throwing up the below error message. I am really struggling to understand why it won't let me connect. 

Item has already been added. Key in dictionary: 'NavigatorBase_3803694d-dbc2-442b-aff5-fb75dfd09447'  Key being added: 'NavigatorBase_3803694d-dbc2-442b-aff5-fb75dfd09447'

[friely47]

Thank you, it works fine if I connect to it in a new and fresh report, but unfortunatly I need to connect to it in this current report as several other datasets and measures feed into it already. 

[Alex87 · Accepted solution]

Try removing the problematic data source from Power Query. The problem is identified. You need to remove and recreate the connexion to the datasource. If it is not working, you can start from a fresh Power Bi and add all the other queries and measures.

If my answer helped, please mark it as the solution . Thanks.

[juleshorton]

How is this a solution? Why is this error occurring?

We can't disconnect & reconnect everything that this dataset feeds.

[Alex87]

Hello,

Ensure that there are no duplicate connections or tables with the same name or identifier in your Power BI model. Sometimes, a previously created connection might not have been deleted properly.

Try removing the problematic data source and then re-adding it

[juleshorton]

This error appears as soon as I select "Enter Data" to add an excel sheet as a static table. There is no duplicate data source because I don't get that far. I can't use the "Enter Data" option at all.

[friely47]

thank you, unfortunatly the option to delete it is not avaliable (greyed out when I right-click on it in Data Source Settings). The only options avaliable are 'Change Source... Edit Permissions... Clear Permissions... Copy Path to Clipboard...' 

I have tried clearing permissions multiple times and re-entering credentials but to no luck 😞

[Alex87]

maybe you can start fresh with a new PBI and see if you still have the same problem?