Thursday, March 17, 2022
HomeBusiness IntelligenceOptimising OData Refresh Efficiency in Energy Question for Energy BI and Excel

Optimising OData Refresh Efficiency in Energy Question for Energy BI and Excel

OData has been adopted by many software program options and has been round for a few years. Most options are utilizing the OData is to serve their transactional processes. However as we all know, Energy BI is an analytical resolution that may fetch lots of of hundreds (or thousands and thousands) rows of information in a single desk. So, clearly, OData just isn’t optimised for that sort of objective. One of many greatest challenges many Energy BI builders face when working with OData connections is efficiency points. The efficiency depends upon quite a few elements equivalent to the dimensions of tables within the backend database that the OData connection is serving, peak learn information quantity over intervals of time, throttling mechanism to regulate over-utilisation of sources and many others…

So, usually talking, we don’t anticipate to get a blazing quick information refresh efficiency over OData connections, that’s why in lots of circumstances utilizing OData connections for analytical instruments equivalent to Energy BI is discouraged. So, what are the options or alternate options if we don’t use OData connections in Energy BI? Nicely, the perfect resolution is emigrate the info into an middleman repository, equivalent to Azure SQL Database or Azure Knowledge Lake Retailer or perhaps a easy Azure Storage Account, then join from Energy BI to that database. We should resolve on the middleman repository relying on the enterprise necessities, know-how preferences, prices, desired information latency, future help requirement and experience and many others…

However, what if we would not have every other choices for now, and we’ve got to make use of OData connection in Energy BI with out blasting the dimensions and prices of the venture by shifting the info to an middleman area? And.. let’s face it, many organisations dislike the thought of utilizing an middleman area for numerous causes. The best one is that they merely can’t afford the related prices of utilizing middleman storage or they don’t have the experience to help the answer in long run.

On this put up, I’m not discussing the options involving any alternate options; as a substitute, I present some suggestions and methods that may enhance the efficiency of your information refreshes over OData connections in Energy BI.


The guidelines on this put up won’t provide you with blazing-fast information refresh efficiency over OData, however they’ll make it easier to to enhance the info refresh efficiency. So should you take all of the actions defined on this put up and you continue to don’t get a suitable efficiency, then you definitely may want to consider the alternate options and transfer your information right into a central repository.

In case you are getting information from a D365 information supply, you might wish to have a look at some alternate options to OData connection equivalent to Dataverse (SQL Endpoint), D365 Dataverse (Legacy) or Widespread Knowledge Providers (CDS). However remember, even these connectors have some limitations and may not provide you with a suitable information refresh efficiency. As an example, Dataverse (SQL Endpoint) has 80MB desk measurement limitation. There could be another causes for not getting an excellent efficiency over these connections equivalent to having additional broad tables. Imagine me, I’ve seen some tables with greater than 800 columns.

Some solutions on this put up apply to different information sources and aren’t restricted to OData connections solely.

Suggestion 1: Measure the info supply measurement

It’s at all times good to have an thought of the dimensions of the info supply we’re coping with and OData connection isn’t any completely different. Actually, the backend tables on OData sources could be wast. I wrote a weblog put up round that earlier than, so I counsel you utilize the customized perform I wrote to know the dimensions of the info supply. In case your information supply is giant, then the question in that put up takes a very long time to get the outcomes, however you possibly can filter the tables to get the outcomes faster.

Suggestion 2: Keep away from getting throttled

As talked about earlier, many options have some throttling mechanisms to regulate the over-utilisation of sources. Sending many API requests could set off throttling which limits our entry to the info for a brief time frame. Throughout that interval, our calls are redirected to a unique URL.

Tip 1: Disabling Parallel Loading of Tables

One of many many causes that Energy BI requests many API calls is loading the info into a number of tables in Parallel. We are able to disable this setting from Energy BI Desktop by following these steps:

  1. Click on the File menu
  2. Click on Choices and settings
  3. Click on Choices
  4. Click on the Knowledge Load tab from the CURREN FILE part
  5. Untick the Allow parallel loading of tables possibility
Disabling Parallel Loading of Tables in Power BI
Disabling Parallel Loading of Tables in Energy BI Desktop

With this selection disabled, the tables will get refreshed sequentially, which considerably decreases the variety of calls, due to this fact, we don’t get throttled prematurely.

Tip 2: Avoiding A number of Calls in Energy Question

Another excuse (of many) that the OData calls in Energy BI get throttled is that Energy Question calls the identical API a number of occasions. There are numerous identified causes that Energy Question runs a question a number of occasions equivalent to checking for information privateness or the best way that the connector is constructed or having referencing queries. Here’s a complete listing of causes for working queries a number of occasions and the methods to keep away from them.

Tip 3: Delaying OData Calls

In case you have accomplished all of the above and you continue to get throttled, then it’s a good suggestion to assessment your queries in Energy Question and look to see you probably have used any customized features. Particularly, if the customized perform appends information, then it’s extremely probably that invoking perform is the wrongdoer. The wonderful Chris Webb explains tips on how to use the Operate.InvokeAfter() perform on his weblog put up right here.

Suggestion 3: Take into account Querying OData As a substitute of Loading the Total Desk

This is likely one of the finest methods to optimise information load efficiency over OData connections in Energy BI. As talked about earlier, some backend tables uncovered by way of OData are fairly broad with lots of (if not hundreds) of columns. A typical mistake many people make is that we merely use the OData connector and get all the desk and suppose that we’ll take away all of the pointless columns later. If the underlying desk is giant then we’re in bother. Fortunately, we are able to use OData queries within the OData connector in Energy BI. You’ll be able to study extra about OData Querying Choices right here.

In case you are coming from an SQL background, then you might love this one as a lot I do.

Let’s take a look on the OData question choices with an instance. I’m utilizing the official check information from the OData web site.

  1. I initially load the OData URL within the Energy Question Editor from Energy BI Desktop utilizing the OData connector
Using OData connector in Power BI Desktop
Utilizing OData connector in Energy BI Desktop
  1. Choose the tables, keep in mind we are going to change the Supply of every desk later
Selecting the tables from an OData connection
Choosing the tables from an OData connection


That is what many people usually do. We hook up with the supply and get all tables. Hopefully we get solely the required ones. However, the entire objective of this put up just isn’t to take action. Within the subsequent few steps, we alter the Supply step.

  1. Within the Energy Question Editor, choose the specified question from the Queries pane, I chosen the PersonDetails desk
  2. Click on the Superior Editor button
Advanced Editor in the Power Query Editor
Superior Editor within the Energy Question Editor
  1. Exchange the OData URL with an OData question
Querying OData in Power Query in Power BI
Querying OData in Energy Question in Energy BI
  1. Click on Executed

As you possibly can see, we are able to choose solely the required columns from the desk. Listed here are the outcomes of working the previous question:

Querying OData in Power Query
Getting information utilizing OData question

In real-wrold eventualities, as you possibly can think about, the efficiency of working a question over an OData connection can be a lot better than getting all columns from the identical connection after which eradicating undesirable ones.

The probabilities are countless with regards to querying an information supply and OData querying in no completely different. As an example, let’s say we require to analyse the info for folks older than 24. So we are able to slender down the variety of rows by including a filter to the question. Listed here are the outcomes:

Using OData query filter
Utilizing OData question filter

Some Further Sources to Be taught Extra

Listed here are some invaluable sources in your reference:

Whereas I used to be in search of the sources I discovered the next wonderful weblogs. There are excellent reads:

As at all times, I might be joyful to learn about your opinion and expertise, so depart your feedback beneath.

Have enjoyable!



Please enter your comment!
Please enter your name here

Most Popular

Recent Comments