web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Service | Customer Service, Contact Center, Fie...
Answered

Change "created on date" in MS Dynamics online 2020

(0) ShareShare
ReportReport
Posted on by

Hello

I switched to dynamics for case management. I have a couple of cases which needed to be imported to dynamics. I did the report and everything went well, but the "created on date" could not be changed. 

I did some research with override contact created on, tried with xml tool but nothing really worked out. Thank you very much for your help. 

pastedimage1603794495665v1.png

I have the same question (0)
  • NicksTuk Profile Picture
    1,833 on at

    You have to map to the Record Created On (overridencreatedon) field DURING your data import to set the custom value for Created On.

    I'm not sure you can do anything to change that post-import.

  • Community Member Profile Picture
    on at

    Hello Nico,

    Thank you for your answer. I tried it with exporting and then I imported it back in matching created on date  => Record created on - but then it says "field can not be modified" :-(

    pastedimage1603811229386v1.png

    this is what I see during the import with the mapping table - but I can not map the created on with record created on. 

  • Verified answer
    NicksTuk Profile Picture
    1,833 on at

    That will not work for updates, only for creating new records through import. It is meant for bulk data loads where you need to keep that original created date as per the source system.

  • Community Member Profile Picture
    on at

    ah okay - how can I export this data and import it with the new date?

  • Suggested answer
    NicksTuk Profile Picture
    1,833 on at

    Well, that's a more complex question. It depends on how much work has happened on those records, how many related records (activities or other things like notes) have been created, etc.

    It might not be worth the effort, depending on how important is the creation date for that batch of records on reporting.

    You might choose to leave that batch as is, and map correctly going forward. Your reporting will show some weirdness for that batch, which you can communicate accordingly and adjust reporting for that period, taking into consideration the issue.

  • Community Member Profile Picture
    on at

    Hello Nico,

    thank you very much for your quick answer. It worked. I deleted the old cases import on the system and added the row "Record Created on" on the sheet and mapped the record created on to created on. So it worked well - I didn't know that it's not possible to update "the created on" field with the export and import function but now i know better  :-)

    Thank you very much

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Service | Customer Service, Contact Center, Field Service, Guides

#1
Tom_Gioielli Profile Picture

Tom_Gioielli 45 Super User 2025 Season 2

#2
Daniyal Khaleel Profile Picture

Daniyal Khaleel 27 Most Valuable Professional

#3
Soundari Profile Picture

Soundari 15

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans