Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Shape the future of the Fabric Community! Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions. Take survey.

Reply
BIanon
Resolver I
Resolver I

Saving thin report as .pbip results in error when opening

Hi,

I saved a thin report file (connected to semantic model in service) as a .pbip folder, but when I try to open either the .pbip or definition.pbir file afterwards, I get the following error:

BIanon_0-1731583979051.png


I've checked references in definition.pbir and the .pbip file and it all looks good so I'm at a loss for what could be the issue here, I've never experienced this issue before using PBIP/PBIR

6 REPLIES 6
MFelix
Super User
Super User

Hi @BIanon ,

 

Did this error ocurred after making changes to the report or after saving it has a PBIP it gave the error even without any changes?


Are you using the new enhanced PBIP format or the previous one?

You can check it on the preview features:

MFelix_0-1731607398270.png

 


Regards

Miguel Félix


Did I answer your question? Mark my post as a solution!

Proud to be a Super User!

Check out my blog: Power BI em Português



I'm using the new enchanced metadata format as publishing to service is supposted as of the October release

Thejeswar
Community Champion
Community Champion

Hi @BIanon ,

By thin reports, I believe you are mentioning a Live Connected report where your dataset sits separately in Power BI Service and you connect your report to it.

 

Per my understanding, both PBIP and PBIR format don't support using with Live Connected Reports as of today.

 

So I don't think you can save your file in these format if they are live connected

 

Regards.

Sure you can

setup your .pbip to point to the report you want fused into the semantic model file (if any)

.pbip

{
  "version": "1.0",
  "artifacts": [
    {
      "report": {
        "path": "customerName.Report\\subdir"
      }
    }
  ],
  "settings": {
    "enableAutoRecovery": true
  }
}

this way my .pbip will open the report located in the \\subdir

you also have to edit the difinition.pbir file to go up one more dir so instead of ../ you just do ../../

{
  "version": "4.0",
  "datasetReference": {
    "byPath": {
      "path": "../../customerName.SemanticModel"
    },
    "byConnection": null
  }
}

 

for the thin reports you just use a conn string definition.pbir instead of a local path ref

{
  "version": "4.0",
  "datasetReference": {
    "byPath": null,
    "byConnection": {
      "connectionString": "Data Source=powerbi://api.powerbi.com/v1.0/myorg/customerName;Initial Catalog=\"customerName\";Access Mode=readonly;Integrated Security=ClaimsToken",
      "pbiServiceModelId": null,
      "pbiModelVirtualServerName": "sobe_wowvirtualserver",
      "pbiModelDatabaseName": "semantic-model-id",
      "name": "EntityDataSource",
      "connectionType": "pbiServiceXmlaStyleLive"
    }
  }
}

then you just publish or deploy the definition.pbir file of the thin reports to the service


this way you can also have a structure like this:
name.Report
      report1
            .pbir report definition with enchanced metadata format
      report2
      report3
name.SemanticModel
      SemanticModel definition
name.pbip


works well for me at least




Hi @BIanon,

 

Did you made any changes to the semantic model online?

 

Open the PBIR file in notepad or VisualStudio Code and check if the connections string values and database ID are correct to the one online.

MFelix_0-1731662468108.png

 

 


Regards

Miguel Félix


Did I answer your question? Mark my post as a solution!

Proud to be a Super User!

Check out my blog: Power BI em Português



I've double checked this and all values in definition.pbir are correct

Helpful resources

Announcements
November Carousel

Fabric Community Update - November 2024

Find out what's new and trending in the Fabric Community.

Dec Fabric Community Survey

We want your feedback!

Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions.