Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Diffrence between "Created On" and "Record Created On"

In CRM, when I'm, trying to set up a work flow, I get to choose the timeout to be related to a certain entity's creation time. There are three fields to relate to.

  • Record Created On
  • Created On
  • Modified On

While the last one is very obvious, I can't see any logical difference between the two others.


1 Answers

The difference is that Created On (createdon) is filled out automatcally by the server when you actually create the record, while Record Created On (overriddencreatedon) will usually be null (unless the record was imported into CRM and you chose to explicitly override the record creation date to match when it was created in another system).

You should use the first and skip the latter, as it's not supported (as far I've got it right when I talked to a MVP about it). Why it show, she had no idea and neither do I. Maybe @JamesWood has a shot. He usually does. (sucking-up in progress)

I've never used the latter and I believe you'll keep your hair off-grey and on-head if you stick to the same approach.

From the SDK:

The createdon attribute specifies the date and time that the record was created. To import data in the createdon attribute, map the source column that contains this data to the overriddencreatedon attribute.
During import, the record’s createdon attribute is updated with the value that was mapped to the overriddencreatedon attribute and the overriddencreatedon attribute is set to the date and time that the data was imported.
If no source value is mapped to the overriddencreatedon attribute, the createdon attribute is set to the date and time that the data was imported and the overriddencreatedon attribute is not set to any value.

  • Link to BlogSpot
  • Link to Social MSDN
like image 100
Konrad Viltersten Avatar answered Apr 18 '26 22:04

Konrad Viltersten