I haven't tried #show yet but I have tried #ask. It seems that the
parser functions cannot be called inside of {{{field}}} tag.
> So is that definitely the case, or are you just guessing that you might
> require this feature in
> the future?
Definitely-definitely. We need some kind of solution f
Ah, that's true, I didn't think about the "edit with form" case. Well, for
that, you could use #show, assuming the value is being stored semantically
- and you could have an #ifexists call to tie the whole thing together, so
that #urlget is called for new pages, and #show is called for existing
pag
I need the first one. There are some problems with this
UrlGetParameters approach: it seems that it will work for article
creation using the #formlink but it will not work for article edition
using 'Edit with Form' button. Another problem is that the parameters
for allowed value set restrictions ma
Hi,
No, the two examples are different - the "silly" one involves two
"substitions", based on editable fields, while the "real" one involves one
substitution, directly from the query string. Can you clarify the
discrepancy? What is the form that you actually need?
-Yaron
On Mon, Oct 1, 2012 at 1
Hi Yaron!
No, these two examples (the synthetic and silly flower example and the
real-world brainstorming example) are really the same.
What I need is to use the data that user put in the field1 as the
parameter of the query that defines the allowed values set in the
field2.
Anyway, I'll try to c
Hi Yury,
I don't understand - are your data needs more complex than what you put in
that sample form definition code earlier? If so, can you revise that sample
code to more accurately reflect what you want your form to look like?
-Yaron
On Mon, Oct 1, 2012 at 2:53 AM, Yury Katkov wrote:
> Hi Y
Hi Yaron!
There is no problem in passing the Session parameter I can use either
'query string' parameter of the formlink or the urlget function.
In this Trend form my main problem is to restrict the set of possible
values which will be displayed in the "Related events" listboxes:
1) All these valu
Hi Yury,
This sounds like a very different example - here the original, "source"
field is just a hidden field that gets its value from the query string. In
that case, I would think the ideal solution would be to use the
UrlGetParameters extension, to directly use the query string value:
https://w
Hi Yaron!
My example is surely very silly and synthetic so let's just forget
about the flowers
I'll try to explain the real problem I faced with in a Foresight wiki.
Here is my problem domain. There are several brainstorming sessions
about the forecasts on a distant future, all of them have diffe
Hi Yury,
Well, you bring up two proposed features for SF here: a standard "values
from query" parameter (which you submitted a patch for), and the ability to
include variables, representing the current content of some other form
field, in the field tag - which could go into a "values from query"
p
10 matches
Mail list logo
