Timeout issue on dataverse side

[Anonymous]

Hi, 

I am getting the below error while attempting to import a +-100k record  microsoft dataverse table, both using the SQL Server connector and the Microsoft Dataverse connector. I tested, e.g. a 500record table on microsoft dataverse will get imported. 

Microsoft SQL: The request channel timed out while waiting for a reply after 00:02:00. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. 

How would I increase the timeout value? Probably needs to be done on platform side.. I already increased the CommandTimeout and ConnectionTimeout to 10 minutes in the Sql.Database function, but the timeout is still capped at 2 minutes. 

With kind regards, 

LG 

[mhammo]

I have barely over 5,000 opportunity records and getting this error using the Dataverse connector. 

This problem needs fixed ASAP.

[Anonymous]

Hi, rather than using the ODATA - you can still use "Common Data Service (Legacy)" and that does not time out.

[Anonymous]

@Anonymous  Thanks for your reply. 

I had already increased this setting to 10 minutes. 

I sitll get the 00:02:00 timeout error while "waiting on orgXX.crm4.dynamics.com/database" : 

[MichaelP2020]

Hi lgpower

Did you manage to find a resolution to this? Experiencing the same issue but trying to establish if the timeout can be increased from the Dataverse Setup (Power Platform Admin Centre).

[Anonymous]

I tried the same without success. Please let me know if you find the magical setting :). 

I ended up using the dataverse odata endpoint . I guess it is less performant but I am able to retrieve +100k records. 

Good luck! 

LG 

[Anonymous]

@Anonymous 

For SQL database, we can also change the command timeout in Advanced options.

Paul Zheng _ Community Support Team
If this post helps, please Accept it as the solution to help the other members find it more quickly.