As I’m sure you’ve guessed by now I’m a big fan of dynamic M parameters in Power BI. They’re easy to use in Power BI Desktop but what if you want to use them in your own DAX queries? Documentation for this is coming soon, but in the meantime I thought it would be useful to show the additions to DAX query syntax to support them – something you can see for yourself if you take a look at the DAX queries generated by Power BI Desktop using Performance Analyzer.
With the QueryCategory property we can execute a query object from a page (also available in Smartlists) by defining a query in AL; it is possible to declare with a comma separated list where the object can be used, in practice it is added to the list of objects published in the SmartList.
If you’re familiar with the topic of query folding in Power Query, you’ll know that the View Native Query right-click option in the Applied Steps pane of the Power Query Editor can be used to show the native query that is run against the data source. You may also know that there are some data sources where query folding does take place but where View Native Query remains greyed out.
In the April release of Power BI Desktop the Power Query Query Diagnostics feature was enhanced so that you can now return performance counter data. As the blog post says:
When you run performance counters, every half second Power Query will take a snapshot of resource utilization. This isn’t useful for very fast queries but can be helpful for queries that use up a lot more resources.
Currently there’s a lot of talk about Business Central performance. Microsoft has released and is releasing guidelines, tools about mechanisms to program for performance, analyse and monitor performance. At the same moment there’s also discussions going on on public and private fora about database size and limitations. And last but not least Artificial Intelligence is also a hot topic, making Business Central smarter, so it can help you in your daily business.