Welcome to the #dominoforever Product Ideas Lab! 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 jointly by the IBM & 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 database option "Do not allow user save Conflict document"

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jul 19 2018
  • Attach files
  • Admin
    Thomas Hampel commented
    July 21, 2018 01:03

    What should be done instead of creating a replication or save conflict??? 

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    July 23, 2018 07:56

    Messagebox "Other user has changed this document. You can't save the changes as it will lead to the conflict. Reopen the document and once again make the changes and save it." with OK button only.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    August 26, 2018 13:31

    Is there a reason why you could not use the existing "Document Locking" functionality to achieve this?

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    09 Feb 01:54

    > Messagebox "Other user has changed this document...

    That message is already there.
    1. Open the document.
    2. Ask a colleague to edit and save the document on his computer.
    3. Edit yourself and try to save the document - you will get exactly such a message.

    I just do not need this message, because in such cases we automatically create requests to change the document.

    There is a way to fix it elegantly - when transiting a document into edit mode, reread it from disk, that is, getting the freshest copy of it. I wrote about this on IdeaJam many years ago, but this unfortunately did not fix it.