You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I used the preview feature of downloading a PBIP of my wire frame and developed a reporting template for my organisation.
I want to distribute this on our teams homepage as a PBIX or PBIT (as most users don't have the PBIP preview feature enabled)
However when saving as another format to distribute I get the following error (note, I had to use the export save as template option to generate the stack trace attached.)
"Unable to save document" "Isn't a valid file path"
I simplified the path as much as I could as I saw posts about failing due to path length but to no avail.
Additionally, I've attached a stack trace based off a much simplified theme with just a background colour applied.
There is bug in the PBIP format that we are aware of that does not like the Background Images containing spaces in the names. Try switching out the background images with file names that do not have spaces in them. We tried to fix this inside the app but seems like desktop is still a bit buggy with spaces in names.
I used the preview feature of downloading a PBIP of my wire frame and developed a reporting template for my organisation.
I want to distribute this on our teams homepage as a PBIX or PBIT (as most users don't have the PBIP preview feature enabled)
However when saving as another format to distribute I get the following error (note, I had to use the export save as template option to generate the stack trace attached.)
"Unable to save document" "Isn't a valid file path"
I simplified the path as much as I could as I saw posts about failing due to path length but to no avail.
Additionally, I've attached a stack trace based off a much simplified theme with just a background colour applied.
Themes stack trace.txt
I checked the MS docs and it states it is possible to move back and forth with these formats using save as.
The text was updated successfully, but these errors were encountered: