Fabric Migration Issue

[SaswataMondal]

We were facing this issue while migrating from the Fabric Dev to the Fabric UAT workspace (screenshot 1). Screenshot 1

For resolution, we followed these steps:

• We identified the specific PR after which this issue started.
• We reverted almost all PRs and merges before that PR and checked after each revert if the issue was resolved.
• For some PRs, we got conflict issues. We also tried resolving them locally using VS Code, but were unable to fix the conflicts completely. (Screenshot 2)
• We informed both Vrunda and Saiteja about this, but they were also not able to help much further.

  We suggested deleting the currently created folder from the UAT workspace and then raising and merging a fresh PR, as that would automatically resolve the issue. However, the POCs have asked us to take the revert approach only.

[v-hjannapu · Accepted solution]

Hi @SaswataMondal,

Thanks for sharing the details and screenshots.

This error usually comes when the Git folder name or structure in the repo is not supported  for example, if there are spaces, special characters, or if some conflicts changed the folder path.

Since you already reverted a few PRs and tried resolving conflicts, I would suggest checking the folder names once in your repo and making sure they follow the supported naming format.

If everything looks fine but the issue still appears, try disconnecting and reconnecting the UAT workspace to the Git branch once. If that also doesn’t work, creating a new folder or branch and syncing again should fix it.

Hope this helps if you have any queries we are  happy to assist you further.
Regards,
Community Support Team.

[v-hjannapu]

Hi @SaswataMondal,
I hope the information provided above assists you in resolving the issue. If you have any additional questions or concerns, please do not hesitate to contact us. We are here to support you and will be happy to help with any further assistance you may need.

Regards,
Community Support Team.

[v-hjannapu]

Hi @SaswataMondal,
I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We are always here to support you.


Regards,
Community Support team.