topic Re: Expression.Error: We can't convert values of this type to JSON. in Dataflow

Expression.Error: We can't convert values of this type to JSON.

Anonymous — Tue, 15 Aug 2023 14:49:36 GMT

Hi Guys,

I have a dataflow that I want to use to create another dataflow but I keep getting this error when I try to load the dataflow.

The MashUp Script:

---------- Message ----------
Expression.Error: We can't convert values of this type to JSON.

---------- Session ID ----------
a7a0579a-ca7c-4ed9-af09-4744c245ddc3

---------- Request ID ----------
35502f83-504f-452a-b21a-edd3d51739a1

---------- Mashup script ----------
[DefaultOutputDestination = "DefaultDestination"]
section Section1;
shared DefaultDestination = Lakehouse.Contents(null){[workspaceId = "97dfcda7-7f2c-4e30-a6c2-27e351e329d2"]}[Data]{[lakehouseId = "f4eaf6ce-7322-42b8-a220-e5d3e7b816be"]}[Data];
[BindToDefaultOutputDestination = true]
shared Query = let
Source = PowerPlatform.Dataflows([])
in
Source;

Re: Expression.Error: We can't convert values of this type to JSON.

miguel — Tue, 15 Aug 2023 16:16:06 GMT

If it only happens with that single entity, it could be a corrupted entity or somethign that happened with that specific entity.

If it happens to every single entity that you're trying to connect to, then it might be a bigger issue.

Regardless, I'd recommend reaching out to the support team by raising a support ticket using the link below:

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

Re: Expression.Error: We can't convert values of this type to JSON.

ELANG — Thu, 17 Aug 2023 16:16:35 GMT

Getting the same issue in my workspace.... was there every a solution found?

Re: Expression.Error: We can't convert values of this type to JSON.

r_mel — Thu, 17 Aug 2023 17:59:36 GMT

I am experiencing the same error and submitted a support ticket. If anyone has insight, that would be great!

Re: Expression.Error: We can't convert values of this type to JSON.

r_mel — Mon, 21 Aug 2023 14:24:27 GMT

For anyone following this thread, it seems as though connecting to a dataflow only works if the destination dataflow is not a Gen2 dataflow.

From what I last heard from support, the internal team is trying to find a fix for this issue.