What is an OData feed and why is it useful?

OData in short

OData stands for Open Data Protocol. It is a standard way to make data available via the internet. Compare it to a website, but for data instead of pages. An OData feed provides structured data (tables with rows and columns) that you can request via a URL.

The protocol was originally developed by Microsoft and has been established as an open standard. Power BI and Excel can read OData feeds via Power Query. The query options, authentication methods, and relationships available vary by OData service.

How does an OData feed work?

An OData feed has a URL, just like a website. If you open that URL in a browser, you will see the available tables (entities). Each table has its own URL where you can request the data.

In Power BI, go to 'Get data', choose 'OData feed' and paste the URL. Power BI will then show you the available tables and you select which ones you want to load. You can filter, sort and create relationships, just like with any other data source in Power BI.

The connection starts with a service root URL and a supported authentication method. You don't need to install a database driver, but you do need to manage source credentials in Power BI Desktop and after publishing in Power BI Service.

What do you need?

For Power BI you need the OData service root, the correct login details and Power BI Desktop. In Get Data, choose OData Feed, enter the service root, and select the desired tables in the Navigator. Start without manually adding query options; Then add filters and column selections in Power Query so it's clear what transformations the report performs.

OData vs. other methods

CSV exports

CSV files are snapshots and must be recreated for a new mode. With OData, Power BI can reload the currently available source data during a refresh. With DigiData, this is the last completed synchronization, so the timing of source and Power BI refresh remains important.

Direct API links

APIs require source-specific documentation for authentication, pagination, and data transformation. OData standardizes the service root, metadata, and query options, but a service may support only some of those options and may use its own authentication method.

Database connections

Connecting directly to a database usually requires network access, credentials and knowledge of the database. An OData feed uses HTTP(S), but remains reachable only to clients that have network access and valid source credentials.

Why DigiData uses OData

DigiData synchronizes data from your business software and makes it available as an OData feed. We do this consciously: OData is the best supported standard in Power BI and Excel. You don't have to install extra software, download plugins or write scripts.

Each integration in DigiData (Exact Online, Twinfield, Bouw7, etc.) provides its own set of OData tables. In Power BI you can combine tables from different integrations via relationships, so you get a complete picture of your company. Read more about connecting Twinfield to Power BI or view all Power BI connections.

What does an OData feed look like in Power BI?

In Power BI, choose OData feed and paste the URL. Then Power BI shows the available tables. For example, you select customers, invoices, transaction lines, projects or hours. Power Query retrieves the chosen tables and lets you filter columns, set data types and prepare relationships.

The main difference with a CSV is that the feed can be reloaded. You don't have to download the same file every month. Power BI uses the same source URL and can refresh the dataset on schedule.

For larger models it is wise to load only the tables you need. Start with the core: invoices, transactions, customers, projects or hours. Then add dimensions such as periods, general ledger accounts, employees or locations.

OData in Excel and Power Query

OData isn't just for Power BI. Excel uses the same Power Query technique. This allows you to first check a dataset in Excel and later model it in Power BI. This is useful for finance teams, because checks often start in Excel.

For example, a controller can load debtors or general ledger transactions into Excel, apply filters and compare totals with the source. The BI maker uses the same feed for dashboards. This way, both roles work with the same source data instead of different exports.

Security and management

An OData feed must be well secured. DigiData uses authorized access to the feed, so that not everyone can simply retrieve company data. Therefore, only share feed URLs and tokens with people who are allowed to use the data.

Management is at least as important as technology. Document which tables are used, who owns the report and how often refresh is needed. Without those agreements, even a good feed can still lead to confusion.

When is OData not enough?

OData is strong for structured tables and recurring reports. It is less suitable for very specific calculations that have to be done per organization in custom code. In that case, you can still use OData as a source, but the calculation will then belong in Power BI, a data model or a separate data layer.

CSV can also be faster for a one-off check. So it is not about OData versus CSV as the winner, but about whether your reporting is recurring. When the same tables are needed more often and the service supports the required filters, OData is often a more practical basis.

Filters, refresh and large data sets

With larger datasets it is wise to load consciously. Power BI can filter OData tables in Power Query, but your model will remain faster if you only use the tables and columns that are necessary. So don't start with all available data; start with the reporting question.

Also think about refreshing. A daily management dashboard often does not need to be refreshed every fifteen minutes. An operational dashboard may need up-to-date data more often. Adjust the refresh in Power BI to the synchronization of DigiData, so that you do not run unnecessary refreshes on data that has not yet been updated.

For historical tables, incremental refresh can be useful when your Power BI model becomes large. First check that date filters are being passed to the OData source; without query folding, Power BI can still retrieve a lot of data before the filter is applied.

Troubleshooting

If an OData feed works in Desktop but not in Power BI Service, check the source references in the Service and use the service root first. Microsoft describes that the connection test can ignore query options in a manually constructed OData URL. Move such filters to Power Query and only use the option to skip the connection test when intentionally set for this resource.

If merges between tables are slow, first limit rows and columns. Microsoft mentions sidebars and, in case of stuck merges, buffering the smaller query as a possible approach. Test the effect: buffering is not a general speedup and can actually prevent filters from being forwarded to the source.

Common misunderstandings about OData

An OData feed is not a dashboard. It is the source layer from which your dashboard retrieves data. You still make the calculations, visuals and definitions in Power BI, Excel or another analysis tool. That distinction keeps your architecture clear.

OData is also not a substitute for data quality. If customer names, project numbers, or periods are inconsistent in the source, you still need to make those agreements. The feed makes data available; your organization determines what the data means.

Finally, OData is not just for large companies. SME teams in particular benefit from this because they require less manual work. A standard feed prevents someone from having to maintain API code, local drivers or separate exports every month.

Summary

OData is an open standard for querying structured data and is supported by Power Query. With the correct service root, source references and a refresh schedule, you can load the same DigiData tables into Power BI repeatedly. View all available integrations or contact us.