Forum Discussion
QUESTION::COPY DATA::TIMEZONE ISSUE
- 2 years ago
How can you say 'solved the issue'? ABSOLUTELY NOT! Because as long as the Copy data/data gateway changes the incoming timestamps to the wrong UTC offset to boot, it is not solved! 😠😠ðŸ˜
FYI Microsoft acknowledged this is a bug that will be fixed in a future update of the data gateway. That's what I have been told. So do not tell me that it is a solved issue when it is not. Further, we have been told the fix should be done by EOM.
Hi Element115
Thanks for the details. The above troubleshooting steps have solved the issue for the other customers. As you said the second one is a work around, but did solve the issue.
Thanks
How can you say 'solved the issue'? ABSOLUTELY NOT! Because as long as the Copy data/data gateway changes the incoming timestamps to the wrong UTC offset to boot, it is not solved! 😠😠ðŸ˜
FYI Microsoft acknowledged this is a bug that will be fixed in a future update of the data gateway. That's what I have been told. So do not tell me that it is a solved issue when it is not. Further, we have been told the fix should be done by EOM.
- Anonymous2 years agoNot applicable
I meant to say it resolved the issue temporarily Element115 .Glad that you got the details from our support team. Kindly update here if you have the details so that it will be helpful for other community members.
Thanks