Microsoft Dynamics 365 | Integration, Dataverse...

BC-CE Integration Date time Issue

(3) Share

Report

Posted on by CU05060412-0

The document date on CE side is 28/10/2024, but once posted to BC it's showing 29/10/2024.
When it's comes to BC side making 23:00 on 28th turn into 00:00 on the 29th.

(this seems to be a problem when Actuals in CE are timestamped with 23:00 rather than 00:00.)

(my concern is when we move from BST to GMT in October)

Can i get a solution for this?

Is this exactly in BC side or CE side?

How can find out, Which side we have to fix?

Thanks.

Categories:

Dynamics 365 general

Power Platform integration

Screenshot 2025-0...

I have the same question (0)

All responses (2)

Answers (0)

Suggested answer

DAnny3211 11,397 on at

Like (0)

Report
Hi there 👋

Thanks for your question!

The issue you're describing—where a document dated 28/10/2024 in CE appears as 29/10/2024 in BC—is likely related to time zone conversion during data synchronization between Dataverse (CE) and Business Central (BC).

✅ Here’s what to check:

Time Zone Settings in CE and BC

Confirm the time zone settings in both environments. CE might be storing timestamps in UTC, while BC could be converting them based on local time (e.g., GMT/BST).

Integration Mapping

Review the integration logic or Power Platform Dataflows. If the timestamp is 23:00 UTC, and BC interprets it as 00:00 in local time, it will shift the date to the next day.

Daylight Saving Time (DST)

Since you're moving from BST to GMT in October, this shift can cause unexpected date changes if not handled correctly. Ensure your integration accounts for DST transitions.

✅ How to identify the source:

Log the raw timestamp values in both CE and BC before and after sync.

Compare how each system interprets the same UTC value.

If CE stores the correct date but BC shifts it, the fix likely needs to be applied on the BC side or in the integration layer.

💡 Possible Fixes:

Normalize timestamps to UTC before syncing.

Apply time zone conversion explicitly in your integration logic.

Use a custom field to store local date if needed.

Hope this helps!
✅ Please mark this reply as helpful if it answered your question.
Best regards! 👋

this post was generated with Copilot

Was this reply helpful? Yes No
Scott_itD Community Manager on at

Like (0)

Report

Thanks for posting @DAnny3211, we appreciate your desire to help the Community!

~~I think your reply might be an AI-assisted post, but I do not see any tools or sources cited. Can you update the post to include your sources, or confirm this was not produced using AI?~~

~~Please refer to the Use AI responsibly section of Writing effective responses in the community~~

Thank you for updating your post to show it was generated by Copilot.

Was this reply helpful? Yes No