Forum Discussion

afbraga66's avatar
afbraga66
Icon for Helper III rankHelper III
2 years ago
Solved

Thin Reports and Git Integration

Hey,

 

So I have an issue.

I've got a report that is connected to a dataset in power bi service through live connection aka thin report.

Whenever I save changes and push them into the repository in Azure Devops, it detects those changes on the Updates tab on Power BI workspace that is connected. So far, so good.

I update all in Power BI, and it immediatly creates a change afterwards. When I commit the change it removes the live connection and turns the report into import. I see this in the commit that is creates on Azure Devops and also when I open the report after pulling into my local workspace.

Has anyone faced this issue before? Any work arounds? Or there is simply no support for this at the moment?

It seems weird because separating the semantic model and the report in separate files is development strategy mentioned by Microsoft. Thanks.

 

Need Help
  • Jannematz's avatar
    Jannematz
    2 years ago

    How does the definiton.pbir of your report look like?

    {
  "version": "1.0",
  "datasetReference": {
    "byPath": {
      "path": "../DatasetName.Dataset"
    },
    "byConnection": null
  }
}

    like this it should work if your dataset is in the same repo.

    If it is not: Check for spaces in the byConnection url in the defintion.pbir. The service does not like those and replaces them wiith %20. So you need to URL encode your connection strings in the thin reports.

    I hope this helps!

3 Replies

  • GilbertQ's avatar
    GilbertQ
    Icon for Super User rankSuper User
    2 years ago

    Hi afbraga66 

     

    I would expect this to work.

     

    If it is changing it to an import to me that is an issue that needs to be resolved.

    • afbraga66's avatar
      afbraga66
      Icon for Helper III rankHelper III
      2 years ago

      Hey GilbertQ 

      That's why I wanted to ask the community, since thin reports are one of the development strategies mentioned by Microsoft. It seems strange to me not seeing anyone mentioning this subject.

      If you or others have the chance to test it as well it would be great.

      While this doesn't make using versioning an impossibility, it is one for the use of git and deployment pipelines.

      Thanks.

  • Jannematz's avatar
    Jannematz
    Frequent Visitor
    2 years ago

    How does the definiton.pbir of your report look like?

    {
  "version": "1.0",
  "datasetReference": {
    "byPath": {
      "path": "../DatasetName.Dataset"
    },
    "byConnection": null
  }
}

    like this it should work if your dataset is in the same repo.

    If it is not: Check for spaces in the byConnection url in the defintion.pbir. The service does not like those and replaces them wiith %20. So you need to URL encode your connection strings in the thin reports.

    I hope this helps!