Forum Discussion
"pbiviz package" does not update visual's capabilities, but "pbiviz start" does
Okay I figured it out - I recently put this visual into the AppSource store and I believe that was why I couldn't see any changes to the Capabilities. My solution was to change the "guid" in the pbiviz.json file and now I see a the new Capabilities.
You're absolutely correct. Power BI loads CV from our CDN if the visual is approved by App Source.
That means that you should use another GUID or pbiviz start for development purposes.
Ignat Vilesov,
Software Engineer
Microsoft Power BI Custom Visuals
Okay I figured it out - I recently put this visual into the AppSource store and I believe that was why I couldn't see any changes to the Capabilities. My solution was to change the "guid" in the pbiviz.json file and now I see a the new Capabilities.
Community ChampionYou're absolutely correct. Power BI loads CV from our CDN if the visual is approved by App Source.
That means that you should use another GUID or pbiviz start for development purposes.
Ignat Vilesov,
Software Engineer
Microsoft Power BI Custom Visuals
- jppp
Continued Contributor
An other option with the Power BI service is: add '?approvedResourcesDisabled=true' to the url to skip the CDN loading of approved visuals.
-JP
Hi I've tried running the command: pbiviz start from it's root directory and yet I keep getting the error message:
could anybody help me with this?
I've generated the local SSL certificate and even installed the same step-wise sequentially
- v-viig
What node.js version do you use?
Ignat Vilesov,
Software Engineer
Microsoft Power BI Custom Visuals
- Nishantjain
Is there a similar option for Power BI Desktop. I am trying to test a new version of my visual in Power BI Desktop but it suffers with the same problem that it is loading the approved version from CDN instead of the local pbiviz file that I have.
Thanks
Nishant
- dm-p
Super User
Hi Nishantjain,
To test updating an already published visual in Power BI Desktop, the only solution I've found that works for me is to temporarily modify the GUID, package and test, as per this post's solution. It makes it tricky ensuring that everything is ready prior to submission to the marketplace - although as long as the latest version of your visual code is uploaded into your sampl workbook, even though it displays the previous version, it will submit okay.
Alternatively, I've had mixed results by using tools such as clumsy to block access to my network when I load the visual via desktop so that the CDN call can't go through and load the marketplace version. This isn't always consistent for me though, so the GUID change is usually what I do.
Not sure if this helps much, but thought I'd weigh in.
Daniel
