An object with name '<ccon></ccon>' already exists in the collection.

[krishnc]

While comitting the Datawarehouse to the GIT I am getting the following error. Anyone faced this issue? Please suggest a solution to identify the duplicate object. I am unable to find the object with the given id.

[krishnc]

Thanks for checking brother.. I tried all possible options but in vain. I would like to recreate my rename my DataWarehouse and create a new DW and import all objects into this and try. Any suggestions?

[v-tsaipranay · Accepted solution]

Hello @krishnc ,

Thank you for the update. Your proposed approach to rename the existing Data Warehouse, create a new instance, and import all objects into it is valid particularly in scenarios where metadata inconsistencies may be causing persistent issues. We recommend exporting all objects using SQL scripts or Fabric’s export options, and initially avoiding Git integration until the new Data Warehouse is fully validated. When ready, link the new instance to a clean Git branch or repository to prevent reintroducing previous conflicts. Additionally, we suggest retaining the original Data Warehouse temporarily as a fallback until the new setup is confirmed to be working as expected.

If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.

Thankyou.

[v-tsaipranay]

Hi @krishnc ,

Thank you for reaching out to the Microsoft Fabric cummunity forum.

The error "An object with name '<ccon>' already exists in the collection". This indicates a naming conflict, and since you can’t locate the object, it’s likely a system-generated artifact or a metadata glitch.

To resolve this, please check your Datawarehouse in Fabric’s workspace across all schemas and system areas for any object resembling `<ccon>`, then review the Git commit changes to see if `<ccon>` appears in the staged files or repo history. If found, rename or remove the duplicate to clear the conflict; if not, disconnect and reconnect the Datawarehouse to Git in Fabric settings to reset the sync. To prevent future conflicts, ensure unique object names and keep your workspace and Git repo aligned.

please refer the following microsoft documentations for more details:
Known issue - Sync content from Git in workspace fails - Microsoft Fabric | Microsoft Learn

Resolve conflicts with Git integration - Microsoft Fabric | Microsoft Learn

I hope my suggestions give you good idea, if you need any further assistance, feel free to reach out.

If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.

Thankyou.

[v-tsaipranay]

Hi @krishnc ,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.

Thank you.

[krishnc]

Thanks for checking. I could not figure out the duplicate object. There is no such object at all in the files or I dont see it. Disconnect and reconnect the Datawarehouse to Git also did not help. 😞

[v-tsaipranay]

Hi @krishnc ,

Thank you for your patience. Since the duplicate object is not visible in your files and reconnecting the Datawarehouse to Git did not resolve the issue, we recommend taking a few additional steps.

First, please review all tables, views, and schemas within the Datawarehouse, as some objects may not be immediately visible in standard views. If your Datawarehouse is linked to Git, manually inspect the repository’s commit history and metadata files for any references to the missing object.

If the issue persists, try fully disconnecting Git, ensuring that no residual metadata remains, and then reconnecting. Additionally, attempting the sync on a fresh Git branch may help resolve hidden inconsistencies. If none of these steps work, this could be a metadata-related issue, and we recommend checking for any ongoing Microsoft Fabric service disruptions.

If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.

Thankyou.

[v-tsaipranay]

Hi @krishnc ,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.

Thank you.