Forum Discussion
Dataflow operation is timed out
Hi Community!
We are trying to import all our dimensions and fact tables into dataflow. We have managed to import all except one. The fact table contains around 2.5 mill. rows and we have Pro licenses to Power BI.
The operation keeps timing out and give us these error details:
Request ID: 6f4b36e8-fe64-44e4-b8ee-0ba53ed90913
We have looked through the forum and also tried to turn on HTTPS in the data gateway, but that did not work either. The operation still times out.
Not sure if this have something to do with a size limitation or what? However, we have imported an almost identical fact table without problems. The goal is to append the two fact tables when they have both been imported correctly.
Hope you can help us!
BR
- Anonymous6 years ago
Hi Maggie,
It seems our SQL statement needs to be rewritten, so the problem is not solved yet, however it has been postpone to an unknown date. I will close the case for now.
3 Replies
- v-juanli-msft
Community Support
Hi Anonymous
Which is the data source?
SQL SERVER database?
After others are imported correctly, you could save the dataflow, open Power query online for the imported tables,
you could get data in the dataflow authoring tool.
https://docs.microsoft.com/en-us/power-bi/service-dataflows-data-sources
I find a workaround in this similar thread.
I created the desired query in PowerBI Desktop. Then I captured the M code from the advanced editor and pasted it into the editor in Dataflows. Then I just clicked 'Close and Save' and navigated away without waiting for the preview to finish.
The dataflow loaded without problem, but managing the query has to be done out of Power Query Editor, and then copied into the editor in the Dataflows interface.
Best Regards
MaggieCommunity Support Team _ Maggie Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly. - v-juanli-msft
Community Support
Hi
Is this problem sloved?If it is sloved, could you kindly accept it as a solution to close this case?If not, please let me know.Best RegardsMaggie- AnonymousNot applicable
Hi Maggie,
It seems our SQL statement needs to be rewritten, so the problem is not solved yet, however it has been postpone to an unknown date. I will close the case for now.