
Has anyone experience the following:
We are exporting data from D365FO to Azure SQL DB using standard data management framework routine.
When data is inserted into BYOD table, datetime value is saved 5 hours ahead. I ran some tests from a OneBox environment to several Azure SQL db created in different locations (US, Europe, Asia) and couldn't replicate this scenario.
Maybe I'm missing some configuration either in D365FO or Azure SQL.
Any help is welcome.
Hi, Anderson
Which field and table you are referring here? In AOT, UTC time is one field with UTC type EDT, but in the AXDB, there are 2 fields (datetime and timezone). Please compare with AXDB and check if timezone field is missing in the BYOD.