Thanks for putting this out on the list. I have been typically just
copy/pasting the same setvalue tags to each of my submit triggers, but I
can (and likely should) be using this method instead to keep things
simple. Nice question, nice answer.
Zach
Joern Turner wrote:
Chris,
regarding my previous mail i should have said: 'the event the setvalue
should react to' (not submission). sorry for the confusion.
Joern
Chris Picton wrote:
Hi
I am trying to use an action on a submission element to set the values
of certain nodes just before form submission.
At http://xformsinstitute.com/essentials/browse/ch08s02.php, at the
section titled Submit processing of relevant nodes, it describes a
technique to ensure that the entire node tree is submitted.
I have attached a form for which this is not working.
I expect the following:
The node 'other' should always be in the submitted data regardless of
the value of the first input (node 'name')
However
It seems that the relevance isn't being calculated correctly.
Using the submit (labelled 'Not working submission'), the node 'other'
only is part of the submitted data if the first input has the value
'test'
Using the trigger (labelled 'Partly working trigger'), the submitted
data only has the node 'other' if the first input has, or HAD the value
'test'.
If I am doing something stupid, please let me know.
Chris
------------------------------------------------------------------------
0 Hello Your name: Other: Not working submission Partly working
trigger Reset
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
|
