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
Moving idea to product : Domino Designer
This is a great idea. It would give the opportunity to store data with relations, without any duplicate data.
It is no problem, that it costs some performance, because the indexer would "save" the looked up data within the view index like today.
Example of a contact database:
A person is related to a company document. Only by having the company unid key reference within the person document, one could having all needed company fields within a person view!
You are right, the issue is similar to dblookup, but my intention was to enable the command GetDocField in a column, and that is a diffent command. If dblookup would be possible this would help indeed.
So you are essentially asking for something similar to @DBLookup in view column, but without the performance cost, right ?
I think that there is a similar idea about the ability to do something like SQL "JOINT" statement in view, maybe these ideas can be combined together ?
That is a great idea, and contrary to a @dblookup should not wreak havoc on performance imho.
Comment by Theo Heselmans