Forum Discussion
Could not determine JSON object type for type Microsoft.DataTransfer.DataTypes.Date.
The values in the date column are just that: dates. Timestamps. Some kind of representation of a date. Whatever format is required, under the hood it should be nothing other than a timestamp. If it was a string column, I could understand the format argument. But the date column has no "format" other than what's displayed to the user. It has some date time information, timezone naive or timezone aware. How that date is made readable, should be irrelevant for the JSON conversion. I would expect the JSON conversion, which essentially converts the date time object into a string (yes), to use some universal or configurable format instead of just failing. I see no option to choose a format for the date to JSON conversion anywhere. It just fails. As a bare minimum/default/fallback format I would expect the datetime to be redered into an ISO string - instead of failing.
Hi Hendrik1980 ,
Just checking back to see if you have a resolution yet .
In case if you have any resolution please do share that same with the community as it can be helpful to others .
Otherwise, will respond back with the more details and we will try to help .
No. I have a workaround: converting the column to string in the Data Flow.
However, I do not want that workaround. I expect the involved components (Lakehouse table, Copy Data node) to work together regardless of the data type. I expect the Copy Data node to be able to convert whatever Fabric data source is used to whatever Copy Data target is used. It's both integrated and core functionality of Fabric. Converting a date field from a Lakehouse table into a JSON field (string, essentially) should be no rocket science (if in doubt about the target format, either use ISO date per default or offer a way to configure a desired format). I expect the Copy Data node to be able to do that as it converts any other data type.
I see the error as a bug and would like to report it as that.
Hi Hendrik1980 ,
The best course of action is to open a support ticket and have our support team take a closer look at it.
Please reach out to our support team so they can do a more thorough investigation on why this it is happening: Link
After creating a Support ticket please provide the ticket number as it would help us to track for more information.
Hope this helps. Please let us know if you have any other queries.
Will do. Thank you for the link.
Hello Hendrik1980 ,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet .
In case if you have any resolution please do share that same with the community as it can be helpful to others .
If you have any question relating to the current thread, please do let us know and we will try out best to help you.
In case if you have any other question on a different issue, we request you to open a new thread .
Thanks