report link to dataset broken

[morganus]

Hello all,

My team and I recently switched from PBIX to PBIP on our Premium workspace and if everything worked like a charm for composite models using my dataset as one of the sources, reports were broken.

I was prompted to re-create the link to the dataset and it worked for all reports hosted on premium worspaces, but not for reports being hosted on personal workspace.

In fact, when trying to re-link the report from a personal workspace, every user gets the following error message:

Can please somebody help ?

Thanks !

[ibarrau · Accepted solution]

Hi. I think the issue is about the premium. Saving as pbip is a preview feature that is still on development as a combination with git integration. For now both of them are premium features. Getting data from that dataset created with pbip and publishing to a shared capacity might produce an error, that's not compatible and doesn't have a documentation yet.

I would say the reports created from the dataset pbip should be hosted at a premium or dedicated capacity workspace. Publishing to "My workspace" for any reports that will be shared later it's not a good practice. 

I hope that make sense.

[morganus]

Thanks Ibarrau,

With the team we reached more or less the same conclusion but it's conforting hearing the same from experts.

Any idea if and how we could open or retrieve said reports to republish them into a dedicated workspace ?

Thanks again !

[ibarrau]

Well you need to forget about "Publishing" when working with PBIP for now. The way it will only work is syncing with an Azure DevOps repo. Create the Git Integration of the workspace sync it with the branch of the repo you want. Then save the PBIP folder to the repo. After Pushing the changes in there, the publishing will occur automatically.

Your daily changes would be turn on machine, pull request to get the last version of repo, open pbi desktop, modify, then commit and push again. No more publishing.

If some changes have conflict you might need to get in PowerBi Service after solving the conflict at repo to pull at service I think.

I hope that helps,