topic Re: When try to Refresh Fabric Warehouse get an error An item with the same key has already been added in Data Warehouse

When try to Refresh Fabric Warehouse get an error An item with the same key has already been added

valeria_dia — Wed, 18 Mar 2026 23:30:07 GMT

Hi,

We face an issue, where the Fabric Web UI would not refresh.

An changes to metadata are reflected in sys tables (and INFORMATION_SCHEMA), but not in Web UI or Semantic model.

Seems like metadata is frozen. I could not find it as a known issue, so posting here.

When I tried to refresh the Warehouse, I get this message:

Anybody had the same issue? Is Microsoft planning to resolve it?

Re: When try to Refresh Fabric Warehouse get an error An item with the same key has already been added

v-prasare — Thu, 19 Mar 2026 11:30:43 GMT

In this scenario i suggest you to raise a support ticket here. so, that they can assit you in addressing the issue you are facing. please follow below link on how to raise a support ticket:

How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

Re: When try to Refresh Fabric Warehouse get an error An item with the same key has already been added

valeria_dia — Thu, 19 Mar 2026 22:29:00 GMT

I did raise a support ticket before posting, Microsoft is investigating (I should mention it). But I don't know when are they going to fix it, so posting in the community in case someone has more information on this issue.

Re: When try to Refresh Fabric Warehouse get an error An item with the same key has already been added

Wikkleyn_81 — Fri, 20 Mar 2026 07:30:09 GMT

Hi valeria_dia I had tis previsouly. We would create a new schem/table and it wouldn't reflect in the web UI. The issue was a schema created with a name thats the same as a Fabric Reserved keywords. Deleted the schema and everyting was visible again.

Re: When try to Refresh Fabric Warehouse get an error An item with the same key has already been added

valeria_dia — Tue, 24 Mar 2026 20:21:25 GMT

Hi Wikkleyn_81 thank you for your suggestion. The name of the table, that I created is 100% not a reserved word.

Re: When try to Refresh Fabric Warehouse get an error An item with the same key has already been added

PierreL — Thu, 26 Mar 2026 00:40:04 GMT

I have been having 2 Warehouse Refresh issues in the last 3 days. The symptoms are the same as yours, changes to metadata are reflected in sys tables but not in the UI.

1. The below issue happened because we had a view in different schema with the same name. After renaming the view the refresh worked. This is weird because we had another 5 views with with a duplicate name in another schema which are not causing any issues.

2. The below error is currently under investigation after opening ticket.

I do hope this can be solved soon as this is completely blocking the deployment pipelines.

Re: When try to Refresh Fabric Warehouse get an error An item with the same key has already been added

valeria_dia — Thu, 26 Mar 2026 01:02:53 GMT

We have same named views and tables in different schemas too that are working.

And yes, Microsoft made a change so we can now see what table causing the issue at least and all working again after I rename\drop it.

Re: When try to Refresh Fabric Warehouse get an error An item with the same key has already been added

v-prasare — Thu, 26 Mar 2026 09:32:38 GMT

Thank you for sharing the update and confirming the resolution. We appreciate your insights as they will be helpful for other community members facing similar issues.

If you have any further questions or encounter new challenges, please feel free to reach out by posting a new thread in the Microsoft Fabric Community—we’ll be happy to assist.

Re: When try to Refresh Fabric Warehouse get an error An item with the same key has already been added

valeria_dia — Mon, 27 Apr 2026 21:57:58 GMT

Microsoft confirmed, that the issue was fixed

"Our Product Group has confirmed that a hotfix has been deployed to address the Fabric UI metadata synchronization issue that was impacting the visibility of tables and schemas in the Warehouse UI."

I checked and it seems working now as expected.