Forum Discussion
Error message importing Data from Dataverse
I am attempting to import data from Dataverse and it keeps timing out. I know it is alot of data but how can I extend the time. See error message below.
Hi,
This timeout is typically not something that can be increased from within Power BI. It usually indicates that the Dataverse query is taking too long to complete or is returning a very large volume of data.
A few things you can try:
- Filter the data at the source in Power Query (for example, only import the required date range or active records) so less data is retrieved.
- Select only the columns you need instead of importing the entire table.
- If possible, enable Incremental Refresh so only new or changed data is refreshed after the initial load.
- Ensure the Dataverse table has appropriate indexes on the columns used for filtering.
- If you're connecting through TDS (SQL endpoint), consider using the Dataverse connector instead, as it's optimized for Dataverse workloads.
- For very large datasets, consider exporting the data to Azure Data Lake, Fabric Lakehouse, or Synapse and connect Power BI to that instead of querying Dataverse directly.
To better understand the cause, could you share:
- Approximately how many rows are in the Dataverse table?
- Are you using the Dataverse connector or connecting via the Dataverse TDS (SQL) endpoint?
- Does the timeout occur during the initial load or only during refresh?
That information will help determine the most appropriate solution.
Hope this helps.
Thanks!
3 Replies
Hello ljc2297,
I have run into this same kind of timeout before, and it's usually not the timeout setting that's actually the problem, it's more that the import's too big or the query just needs more time to finish running.
First thing I will check: roughly how many rows are you importing?
Are you loading the entire table, or can you filter it before importing?
If you don't need every column, remove the ones you don't need. That alone can make a noticeable difference.
Are there any lookup, calculated, or rollup columns in the table? I have seen those add quite a bit of overhead to the query.
One thing I will test is importing a smaller date range first. If that works, you'll know the overall data volume is probably the limiting factor.
The Dataverse connector in Power BI Desktop doesn't expose a configurable timeout setting. Microsoft's documentation notes that Dataverse queries have a fixed timeout, so I will focus on reducing the amount of data being returned or simplifying the query instead.
At what point does it fail? Is it during the preview in Power Query, or only when you apply the changes?
Docs: DataverseHi,
This timeout is typically not something that can be increased from within Power BI. It usually indicates that the Dataverse query is taking too long to complete or is returning a very large volume of data.
A few things you can try:
- Filter the data at the source in Power Query (for example, only import the required date range or active records) so less data is retrieved.
- Select only the columns you need instead of importing the entire table.
- If possible, enable Incremental Refresh so only new or changed data is refreshed after the initial load.
- Ensure the Dataverse table has appropriate indexes on the columns used for filtering.
- If you're connecting through TDS (SQL endpoint), consider using the Dataverse connector instead, as it's optimized for Dataverse workloads.
- For very large datasets, consider exporting the data to Azure Data Lake, Fabric Lakehouse, or Synapse and connect Power BI to that instead of querying Dataverse directly.
To better understand the cause, could you share:
- Approximately how many rows are in the Dataverse table?
- Are you using the Dataverse connector or connecting via the Dataverse TDS (SQL) endpoint?
- Does the timeout occur during the initial load or only during refresh?
That information will help determine the most appropriate solution.
Hope this helps.
Thanks!
Hi ljc2297,
Thank you for posting your query in the Microsoft Fabric Community Forum, and thanks to SamInogic & Olufemi7 for sharing valuable insights.
Could you please confirm if your query has been resolved by the provided solutions? This would be helpful for other members who may encounter similar issues.
Thank you for being part of the Microsoft Fabric Community.
