‘Timeout Expired’ Issue in Power BI When Publishing Reports with Dataverse

[homarmp]

Hello everyone, I hope you can help me with an issue I’m facing in Power BI.

I’m experiencing a ‘Timeout Expired’ issue in Power BI when publishing reports with Dataverse as the data source. I managed to temporarily solve it by using Measure Killer to remove unused columns and by configuring incremental refresh in my fact tables. However, after modifying a chart and publishing the report to Power BI Service, the ‘Timeout Expired’ error reappeared.

Currently, I have around 500,000 records in Dataverse and I’m using a premium workspace that, as far as I know, allows up to 5 hours of processing time, but my model already exceeds this limit.

Has anyone managed to publish in Power BI Service without performing a complete read of the data source, perhaps by segmenting it with filters? Or do you have any tips to solve this problem?

I appreciate any help or advice you can offer. Thank you!

[v-fenling-msft]

Hi, @homarmp 

May I ask if you have gotten this issue resolved? If it is solved, please share your solution and accept it as solution, it will be helpful for other members of the community who have similar problems as yours to solve it faster.

If it hasn't been resolved yet, please share more details about the issue you're having and we'll do our best to help you solve the problem you're having.

I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.
Best Regards,
Fen Ling,
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[GilbertQ]

Hi @homarmp 

You can sometimes get a timeout also from the source for your querying from, which is how this appears to be in this case while. I would recommend doing is to create the incremental refresh and then processing the partitions in batches of say one week at a time in order to get the data in in a batch kind of process.