Upload Document and Change Create Date

Hi,

I'm uploading a document using the Enterprise Web Services, however the create date I specify does not get set. Instead the current date is the create date. Here is a some of my code:

// Apply the file information and contents of the document to the attacment object.

DocumentManagement. Attachment doc = new DocumentManagement. Attachment ();

doc.Contents = contents;

doc.CreatedDate = fileInfo.CreationTime;

doc.FileName = fileInfo.Name;

doc.FileSize = contents.Length;

doc.ModifiedDate = fileInfo.LastWriteTime;

......

DocumentManagement. Node obj = dm.CreateDocument(ref dmOTAuth, parentID, "test2.doc" , "Add Comments Here" , false , metadata, doc);

Anyway, is it possible to set a different date for the create date?

Thanks,

Find more posts tagged with

Comments

Hugh_Ferguson

I haven't been able to do this either. Given that Object Importer allows this, it is technically possible but updating the creation date on a DAPI node (even before create, just after the alloc) doesn't seem to be covered.

In theory, you could patch the SDO to do this if you can find the point inbetween node allocation and node creation, and set the node.pCreateDate flag.

-Hugh

Kyle_Swidrovich

I’ll provide an official OpenText response on this…

Although the CreatedDate and ModifiedDate properties can be set locally in the object, the server will ignore these value when updating the metadata.

This is by design.

Hugh_Ferguson

This confirms what I've observed in the code. Whether or not I'd try to patch the SDO would depend on how badly the client wants to set dates other than the create date. I'm doing a lot of data migration work these days and they ask for all kinds of crazy things

-Hugh

Vanderpoel_Rob

I was looking at the OI code recently and my recollection is that theyexplicilty use SQL there to enable these dates to be overidden onimport. Will confirm when I'm back in the office.

Hugh_Ferguson

I just checked. It happens in OI's _SubclassMetadata. At that stage you have an allocated node but it hasn't been created (effectively you've been assigned a dataID and not much mroe. In that method, the create date is set by setting the node's pCreateDate directly on the DAPINode object. After this is done, the LLNode.NodeCreate() method is called. My suspicion is that as was stated earlier on a different thread, that once you write the values to DTree, the date is not modifiable, but you have a window between nodeAlloc and nodeCreate to do so. This might be a nice feature for WS as more and more data migration applications will want to set the original create date when importing into Liveli....er...Content Server.

-Hugh

Vanderpoel_Rob

My recollection with regards to direct SQL wasn't right for create date. It does this for modified date, though, at least in my development box, which is still at Update 5. This happens in _SubclassCreatePost for documents.

Ferdinand Prantl

Wanting to set CreateDate and ModifyDate in any ECM system is a almost always a bad idea. They are system fields and match with the audit log. If you are able design your scenario (importing documents from other system) without this, using custom properties and forms/views, for example, you'll have some extra work but no problems. While you can hack the system into this on the database level, it is not supported in Livelink or SharePoint and impossible in Lotus Notes, for example.

--- Ferda