Question about Report content definition.pbir section attribute

[ddelapasse]

Hi!  I've been requested to allow 'cloning' of reports from one workspace to another.  The db fields are the same, BUT the modelnames will be different.  I've been able to do this within a workspace, but I must be missing some piece to the puzzle when I cross workspace boundaries.

I have a good reason to avoid the clone api method and instead am pulling the source content, modifying it and pushing it into a newly created report at the destination.  All of this passes thru the apis without error, but the report doesn't show the proper data (even tho it DOES appear to be linked to the correct model).  I'm taking the content section by section and updating the model reference guids but I just noticed the "definition.pbir" section contains both the workspace NAME (which seems odd) and then has an ID that I cannot figure out.   

Can anyone tell me what the "pbiModelDatabaseName" reference is pointing to (I've masked it below but points to a valid looking guid)?
{
  "version": "4.0",
  "datasetReference": {
    "byConnection": {
          "connectionString": "Data Source=\"powerbi://api.powerbi.com/v1.0/myorg/{workspaceName}\";Initial Catalog=          {modelname};Integrated Security=ClaimsToken",
          "pbiServiceModelId": null,
          "pbiModelVirtualServerName": "sobe_wowvirtualserver",
          "pbiModelDatabaseName": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
          "name": "EntityDataSource",
          "connectionType": "pbiServiceXmlaStyleLive"
          }
   }
}

[v-sdhruv]

Hi @ddelapasse ,
Just wanted to check if you had the opportunity to review the suggestions provided by the Super Users? 
If the response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you

[v-sdhruv]

Hi @ddelapasse ,
Just wanted to check if you had the opportunity to review the suggestions provided by the Super Users? 
If the response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you

[v-sdhruv]

Hi @ddelapasse ,
Following up to check whether you got a chance to review the suggestion given. If the issue still persists please let us know.
If the response has addressed your query, please accept it as a solution and give a ‘Kudos’ so other members can easily find it. 
Thank You

[SaiTejaTalasila · Accepted solution]

Hi @ddelapasse ,

Datasets have unique GUIDs per workspace, cloning a report across workspaces requires updating this value to match the target dataset's GUID. To fix your issue, retrieve the destination dataset's GUID using the Power BI REST API (/groups/{workspaceId}/datasets), then replace the old GUID in pbiModelDatabaseName. Ensure the connection string is also updated with the correct workspace and model name before repackaging and publishing the report.

I hope it helps.

Thanks,

Sai Teja