 <p>If you need relational properties, <strong>look for non-Notes solutions</strong>. It is possible to get some relational behavior using document UNIDs and update agents, but it will be harder than with a proper relational backend.</p> <p>Your specific problem with referencing to a piece of text that might change can to some extent be resolved by using <strong>aliases</strong> in the choice fields. If a dialog list contains values on the form...</p> <pre><code>Foo|id1 Bar|id2 </code></pre> <p>...the form will display <strong>Foo</strong> but the back-end document will store the value <strong>id1</strong> - (and this is what you will be able to show in standard views - although <a href="http://www.lotus911.com/nathan/escape.nsf/d6plinks/NTFN-7FRG79" rel="nofollow noreferrer">xpages</a> could solve that). Using the <code>@DocumentUniqueID</code> for alias can be a good idea under some circumstances. </p>