Performance issues opening specific pages

It all started when we noticed in Telemetrics that some of our customers have performance issues. Since the product facing this problem is POS Solution, where everything needs to be very fast, we cannot tolerate issues like this one. Besides that, how do you explain to a customer that a new shiny ERP solution does not work as fast as it should?

Source : Milan Milinčević
Read more…

Performance & Variables exposed as field on a Page

I just wanted to add a flow field to a table to look up some value, and display it on a list page. After some time I realized that this wont work. Im my case I needed to go three table relations deep to get out the value I needed. But just chaining two FlowFields would already be enough to see this mission failing.

Source : Stefan Maroń
Read more…

Dynamics 365 Business Central: the impact of tableextensions

I think that everyone of you already knows that when working with Dynamics 365 Business Central, table extensions are killers for performances. But how much?

That’s a question that I’ve also done to myself a lot of time when working with partners or when creating my own solutions. Is there a “deadline” for how many table extensions can I create for the same table in order to not kill my performances?

Source : Stefano Demiliani
Read more…

Power BI Report Performance And The Number Of Visuals On A Page

When you’re faced with a slow Power BI report it’s very easy to assume that the problem is something to do with the dataset, how it’s modelled and how the DAX has been written, and then disappear down a rabbit hole of Marco-and-Alberto videos trying to shave milliseconds of the time taken by each DAX query the report runs.

Source : Chris Webb’s BI Blog
Read more…

Optimising The Performance Of Power Query Merges In Power BI, Part 3: Table.Join And SortMerge

When you merge data from two queries in the Power Query Editor the M code generated uses the Table.NestedJoin function. There is, however, another M function that can be used to merge data: Table.Join. The interesting thing about this function is that has a parameter that Table.NestedJoin doesn’t have: the joinAlgorithm parameter allows you to specify the algorithm used by the Power Query engine for the merge.

Source : Chris Webb’s BI Blog
Read more…