#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

Conflict handling - add an option to merge a field (especially document history fields)

Many developers add a "history" field in their applications to document when/who updated a document and what happened.

This prevents the "Conflict Handling" form property "Merge Conflicts" option from working as there could always be a difference in this field even if otherwise the document could be merged.

To improve merging and reduce conflicts add a field option for merging

options should be:

1)  "ignore differences" in this field when merging documents. The winning document's field is used.

2) "merge field contents" - The contents of the field are merged. An entry is added to show the merge happened. Field contents would have to be in a specified format e.g. dd-mmm-yyy hh:mm:ss username - history text

3) a default option to work as it does now

Maybe a new "document history" field type would help resolve this situation. When entries are appended via LotusScript or @Formula the date and time and username are automatically prepended.

  • Guest
  • Jan 21 2019
  • Under Consideration
  • Attach files
  • Guest commented
    25 Jan, 2019 04:00am

    I currently have a PMR ticket open with IBM.  "Merge Conflicts" is broken and I'm not sure where it broke.  But, this feature needs to be put back and make it work.  If IBM/HCL can't make this feature work properly again, I don't have much hope for this product further as replication is key to this technology. Without "Merge Conflicts", I don't have much choice to recommend a different platform for my clients...

  • Guest commented
    22 Jan, 2019 03:59pm

    Document locking doesn't resolve the issue if you have remote users who aren't connected, or able to connect, to your server. 

  • Guest commented
    21 Jan, 2019 04:52pm

    Best way to avoid conflicts is to "allow document locking" and apply an admin server to the Notes application.  Sure, you might get someone who doesn't close a document properly and leaves it "locked" but that is easy enough to deal with.