Skip to main content

Notifications

Microsoft Dynamics 365 | Integration, Dataverse...
Unanswered

Dates mismatched between CE and FO

Posted on by 405
We are facing a weird issue with the dates in dual-write integration. We have custom date fields created on the sales line table in FO and mapped it with CE custom fields. It's simple DW mapping without any business logic around it.
We see a date mismatch for CE to FO flow. We observed this behavior mainly happening with the users in the Australian timezone, but I can not deny this is happening with the users in different time zones.
The timezone for the dualWrite user is set as GMT. 
I appreciate any help you can provide. 
 
CE Start date CE end dateFO StartFO End
6/26/20236/28/20232023-06-25 00:00:002023-06-27 00:00:00
8/7/20238/9/20232023-08-06 00:00:002023-08-08 00:00:00
8/7/20238/9/20232023-08-06 00:00:002023-08-08 00:00:00
8/21/20238/23/20232023-08-20 00:00:002023-08-22 00:00:00
12/4/202312/4/20232023-12-03 00:00:002023-12-03 00:00:00
  • Martin Dráb Profile Picture
    Martin Dráb 230,149 Most Valuable Professional on at
    Dates mismatched between CE and FO
    This is a lot of text without any actual information. It looks to me like text generated by AI just to promote the company mentioned in the text.
  • Dates mismatched between CE and FO

    Hey there!

     

    So, you've got a little problem with the dates in our CE to FO flow. It's not syncing up properly, especially for your users in the Australian timezone. But hey, your users in other timezones might be facing it too.

     

    To fix this date issue, here's what we need to do:

     

    First things first, let's double-check how we handle timezones in our mapping process. We want to make sure we've got the right timezones for CE and FO flows without any mix-ups or conversion errors.

     

    Next, we gotta settle on a single date format for both CE and FO. It'll make things less confusing and reduce the chance of making mistakes during conversion. Choose a format that works for both systems and keeps the mapping accurate.

     

    If our CE and FO flows are in different timezones, we need to do some proper timezone conversion during data transfer. We can rely on a reliable method or library to handle this conversion accurately, so we don't end up with any more date mix-ups.

     

    Lastly, let's test the date mapping with users in different timezones. It's not just our Australian friends facing this issue, so we want to make sure our mapping works perfectly for everyone, no matter where they are. This may sound overwhelming but trust me it’s not coz this is what we do at Triotech Systems or any other client’s projects. 

     

    By following these steps, we'll fix the date mismatch problem and ensure our mapping process runs smoothly without any complicated business logic.

     

    Hang in there, you got this!

  • Martin Dráb Profile Picture
    Martin Dráb 230,149 Most Valuable Professional on at
    Dates mismatched between CE and FO
    When talking about the date in F&O, are they date or utcDateTime fields? If the latter, are you showing us at values in database (UTC) or what a user see in GUI (which depends on his/her timezone)?

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Community AMA December 12th

Join us as we continue to demystify the Dynamics 365 Contact Center

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,240 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,149 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Product updates

Dynamics 365 release plans