#dominoforever | Product Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Add accurate Last Modified date/time

It seems that the Last Modified date/time is taken from the OID and is required to be unique:


Due to this tie, and issues with many updates being done in a short time, the OID drifts ahead of the current time. This means that the Last Modified date/time value derived this way cannot be relied upon to be accurate. It also has a down-stream affect on the $Revisions field.

Could a field be dedicated to the actual last modified date/time so that it is accurate?

  • Guest
  • Dec 9 2022
  • Needs Clarification
  • Attach files
  • Guest commented
    13 Dec, 2022 12:16am

    There is no support ticket for the case. Just a recent observation.

    For 12/12/2022, the last document modified by the agent was at 9:22:27pm, and the modification date/time is 11:42:20pm.

  • Admin
    Thomas Hampel commented
    9 Dec, 2022 02:44pm

    Yes that is by design and has been a problem in the past where Domino servers were not as powerful as they are today. How much of a time drift do you see in your environment? Is there a support ticket for your case?