In our solution to this problem you can define what attribute to use for value and what attribute to display (even multiple). In addition "uuid" and "name" are supported as "special attributes". This has worked fine for us so far.
-will On 12.07.2011, at 10:30, Jan Haderka wrote: > > I don't think there's an issue with storing uuid, but more with what would > the uuid represent in the value that would be also meaningful to the client? > The node name or title or ...? > > On Jul 10, 2011, at 11:00 PM, Danilo Ghirardelli wrote: > >> >> Hi everybody, >> just a quick question. The select dialog can be used to show values (and >> labels) from a list of nodes in any repo, but you are always bound to use >> some node property as stored value. I was just wondering why not to use the >> node uuid? Is there any downside that I can't get at first glance? You have >> to retrieve the node first and the the properties you may want, but this may >> be the expected behaviour in some cases. Still I have never seen the select >> used like this, so I'm just thinking if I'm missing something. >> >> Regards, Danilo. >> >> >> ---------------------------------------------------------------- >> For list details see >> http://www.magnolia-cms.com/community/mailing-lists.html >> To unsubscribe, E-mail to: <[email protected]> >> ---------------------------------------------------------------- > > > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- > ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
