I remember being annoyed with this a few months ago. I got around it
by making the default value for truly optional fields a dash (-).
More recently, another person on our team used the parser function
statement in the template to only show the field if there's a value;
which short-cuts the
Probably more like a few days.
On Tue, Sep 30, 2008 at 5:23 AM, Daniel [EMAIL PROTECTED] wrote:
Thanks for the fast response, Yaron ;-)
Could you please give me an idea of when it may be fixed?
Does it need a few days or several weeks to integrate?
Thanks
-Dani
On 30 Sep., 06:28, Yaron
Is there a way of populating 'Allows Value' lists dynamically, from the
result of a query? I've come accross a number of situations where such
functionality would be useful, but have so far not found any way of
achieving it.
Guy
--
View this message in context:
