Hello,
I have a standard data entity, Employee, and I use DMF to import data for insert/update operations in AX. In the imported CSV, I have datetime fields that correspond to ValidFrom and ValidTo in the Employment table in AX 2012.
For some reason, the import treats those values as UTC instead of using the imported user’s time zone. As a result, during updates it cannot correctly determine whether a record for the given time range already exists. Instead of finding a matching record, it treats the records as overlapping and raises an error.
Additionally, in the debugger I can see that, during staging-to-target processing, the system applies the time offset one more time.
Is this a common bug? Or is there some setup/configuration that I might be missing?
Thanks a lot for your help!
Hi @Jina_K
This is a known time zone issue in DMF. The system treats imported datetimes as UTC by default, then applies conversion again during staging-to-target, causing the double offset you’re seeing.
Best fix: Pre-convert your ValidFrom/ValidTo values to UTC in your CSV before importing. This eliminates the ambiguity.
Alternative: Check your data entity configuration for any custom datetime transforms or timezone adjustment rules that might be conflicting with DMF’s default behavior.
The staging table values are worth checking too, if they’re already wrong there, the issue is in the import step itself.
Hope this helps!
Hi Jina,
This is the standard behaviour . By default, the system takes UTC.
Can you try changing the session time and import? If this doesn`t work, some customisation is needed.