Datawarehouse Subfolder DisplayNameValidationFail Error while syncing git branch to new workspace

[Gerrelt]

Hi all,

I am trying to sync the main git branch to a new fabric workspace, but I am getting this error on the datawarehouse:

Cluster URI https://wabi-west-europe-e-primary-redirect.analysis.windows.net/

Request ID d25d1726-afe5-4d70-9bd8-7b1199299698

Workload Error Code Subfolder Error_DisplayNameValidationFail

Time Tue Oct 14 2025 15:43:49 GMT+0200 (Midden-Europese zomertijd)

It doesn't say which part of the datawarehouse has the validation fail or what didn't pass validation.

Does anybody know what's going on here?

[v-priyankata]

Hi @Gerrelt 

Thank you for reaching out to the Microsoft Fabric Forum Community.

@grazitti_sapna @KevinChant Thanks for the inputs

I hope the information provided by users was helpful. If you still have questions, please don't hesitate to reach out to the community.

[Gerrelt · Accepted solution]

Thank you for your replies.

I solved it, and, indeed, it was something with the folder structure.

In GIT, the fabric files were stored under a ".Fabric" directory, but I did not set that as the GIT folder.

After setting the GIT folder to ".Fabric", it started working.

Here in the workspace settings I had to set the folder:

[grazitti_sapna]

Hi @Gerrelt 

The error you mentioned usually indicates folder naming conflicts or unsupported nested folder structures. Currently, Microsoft Fabric Git integration supports mostly flat folder hierarchies, so deeply nested folders or invalid folder names can cause validation failures.
To fix this, rename folders/subfolders to simple names without special characters, avoid duplicate display names for warehouses or other objects, and consider flattening your folder structure in your workspace. Manual conflict resolution in Git may also be necessary before syncing. 
Always verify object name consistency across branches to avoid sync conflicts.

🌟 I hope this solution helps you unlock your Power BI potential! If you found it helpful, click 'Mark as Solution' to guide others toward the answers they need.

💡 Love the effort? Drop the kudos! Your appreciation fuels community spirit and innovation.

🎖 As a proud SuperUser and Microsoft Partner, we’re here to empower your data journey and the Power BI Community at large.

🔗 Curious to explore more? [Discover here].

Let’s keep building smarter solutions together!

[KevinChant]

Have you tested connecting to the same branch in a separate workspace to see if the error still happens there?