Overriddencreatedon

Everybody who's performing data imports knows the problem. When you create a record in CRM, the created on field always points at the date the record is created. Ofcourse you could go into the database and update the date by using a SQL script. But then again, there is this good white angel hanging above your shoulder whispering "Don't do it, it's not supported". No matter what this angel says, the evil red devil shouts "Do it, your customer wants the correct data" and you go into the database.

Well these kind of situations are now history. The CRM development team has silently introduced a new feature. While performing an insert, you can set the attribute overriddencreatedon field. The value of this field will be used to set the record's created on attribute. So now you can import records in the history! A small feature which will make many people happy.

12 comments:

Jeffry @ CWR Mobility said...

Excellent, that's a nice little feature!

Anonymous said...

Hi.

You're talking about version 4, right?

Thanks,
Vasco

Ronald Lemmen said...

This is indeed newly introduced in CRM 4.0. My excuses for not making this clear.

Anonymous said...

No prob :-)

Thanks once again.

Vasco

Anonymous said...

ping back from http://www.castorsoft.com/articles/2008.1.23.htm

Anonymous said...

ufxThanks for the info, can you somehow use to field for orders that are already imported? the users want to be able to modify the the "created on" date for orders that have been previously imported.

Bill said...

But not when you are impersonating:

// Privilege prvOverrideCreatedOnCreatedBy is not available when impersonating.
// contact.overriddencreatedon = CrmTypes.CreateCrmDateTime( DateTime.UtcNow );

Anonymous said...

Now if we could just have an overriddencreatedby...

Ronald Lemmen said...

For that you can use impersonation while importing your data. That would set the createdby user to the user you want.

Senthil said...

Hi,

overridencreatedon filed is not working while updating the record. Is there any way to change this field through API.

Ronald Lemmen said...

Hi Senthil,

You should only use this attribute for setting the createdon attribute. This attribute has no other value, so trying to update this makes no sense. The real question though, that is: how do you change the createdon attribute. This is not possible in a regular plugin or feature. You'll have to do this on the database level, if you didn't set it correctly while creating the record.
Make sure that you challenge the requirement, because usually you don't want to change the creation data of a record.

Muhammad Muddassar said...

Thanks for sharing a best informetion
CRM Development Dubai:ERP Development Dubai