Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
Hi everyone,
I'm coming across a rather frustrating issue. My report refreshes keep getting timed out on one table, the sales quotes. There hasn't been a giant increase on quotes that could cause the size of this table to be too large. Nor have we changed anything to the connecting webservice. So I don't really understand why this table suddenly is starting to time out.
See error below:
Data source error: DataSource.Error: Dynamics365BusinessCentral: Request failed: The operation has timed out. Microsoft.Data.Mashup.ErrorCode = 10122. DataSourceKind = Dynamics365BusinessCentral. DataSourcePath = Dynamics365BusinessCentral. ;Dynamics365BusinessCentral: Request failed: The operation has timed out. The exception was raised by the IDataReader interface.
Every dataset refresh via the service there is a small shot that it would succeed. And even if it succeeds, it's only after 2-4 tries of approx 1h. Occasionally it works on the first try. The dataset is trying to connect to Business Central in the cloud. This issue happens for multiple different reports all running for the same company within Business Central. The reports also all run at different timings to keep the workload lower. But also when trying to refresh on the desktop version it would fail with a timout. I already tried clearing cache in PBI desktop.
I had issues with refreshing the dataset before, that issue was noted and solved in this thread. That's also how my connection string is now built up Dynamics365BusinessCentral.ApiContentsWithOptions(null, null, null, [UseReadOnlyReplica = null]). I have tried setting it back to a null but the timeout keeps appearing. Both on desktop and service.
Solved! Go to Solution.
Hi @KatrienVds ,
Just wanted to check in to see if your query has been resolved and whether the steps suggested by @Akash_Varuna were helpful. If they were, kindly consider marking the helpful reply as 'Accepted Solution' to assist others with similar queries.
If you've raised a support ticket and received assistance, please feel free to share your experience here to help the community.
Otherwise, don't hesitate to reach out if you need further assistance.
Thank you.
Hi @KatrienVds ,
We’re following up once more regarding your query. Could you please confirm if the issue has been resolved? If you raised a support ticket, we’d appreciate it if you could share any updates or insights from the support team.
If the issue has been resolved, we kindly request you to share the resolution or key details here to help others in the community.
For any future questions or assistance, feel free to create a new thread in the Microsoft Fabric Community Forum - we’ll be happy to help.
We may consider closing this thread if there is no response.
Thank you for being part of the Microsoft Fabric Community.
I have indeed raised a support ticket as there seemed no end to the recurring issue.
They made some adjustments in the back.
However the topic is not fully closed... as the issue persists.
From time to time the reports still crash with the same error.
I've found out that when it crashes it feels like there is a time out happening in the back.
So far we were unable to define why this happens.
Hi @KatrienVds ,
Just wanted to check in to see if your query has been resolved and whether the steps suggested by @Akash_Varuna were helpful. If they were, kindly consider marking the helpful reply as 'Accepted Solution' to assist others with similar queries.
If you've raised a support ticket and received assistance, please feel free to share your experience here to help the community.
Otherwise, don't hesitate to reach out if you need further assistance.
Thank you.
Hi @KatrienVds The timeout issue likely stems from large data loads or delays in the Business Central cloud API.
Could you try these please
Use OData filters like $top, $filter to limit data pulled.
Split queries into raw data + transformation steps.
Set UseReadOnlyReplica = true in your connection string.
If possible try enabling incrimental refresh
Disable background data previews in Power BI Desktop.
If nothing works then raise a Microsoft support ticket
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
| User | Count |
|---|---|
| 55 | |
| 50 | |
| 43 | |
| 16 | |
| 15 |