Following on from the series of posts I wrote last month (starting here) about testing the performance of Power BI reports in the browser, I would now like to highlight one possible cause of slow report rendering performance: the over-use of custom visuals. Before we go any further, though, let me be absolutely clear about something:
Recently I attended an excellent session by Andy Kirk on the state of data visualization for 2019. One of the tools Andy is most excited about is called Charticulator. For those of you that haven’t heard about it, Charticulator is an open source project from Microsoft Research. Using a web UI you can design almost any charts by interactively specifying constraints (NO code).
Yesterday we stuck with an issue for a customer which we recently upgraded to Business Central 13.x on-prem. It took time to find the solution so I thought to share a solution with everyone.
Issue Description – Report using custom Barcode Font does not work with Web client but works with the windows client.
Now that we can apply custom format strings to fields and measures in Power BI in the September 2019 release, I thought it would be useful to provide some examples of what’s possible with this very flexible new feature because the existing documentation for VBA isn’t easy to make sense of. In fact there’s so much to say I’m going to have to write a series of blog posts to cover everything! In this first post I’m going to look at formatting numbers.
When we do Microsoft Dynamics Business Central or Dynamics NAV development, one of our goals is to minimize the work required during an upgrade. When it comes to report customizations, we can handle this by using a custom report layout instead of modifying an existing report. It’s easier to upgrade, and it’s not any harder than modifying the existing report layout. I’ll talk you through custom report layout limitations, how you can make a custom report layout, and why you would want one.
There’s a new, as yet undocumented, option for the Web.Contents() M function that is only available for custom data connectors and not in Power BI Desktop: CredentialQueryOption. It does the same thing as the Query option, but it stops the values you are passing to the query parameter from being logged in Power BI’s diagnostic logs, so it’s useful if you are passing sensitive information such as passwords.