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
Super UserHi 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
Continued ContributorPower BI Desktop caches custom visuals and downloads the latest version of the visuals from the CDN network once in a while. Probably that is the reason that clumsy is not always working.
So indeed changing the GUID to a temp version is the preferred way to (extra) test your visuals in Power BI Desktop.
-JP