Copy data activity loses factorial seconds about azure-datafactory HOT 7 OPEN

Are you still experiencing this?

from azure-datafactory.

Close due to inactivity

from azure-datafactory.

I'm experiencing this very issue with my high water mark field but it's also impacting any other datetimeoffset fields in my copy activity and since I'm dynamically mapping my fields because I'm copying a large of number of tables from Odata to Azure SQL db, I can't explicitly format my output of every single field this is affecting. This is really poor in terms of accuracy of copy activity.

from azure-datafactory.

@lpmac , could you provide your copy activity run ID?

from azure-datafactory.

@fhljys f33c5464-84b2-45b6-a51a-ceb93a11b1b3
This is the pipeline run ID which does the copy activity

from azure-datafactory.

@lpmac , could you help identify which stage caused this issue? For example, you can check lookup output and set variable input/output? Or if possible, you could create a support ticket to Microsoft.

from azure-datafactory.

@fhljys
you can't use a lookup output of the copy activity as it does not give you the detail required to preview the level of precision the source data is pulling through for the datetimeoffset fields.

To clarify, I have a copy data activity with an Odata source and Azure SQL db sink and regardless of whether the data is explicitly mapped or dynamically mapped - the fields with datatype datetimeoffset are not being copied into the sink SQL db with the same level of precision as they are found when directly querying Odata from Postman.
Odata via Postman field:
2021-07-07 13:55:58.9100000 +01:00

Output of Copy activity field:
2021-07-07 13:55:58.0000000 +01:00

I have raised it here;
https://feedback.azure.com/forums/270578-data-factory/suggestions/43971279-copy-activity-to-preserve-precision-of-datetimeoff

from azure-datafactory.