Forum Discussion
QUESTION::PIPELINE::COPY DATA::MAPPING::DATETIMEOFFSET FORMAT
Thanks for reporting this. The product team has decided that this behavior is a bug, and Copy Data task should not be modifying datetime/datetime2 values. This behavior will be changed in a future release of the On Prem Data Gateway.
Last OPDG release was a week ago, so a week after You found this bug. But still no solution for this? In my case, all dates and times are in UTC and time zone is +2, so i get all results with -2 hours. Date fields with T00:00:00 are converted to -1 day T22:00:00....
Same here. But I discovered this bug before last week and notified Microsoft, who didn't seem to be aware. But to make matters worse, it's not just that all timestamps are converted to UTC, half of them are converted to the wrong UTC, so even using a view on the source to shift the timestamps won't work because the conversion, at this point in time when DST is off, will convert all timestamps to UTC with DST off, meaning also those timestamps that should be converted with DST on, ie Winter timestamps.
I have a support ticket open already for the past 2 weeks and waiting on a resolution. Further response on the forum from Microsoft can be found here:
Re: QUESTION::COPY DATA::TIMEZONE ISSUE - Microsoft Fabric Community
I got a reply from support, created ticked, that this bug fix should be deployed by the end of this month. Hoping that will solve...
