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
Moving idea to product : Domino Designer
I was talking about Notes applications. I have never been able to get the "merge" conflicts option to work. If you read the fine print, I believe that option only applies when replicating databases.
As far as how you would implement this in a multiple-server environment, I really don't know. That's for IBM to figure out. I'm looking at this idea blog (which is a really great idea) as the firs step in problem solving. As such, I'm thinking that all ideas should be put on the table, without consideration of whether/how it could be done. In the next steps of the problem-solving process, IBM will boil all of this down to determine where to go next.
We have been able to work around the problem, by 'hardening' against two users and/or 'document locking'. I'm just throwing it out there that it would be much, much better if field locking were built in. I view it as a serious limitation of the software. We have some applications, where users complain on a regular basis, that they want to edit a document that someone else has open.
Is this for web/xpages or Notes applications? For Notes applications there is already document locking.
There's a form option to "merge" conflicts if different users edit different fields.
Distributed and local replicas are a major strength of the software. The disadvantage of any system that does this is the likelihood of replication conflicts.
Agents can be scheduled to run only overnight.
How would you implement this in a multiple-server environment where people are working on different replicas? If this is a requirement you should look at ways to set up the application so that it will be 'hardened' against two (or more) users working on the same field at the same time.