This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreDid you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now
This blog post covers the latest updates for the Power BI Developer community. Don’t forget to check out our last developer blog posts, if you haven’t done so already.
Here is the list of updates for this month:
Power_BI_Developer_community_August_2020_update
To reset the persistent filters in an embed scenario, developers will need to implement a button and use the Reset persistent filters API. Other Persistent filters APIs include Save persistent filters and Persistent filters applied, used to determine the ‘Reset’ button state.
Power_BI_Developer_community_August_2020_update
powerbi.embed. Once called, the embedded report is loaded in front of the end-user, and any interaction with the report is done while shown to the end-user. To improve the end-user experience and provide more flexibility for developers, we have extended this flow with API calls that add phases to the embedding process for report embed. powerbi.load(...) allows developers to stop the report from rendering, and to interact with the report before the end-user can see the results. As an example, developers can use it to get pages and then decide which page to present to the end-user. Once the load is completed, a 'loaded' event is fired.
In case developers use powerbi.load(), they need to use report.render() to continue the report rendering. A 'rendered' event will be fired once the render is completed
Phased embedding example:
const config = {
...
};
var report = powerbi.load(config);
report.on('loaded', async () => {
await report.setFilters(fitlers);
report.render();
});
Now we’ve added a parameter that can be used to disable this behavior. By setting the optional ‘autofocus’ parameter value to false, in createVisual and cloneVisual, the page will no longer focus on the new visual and it would be possible to add multiple visuals programmatically without forcing the page to focus each time on the last added visual.
Up to now in Power BI embedded analytics there was only a limited control of the Power BI panes, achieved by three distinct properties: filterPaneEnabled, bookmarksPaneEnabled and navContentPaneEnabled.
To allow greater control over the existing panes and to make it easier to support new panes in the future, we added a new 'panes' object to the Power BI embedded settings, that unifies all the existing ‘panes’ properties and adds support for controlling more panes programmatically. For example, it is now possible to open an embedded report in edit mode with all the panes collapsed, allowing the report itself more space. It is also possible to open the Sync slicers and Selection panes programmatically.
Visual authoring data field enhancements
Previously, when adding a data field to a visual data role, the data field would be added last. Now we’ve added an optional ‘index’ parameter to define where the data field should be added. This option provides developers the flexibility to build the visuals they need, for example, they can add a column to the middle of an existing table.
Relative Time Filters/Slicers support
Power BI JavaScript APIs allow to apply filters and slicers when loading a report and change them dynamically. Various Filter types and Native slicers are already supported and now we’ve added support for RelativeTime filter type which also applies for slicers.
Extend page operations
As part of the Page Operations API, developers can now add and delete pages from a report during an embed session.
‘Visual Rendered’ event
A new visualRendered event was recently added to the list of supported events, and it can be useful for developers that want to show reports to their end-users only after a specific or several visuals have completed rendering.
Enabling the firing of this event requires setting visualRenderedEvents to ‘true’ in the settings object. It is recommended to enable it only when necessary.
Learn more on handling events in Power BI Embedded
Power_BI_Developer_community_August_2020_update
Power_BI_Developer_community_August_2020_update
Power_BI_Developer_community_August_2020_update
Typically, users hover over data points in a visual for the right-click menu to be available.
To provide a unified and smooth experience to all users using any Power BI visuals, we recommend that our developers and partners enable the context menu in their existing and new visuals' submissions. We have also updated our guidelines for Power BI visuals.
Power_BI_Developer_community_August_2020_update
We want to keep improving our AppSource visuals. Visuals that are in-par with the default ones. For the best customer experience, it is very important to preserve the same look and feel experiences for the AppSource visuals. We recommend to keep updating the visuals with the latest API release. In addition, to support the features as documented in our How-To guides, such as report page tooltips and drill down features.
This is a heads-up that we'll add this new requirement of supporting the context menu to our submission process for any new submitted visuals or any updates of existing visuals.
The policy will take action on the first of September.
The new API supports the Multi visuals select feature which allows to use selection in multiple visuals in a report.
That’s all for this post. We hope you found it useful. Please continue sending us your feedback – it’s very important for us! Have an amazing feature in mind? Please share it or vote in our Power BI Ideas forum
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.