Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG: After downloading PBIP cannot save as PBIX or PBIT #30

Open
VizRich opened this issue Dec 1, 2023 · 1 comment
Open

BUG: After downloading PBIP cannot save as PBIX or PBIT #30

VizRich opened this issue Dec 1, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@VizRich
Copy link

VizRich commented Dec 1, 2023

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.

image

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.

@MikeCarlo
Copy link
Contributor

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.

@MikeCarlo MikeCarlo added the bug Something isn't working label Dec 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants