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
Would be useful for troubleshooting.
The computed field suggestion wouldn't always work. e.g. for a conflict document it may have the value of the parent document that was created on a different server.
Adding a computed when composed field is great when creating new records, however the organisation that I work for has a database with over 1 million existing records, and 10 replicas. Without some form of script to access and compare created and added in this file timestamps on the notes document properties it's simply not possible to do the same for the existing records
Agree with the previous comment that a developer can add a custom field with additional information on the actual replica or computer name of the machine where the document was created on. so apologize for changing this idea to 'no plans to implement' - if you think this needs to be done anyway, please continue to vote for the idea.
Developers can easily add a field for that, e.g. storing @DbName in a computed when composed field.