The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hi,
i cant solve time zone issues, maybe on prem gateway should have some settings or what i should do?
1. Data source is On Prem SQL, all date/time fields are stored in UTC time;
2. Our local time zone is +2;
3. Using copy activity to Lakehouse, all date/time fields are saved these -2 hours. Example, if it is only date (2024-05-22T00:00:00), then in Lakehouse table i have 2024-05-21T:22:00:00, and everything with time is just -2hours back... Until now i was using dataflows gen2, this issue was not ocurring...
Hello any fix for this issue? i am having the issue when copying from an oracle DB to lakehouse. The oracle DB has an America/New York TimeZone, and after copying the timezone is converted to UTC.
When is this issue going to be resolved? I am also seeing simillar issue.