Forum Discussion
Live connection error when save as pbip report
Well, Found the problem.
Functionality "Save as" is different for PBIX and PBIP
The issue was I had a "blank" at the end of the workspace where I deployed the semantic model.
- When saving as PBIX the where no issues, as the report was connected with no issues.
- When saving as PBIP the issue was that PBI desktop "trim" the connection string, removing the "Blank" from workspace name where the semantic model whas hosted and creating the problem.
Solution: rename the workspace to remove the blank from the name at the end and all started working well.
Hi,
This appears to be related to how PBIP stores the live connection metadata, rather than an issue with the semantic model itself. Since the same report works when saved as a PBIX, it suggests the connection and permissions are valid.
A few things you can check:
- Verify the PBIP connection metadata (.pbir/.pbip files) to ensure the semantic model ID and workspace ID haven't changed or become invalid.
- Ensure you're using the latest version of Power BI Desktop, as there have been fixes for PBIP and Fabric integration in recent releases.
- Try creating a new PBIP project and reconnecting to the semantic model from scratch to rule out project corruption.
- Confirm you have Build permission on the semantic model (Workspace Admin usually includes this, but it's worth verifying if permissions were recently modified).
- If the semantic model was renamed, moved to another workspace, or republished, the PBIP project may still reference the old metadata.
Since this works correctly as a PBIX but consistently fails after reopening a PBIP, it could also be a product issue/regression with PBIP rather than a configuration problem.
If possible, could you share:
- Your Power BI Desktop version.
- Whether the semantic model is in the same Fabric workspace as the report.
- Whether this happens with all live-connected semantic models or only this specific one.
That information will help determine whether this is a configuration issue or a known PBIP limitation/bug.
Thanks!
Well, Found the problem.
Functionality "Save as" is different for PBIX and PBIP
The issue was I had a "blank" at the end of the workspace where I deployed the semantic model.
- When saving as PBIX the where no issues, as the report was connected with no issues.
- When saving as PBIP the issue was that PBI desktop "trim" the connection string, removing the "Blank" from workspace name where the semantic model whas hosted and creating the problem.
Solution: rename the workspace to remove the blank from the name at the end and all started working well.