dCreateDate of New Revision Added Through WebDAV Is Same As Previous Revision Minus Seconds (Doc ID 445989.1)

Last updated on MAY 19, 2017

Applies to:

Oracle Universal Content Management - Version: 7.5.0 to 7.5.2 - Release: Stellent to Stellent
Information in this document applies to any platform.
Checked for relevance on 20-Mar-2009

Goal

You are checking in a new revision of a content item through WebDAV using Microsoft Web Folders. When you look in the database, you see that the value of dCreateDate for the new revision is the same as for the previous revision, but the seconds have been set to "00". This is not the case if you check in a new revision through the Content Server browser interface. If you do the checkin that way, the new revision gets a new dCreateDate.

For example, you checked in revision 1 of a content item through the browser at 9:42. You then checked in revision 2 of the content item through the browser at 9:44. Finally, you checked in revision 3 of the content item through WebDAV at 9:45. The values from the database are as follows:

dDocName

dRevLabel

dCreateDate

dInDate

000080

1

2007-03-13 09:42:20.810

2007-03-13 09:42:00.000

000080

2

2007-03-13 09:44:15.447

2007-03-13 09:44:00.000

000080

3

2007-03-13 09:44:00.000

2007-03-13 09:45:28.720

Notice that dCreateDate for revision 1 and 2 (checked in through the browser) reflect the actual time the content item was checked in.  However, revision 3 (checked in through WebDAV) has a dCreateDate that is the same as revision 2, with the seconds set to “00”.

What is causing this and how can it be resolved?

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms