We are developing a custom visual and are having problems with deploying new versions. Here's what we are doing:
1. We have an existing visual, let's say that the version is 1.0.0.
2. We add some new functionality to it.
3. We increase the version number, let's say to 1.0.1.
4. We package the visual using pbiviz package.
5. We deliver the visual to a end user who imports the visual to the Power BI online.
Until now everything works just fine and the visual on the report, where he imported the visual, work fine. That is: the new version of the visual is shown. However, if the end user now saves the report and reloads the page (or comes back to it later), the report is using the old visual again. Sometimes this reverts not only to the previous version but even to a much older version of the visual.
It seems that this is the same issue as this one for the Desktop version of Power BI:
http://community.powerbi.com/t5/Developer/Problems-updating-Custom-Visuals-in-Power-BI-Desktop/m-p/3...
Increasing the GUID is not really an option since it would mean that the end user now has to redo all the reports that were done with the previous version of the visual.
Isn't there a way to offer a smooth upgrade process for custom visuals?
