Skip to Main Content
HCL Domino 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

Status No Plans to Implement
Workspace Domino
Categories Administration
Created by Guest
Created on Aug 22, 2022

All databases can be replicated on the server side, regardless of access privileges

We understand that it is a function to synchronize between servers, except only for necessary or unnecessary portions. For example, if you set a specific user to "Who can read this document" in the document properties, the documents will not be replicated to the destination server.
Customer wants to replicate the entire database to the backup server. Therefore, they would like to add the ability to replicate all elements of the database (documents, design elements, etc.) on the server side, regardless of the database settings configured on the user side.

  • Attach files
  • Guest
    Aug 22, 2022

    We already know that if we create reader/author name fields, we can replicate it. However, it is not a practical action to add reader/author name fields to every form in every databases on the server after the fact. Therefore, the request is to be able to duplicate all of them on the server side without having to do such work.
    We would like it not to be No Plans to Implement out of the blue without asking for our background.

  • Admin
    Thomas Hampel
    Aug 22, 2022
    Rejecting this idea because you can already now replicate all documents if the design of the application wouldnproperly use reader/author name fields (e.g. with roles) that are assigned to the servers.