Modifying a node's CreateDate and ModifyDate

Hi there,

From what I can see, we should be able to modify CreateDate and ModifyDate properties on a node through web services but I can’t get it to stick.

I’ve modified the sample to test this as follows:

newDoc = docManClient.CreateDocument(ref otAuth, parentID, fileInfo.Name, "Initial Comment", false, metadata, attachment);

Console.WriteLine(" Created: CreateDate: {0}, Comment: {1}", newDoc.CreateDate, newDoc.Comment);

newDoc.CreateDate = fileInfo.CreationTime;

newDoc.Comment = "Modified Comment";

docManClient.UpdateNode(ref otAuth, newDoc);

Console.WriteLine("Modified: CreateDate: {0}, Comment: {1}", newDoc.CreateDate, newDoc.Comment);

int tempID = newDoc.ID;

newDoc = null;

newDoc = docManClient.GetNode(ref otAuth, tempID);

Console.WriteLine("Reopened: CreateDate: {0}, Comment: {1}", newDoc.CreateDate, newDoc.Comment);

and here’s what I get:

Created: CreateDate: 4/8/2014 2:42:51 PM, Comment: Initial Comment

Modified: CreateDate: 9/24/2013 12:33:12 PM, Comment: Modified Comment

Reopened: CreateDate: 4/8/2014 2:42:51 PM, Comment: Modified Comment

So I can see that the node is being updated by the change to the Comment. But even though it’s accepted the changed CreateDate, the UpdateNode is not committing that change. The same happens for ModifyDate.

Is this a bug? Working as designed? Am I doing something wrong or is there a workaround?

Thanks

Rob

Find more posts tagged with

Comments

Jason_Smith

This is working as designed. The node create date and modified date cannot be updated. The create date is set on creation of the object in Content Server and the modified date is updated whenever some other property of the node is updated.

Steven Herring

Jason,

I have always given the answer that you gave in the past but something cropped up today causing me to rethink. Given that most users have long since stopped using or relying on LAPI and now rely solely on Web Services how should we deal with this date issue when dealing with long term archiving ?

In other words if we are adding records (documents) with a Fixed Retention (meaning the CreateDate is all important) then surely it should be possible and in fact necessary to touch the CreateDate ?

Is there any plan to revisit this or am I missing something ?

Steven

appuGmail

You probably want to post this in the RM forum.RM can key off many dates its processing logic so in most cases the legacy date could be a date field in a category that you have designed for that purpose .OI old versions also was able to change this although I am not too sure because the new OI seems to be having many more oscript changes than the old ones so perhaps the immutability is exercised there also.OI being oscript could also be patched/extended so could most of the webservices for a oscript person.

..... appnair appunair( Livelink Rocks )

Well, if I called the wrongnumber, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

On Tue, Feb 28, 2017 at 4:47 AM, eLink Entry: Content Web Services Forum <otdncontentwebservices971forum@elinkkc.opentext.com> wrote:

Modifying a node's CreateDate and ModifyDate Posted byHerring, StevenOn 02/28/2017 05:47 AM

Jason,I have always given the answer that you gave in the past but something cropped up today causing me to rethink. Given that most users have long since stopped using or relying on LAPI and now rely solely on Web Services how should we deal with this date issue when dealing with long term archiving ?In other words if we are adding records (documents) with a Fixed Retention (meaning the CreateDate is all important) then surely it should be possible and in fact necessary to touch the CreateDate ?Is there any plan to revisit this or am I missing something ?Steven
[To post a comment, use the normal reply function]
Topic: Modifying a node's CreateDate and ModifyDate
Forum: Content Web Services Forum
Content Server: Knowledge Center CS16

Kyle_Swidrovich

Steven,

The CreateDate and ModifyDate fields are reserved to only reflect the object’s existence within the Content Server system.

This is why their values cannot be defined/updated by a general public API.

They are implicitly recorded based on the introduction of an item into Content Server or when the properties of the item change.

As Appu noted, RM provides a Record Date field that can be used during import to define a ‘start’ date for the item for RM purposes.

Object Importer provides an administrative method of adjusting the CreateDate/ModifyDate values.

And finally, in the upcoming 16.2 release, we will be providing new “buckets” for storing the source system dates for reporting and search purposes.

While not necessarily suitable for all RM purposes (for a variety of reasons), they do provide a new interesting set of data points for ingested items.

Regards,

Kyle