OData API Timeout When Extracting Large Table via Invantive Bridge Online

[vh63]

I am writing to report a persistent issue I encountered while attempting to extract data from a customer’s Exact Online environment via the Invantive Bridge Online OData API.

Environment

• Endpoint: https://bridge-online.invantive.com/[company-instance]/odata4
• Table: ExactOnlineREST.FinancialTransaction.TransactionLines@eol
• Account type: Free tier
• Target: Microsoft Fabric Lakehouse

Issue Description

The TransactionLines table contains a large volume of data (approximately 54,000+ records per financial period). Every attempt to extract this data via the OData API resulted in a server-side timeout, regardless of the method used.

We tested the following approaches, all of which failed:

1. Direct OData query with $top parameter; the API hangs indefinitely for large $top values.
2. Filtering by FinancialYear and FinancialPeriod; the API times out even when filtering to a single month.
3. Pagination via $skip; not supported (error itgengcr008: “Skip is not supported on Invantive Bridge Online”)
4. Partitioning by date ranges; same timeout behavior
5. Microsoft Fabric native connectors (Pipeline Copy Data, Dataflow Gen2) — both fail with ODataRequestTimeout.

Small queries (e.g. $top=1 without filters) work correctly and return results in seconds. The issue only occurs when attempting to retrieve meaningful volumes of data.

Questions

1. Is this timeout behavior a known limitation of the free tier? Would upgrading to a paid plan resolve this issue by increasing the server-side query timeout?
2. Is there a recommended approach for extracting large tables like TransactionLines in bulk? Given that $skip is not supported, what is the intended pagination or extraction strategy?
3. Are there any server-side configuration options (e.g. query timeout, max rows per request) that could be adjusted to allow full extraction of this table?

Any guidance would be greatly appreciated. Please let me know if you need additional details or logs.

[forums]

Please use the *Incremental tables as described in more details here:

Faster Exact Online download using incremental "sync API"-tables

Go to Dutch version The Exact Online REST API provides so-called “sync APIs.” Sync APIs are new REST APIs that solve some of the disadvantages when using Exact Online webhooks for incremental replication. Exact Online’s sync APIs are a welcome improvement for environments based on Invantive Cloud or the Excel add-in Invantive Control: Easy to use: the sync APIs are easy to use and work right the first time. More reliable: the chain of dependencies is much shorter compared to webhooks. The fa…

Alternatively, please use TransactionLinesBulk when a specific range can be filtered upon. The *Incremental tables have different characteristics since they require an initial reconstruction phase.

Please find more tips on:

What are the critical points for implementing Power BI?

Go to Dutch version Users with a free consultancy subscription of Invantive for Invantive Cloud, Power BI and Exact Online often connect multiple customers. These often involve the same points of interest. This topic serves to give an overview of the points that can be checked during the implementation or upon delivery whether they have been included or left out. Choices Beforehand To improve the odds for a successful project it is necessary to make some choices in advance. Guidelines can be f…

Or consult the person that received the free training within your company.

Please note that the Free Exact Online Plan covers at most 100,000 rows per day retrieved fresh. With the indicated volume of 600K rows yearly created, the Free Exact Online Plan is unlikely to be a feasible option.

All plans have similar timeout statistics, but please read the article on the link with more tips on time-out extension.

When the free trial has ended as visible in the Agreements form, please reach out to the sales department for an upgrade of your plan.