General point of attention 2 is configuring the time-out in Azure Data Factory / Microsoft Fabric.
Some examples:
itgenboe312
The data download was cancelled after 10 minutes, 1 second, for example because Azure Data Factory terminated the download prematurely due to a time-out configured in Azure Data Factory.
Optimise your query as described at Overzicht van Power BI-technieken om prestaties en downloadtijd te verbeteren - invantive. Then run the query again.
URL: ExactOnlineREST.CRM.AddressesBulk@eol?$filter = Modified ge 2026-05-01T16:00:30.3259182Z
In 2022, Exact decided to no longer allow a filter on Modified on the underlying bulk API Addresses, in order to encourage users to make use of the *Incremental APIs.
See also, for example:
- Exact Online Bulk endpoints (server-side filtering)
- Mandatory filtering on single and bulk endpoints where sync APIs are available
Given the short time frame, using ExactOnlineREST..Addresses is likely to be many times faster, since a server-side filter is possible there on Modified, despite the roughly 12x slower download speed.
This can be verified using:
select *
from AddressesBulk@eol
where Modified >= sysdateutc - 1/24
select url
from SessionIOs@DataDictionary
where call_safe_name = 'ExactOnlineREST.CRM.AddressesBulk'
order
by id desc
select *
from Addresses@eol
where Modified >= sysdateutc - 1/24
select url
from SessionIOs@DataDictionary
where call_safe_name = 'ExactOnlineREST.CRM.Addresses'
order
by id desc
This can also be determined in advance with this query:
select table_name
, name
, can_filter_server_side
, influences_insert
from SystemTableColumns@DataDictionary
where name = 'Modified'
and table_name in ('Addresses', 'AddressesBulk')
and table_catalog_name = 'ExactOnlineREST'
The results with and without server-side filtering are identical; only the number of API calls can vary considerably.