Forum Discussion

Geetha21's avatar
Geetha21
Frequent Visitor
1 year ago
Solved

Issue with power bi git integration when I switch the branch

Hi,   My workspace is integrated with power bi git integration. I have few dashboards in git branch(test_a). I need to switch the branch to test_b. Some dashboards in test_b branch is already exi...
Need Help
  • Geetha21's avatar
    Geetha21
    1 year ago

    Hi Anonymous ,

     

    The issue was in report.json file. The bug was resolved from microsoft side, nothing was done on my end. I just reported the issue to Microsoft to resolve it.

     

tomordonezmiron's avatar
tomordonezmiron
Frequent Visitor
1 year ago

I have the exact same issue and I think it's a PBI service bug that seemed to be introduced in the last few days. I tried removing the git repo from the workspace, deleting all objects from the workspace, and connecting the repo again. Same error. Also tried creating a new workspace and connecting the repository. Same error. Power BI must have broken something related to custom visuals and TMDL, not being able to parse the report.json when it has custom visuals.

  • Geetha21's avatar
    Geetha21
    Frequent Visitor
    1 year ago

    Thanks for the reply. I highly appreciate. Yes thats right. Something was wrong on power bi side.

    Now it has been resolved. I can able to switch the branch now without any issues.

    • Anonymous's avatar
      Anonymous
      Not applicable
      1 year ago

      Hi Geetha21 

       

      Glad to know you solved the problem.

      Could you please share your solution? This will make it easier for other users with the same problem to find it and benefit from it.

      Thank you in advance for your cooperation!

       

      Best Regards,
      Jarvis Tang
      If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

      • Geetha21's avatar
        Geetha21
        Frequent Visitor
        1 year ago

        Hi Anonymous ,

         

        The issue was in report.json file. The bug was resolved from microsoft side, nothing was done on my end. I just reported the issue to Microsoft to resolve it.