lapi allows it but it is controversial.CreateDate is when the object is created in livelink and bases livelink creating the object at that date.The historical create date is always attached as metadata.
several discussion on this exists and it always have the controversy that I say as disclaimer
I have tried using LL_CreateObjectEx() to add CreateDate into createInfo LLVALUE. The object was created, and checking the logs on server side my CreateDate is sent, but the new object's CreateDate is actualy the current date.
Can you give more details how to do it?
Thanks,
Cristian
right after you create the object run a UpdateObjectinfo on it.If you look at audit of the object
it will say version created and update happening by the lapi user in context.
Java/.NET Method Declaration
public int UpdateObjectInfo( int volumeID, int objectID, LLValue objectInfo )a java sample that I wrote several years which used to workhttps://knowledge.opentext.com/knowledge/cs.dll?func=ll&objaction=overview&objid=16473308
As Guy said if you use OI as the import file then CreateDate can be set with one call as well.
You should prefer not changing the system attributes.like Created or LastModified. While it is technically possible you can see that it is not without troubles. If you are able to come up with a design that does not need it you will save quite a bit effort. For example, creation date from the document origin can be saved to a custom attribute during archiving.
You can learn what other customers did in these threads:
https://knowledge.opentext.com/go/18862585
https://knowledge.opentext.com/go/18499576