topic Re: Read data from Dataverse table via Fabric Dataflow gen 2 in Dataflow

Read data from Dataverse table via Fabric Dataflow gen 2

NandanHegde — Thu, 15 Feb 2024 05:02:59 GMT

Hello All,

Good day!

I am trying to read data from dataverse tables through Farbic dataflow :

https://learn.microsoft.com/en-us/fabric/data-factory/connector-dataverse

But getting timeout error :

So how to check the logs on dataverse side and whether the timeout is on dataverse side or dataflow capacity issue and what actions should be taken?

Re: Read data from Dataverse table via Fabric Dataflow gen 2

Anonymous — Thu, 15 Feb 2024 05:10:51 GMT

Hi NandanHegde
Thanks for using Fabric Community.
Can you please copy and paste the entire error message here?
Thanks

Re: Read data from Dataverse table via Fabric Dataflow gen 2

NandanHegde — Thu, 15 Feb 2024 05:12:59 GMT

Error Msg :
Error Code: 104100, Error Details: Couldn't refresh the entity because of an issue with the mashup document MashupException.Error: DataSource.Error: Failed to insert a table., InnerException: #{0}: #{1}, Underlying error: Microsoft SQL: The timeout period elapsed prior to completion of the operation or the server is not responding. RequestId: TDS;7ef36592-e05d-4fa4-aba4-2867211f2ce5;17 Time: 2024-02-14T10:42:17.9260565Z Details: Reason = DataSource.Error;Message = Microsoft SQL: The timeout period elapsed prior to completion of the operation or the server is not responding. RequestId: TDS;7ef36592-e05d-4fa4-aba4-2867211f2ce5;17 Time: 2024-02-14T10:42:17.9260565Z;Detail = [DataSourceKind = "CommonDataService", DataSourcePath = "avanadeuat.crm.dynamics.com", Message = "The timeout period elapsed prior to completion of the operation or the server is not responding.#(lf)RequestId: TDS;7ef36592-e05d-4fa4-aba4-2867211f2ce5;17#(lf)Time: 2024-02-14T10:42:17.9260565Z", ErrorCode = -2146232060, Number = 40001, Class = 16, State = 1];Message.Format = #{0}: #{1};Message.Parameters = {"Microsoft SQL", "The timeout period elapsed prior to completion of the operation or the server is not responding.#(lf)RequestId: TDS;7ef36592-e05d-4fa4-aba4-2867211f2ce5;17#(lf)Time: 2024-02-14T10:42:17.9260565Z"};Microsoft.Data.Mashup.Error.Context = User (Request ID: c45326c6-6658-41a0-ba0d-1adf5c1d1648).

Re: Read data from Dataverse table via Fabric Dataflow gen 2

Anonymous — Thu, 15 Feb 2024 10:48:25 GMT

Hi NandanHegde
Can you please try to disable the staging of power query? This might solve the issue.

If you are still facing the issue please do let me know.
Thanks.

Re: Read data from Dataverse table via Fabric Dataflow gen 2

NandanHegde — Thu, 15 Feb 2024 13:33:02 GMT

Did that but still getting the error but now the error message is not present :

Re: Read data from Dataverse table via Fabric Dataflow gen 2

Anonymous — Thu, 15 Feb 2024 15:51:57 GMT

Hi NandanHegde
Apologies for the issue you have been facing. This might be an intermittent issue. So I request you to kindly wait for sometime and try again.

If the issue still persists, please reach out to our support team so they can do a more thorough investigation on why this is happening.

Please go ahead and raise a support ticket to reach our support team:

https://support.fabric.microsoft.com/support

After creating a Support ticket please provide the ticket number as it would help us to track for more information.

Thank you.

Re: Read data from Dataverse table via Fabric Dataflow gen 2

pqian_MSFT — Thu, 15 Feb 2024 19:32:59 GMT

BTW, this is clickable to drill into details

Re: Read data from Dataverse table via Fabric Dataflow gen 2

pqian_MSFT — Thu, 15 Feb 2024 19:44:17 GMT

Looks like this is the same issue as

Gen2 Dataflow load to Lakehouse error - Can't inse... - Microsoft Fabric Community

Exception:

ExceptionType: Microsoft.Mashup.Engine1.Runtime.ValueException, Microsoft.MashupEngine, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35

Message: We can't insert null data into a non-nullable column."

i.e., your source\destination target has nulls but the columns are non-nullable.

You can mark your source table's columns to nullable to fix this for now. We are working on several changes here that will address the issue - such as defaulting to nullable, and surfacing nullability better in the mapping screen.