Forum Discussion
Data Pipeline COPY activity datetime mapping to timestamp
I have a COPY activity in my Pipeline that ingest data from SQL Server. I don't know why, but my datetime type filed is being converted to timestamp subtracting an offset with no reason.
1. Source connection and preview data:
2. Destination table in Lakehouse:
3. Mapping for fields:
4. Run pipeline and check lakehouse final table:
As you can see, comparing step 1 preview data and step 4 lakehouse data, final table StartTimeLocal field has subtracted an offset that is not stored in source filed. Source field is of type datetime, is not datetimeoffset. Why is Fabric applying the offset?
10 Replies
Hello amaaiia ,
Thanks for the using Fabric Community.
At this time, we are reaching out to the internal team to get some help on this .
We will update you once we hear back from them.I've already tried this. But I think this conversion types is for when you have incoming string fields and have to be converted to datetime or datetmeoffset. In my case, my fiels are all datetime or datetimeoffset in source, so I'm not sure if this is usefull for me.
My main problem is how tell COPY activity not to parse datetime or datetimeoffset to UTC by default,
