Back on the multivalue key for @dblookup... I think it's cool that you can use an initial @dblookup to return a list, and use that list, in turn, to perform a second set of lookups. @Formulas can be pretty powerful when you start leveraging them in series.
I think you're right Lutz on the surface. You're talking about asking the ID to get the document directly, like a URL that is formulated 0/unid?opendocument. It's going to be more reliable than waiting on a view to build to use view.getdocumentbykey... especially if the view wasn't built -just- for your lookup. I say 'on the surface' as I havn't put the conventional wisdom to the millisecond test just yet. Seems logical though.
Back on the multivalue key for @dblookup... I think it's cool that you can use an initial @dblookup to return a list, and use that list, in turn, to perform a second set of lookups. @Formulas can be pretty powerful when you start leveraging them in series.
I think you're right Lutz on the surface. You're talking about asking the ID to get the document directly, like a URL that is formulated 0/unid?opendocument. It's going to be more reliable than waiting on a view to build to use view.getdocumentbykey... especially if the view wasn't built -just- for your lookup. I say 'on the surface' as I havn't put the conventional wisdom to the millisecond test just yet. Seems logical though.