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
You can code this now including changes to the field in the original document even in another application (if that is what is being suggested) but you would also need to be sure you have a lock on the target when executing this. Maybe a new field Type "Share Field" that allows the selecion of database / form / field and this meta information is stored but the field takes on the original field properties (text / numeric etc). Additional options to display only / update on save / update on change and possibly a failure option eg allow save if source not avaiable. Domino can then check for these types of field and deal with them as appropriate on loading / closing / saving.
I think what he's getting at here is having the field on the form but when saving the form it would save the value of that field in the original document instead of the current document. You can display fields from another document fine but saving is where the issue is. Correct me if I'm wrong here.
I see where you are going, and I’ll vote for it.
However you can already achieve this yourself by storing a unid of the related document (but has to be in the same database), and use @getdocfield, to show fields from the related document on a form.
caveats: Only links to the same database, and cannot be used in a view or for searching.
Comment by Theo Heselmans