Open ignatvilesov opened 7 years ago
As of September 1st only API 1.2 and above will be supported.
What does this mean for you as a custom visual developer?
The absolute majority of custom visuals are built on top of API version 1.2 and above, however, if you have an older version of your custom visual that was built using tools published earlier than September 2016, they may be using deprecated APIs. You can verify the API version of your visual by looking at the pbiviz.json file at the "apiVersion" property.
What should you do?
In case you are using deprecated APIs, you may want to migrate to a supported API (1.2 and above) to avoid potential breaks for your visuals. It is recommended to occasionally update your custom visual with latest tools and APIs to benefit from the latest and greatest features and enhancements. As of the September Power BI release, we will issue a warning to report authors for each visual using a deprecated API in both Power BI desktop and web (edit mode) with the following statement:
“This visual is using an old and unsupported version of interface and will be deprecated soon. Please replace this visual with an alternative one from our in-house or marketplace visuals.”
Your visual was marked as deprecated and will probably stop rendering in Power BI soon because it still uses API 1.1 that is obsolete. We recommend to update the visual and contact us (pbicvsupport@microsoft.com) to restore it's functionality.
We’ve noticed that Start (PBI_CV_9053509D_D461_463A_B485_CE9F6AB0F13C) is based on API 1.1. This version of API doesn’t include performance improvements. We recommend that you should upgrade your custom visual to the latest version of API (1.7).
Could you please consider this suggestion in upcoming updates?
Please also share your email because the previous one is no longer valid.
Ignat Vilesov, Software Engineer
Microsoft Power BI Custom Visuals pbicvsupport@microsoft.com