What does the 2nd Modified on the Document Info tab refer to?
I’ve got some documents that show 2 different dates in the 2 different Modified. When I create a view by @Modified, the 1st date is used. How can I get the 2nd date to show in a view?
Example:
Created 09/11/2002 01:37:08 PM (Initially)
Modified 09/11/2002 01:40:35 PM (Initially)
Added 11/15/2005 10:01:21 AM (In this file)
Modified 11/15/2005 10:01:21 AM (In this file)
Also, $Revisions does not show 11/15/2005 as the last date modified. The only date listed here is 9/11/2002. How can this be?
I’ve tried searching Document Info & @Modified in both forums, but haven’t found anything like this.
Let me try to explain, I am not a native english speaker :).
Created and Modified (Initially) are referred to the real date/time when the document was created/modified, regardless on which replica of the db was performed the action.
Created and Modified (In this file) are referred to the date/time when that document was created/modified, , through a replication action, to the db replica using to view the document’s properties.
I think that the info that you wuold show in your views is the initial Created/Modified, since they are when the user (o server if there are scheduled agents) created or modified the document.
I need the 2nd date because these documents suddenly appeared in a view for Pending docs. Last Friday these docs were not showing up in the view. Today they are there. The Pending view is monitored regularly, as the information is date sensitive.
These documents are from 2002 and were closed quite a while ago; hence, they would not show up in the view. The server hardware was changed out over the weekend. Why documents suddenly show up in the view if they were modified/replicated on 11/15/2005?
I’m guessing that these documents were deleted from your server copy sometime in the past. However, someone had an old local replica copy which had not seen the “delete action” in time (more on this below).
So when they replicated on November 15th, Notes saw these document in their local copy, and not on the server copy - so it through they were “new” and replicated them over to the server.
This is something that hits all of us occasional, and there’s no really good answer to the problem.
How deletion replicates.
When you delete a document from a replica (local or server) Notes leaves behind a “deletion stub” for a certain amount of time. As replication happened between copies, it’s this stub that allows the deletion action to be propagated to the other copies.
The problem is that these stubs have a fixed life-span (which you can control and we can go into that if you want.) Once they are removed, Notes “forgets” about that original document.
So if there is a replica that did not sync-up within that life-span, those documents are not deleted, and are instead replicated back to the server as “new” documents.