Re: Problem setting field values with filter

SteveJones — Sun, 08 Aug 2010 17:05:00 GMT

I have managed to bypass this issue by writing code behind to accomplish this task. I loop thru the DocOwner nodes to find the one with the ID that matches, then I set the other childnodes as required. I was hoping to avoid code in the form, but it seems unavoidable. Is there a way to select the proper DocOwner node without looping thru them? something like ' dest = ...selectSingleNode("../my:DocOwner[CurrentID]")?

I guess the way the filters were designed to work was to set a value of a non-repeating node from a value in a repeating node (filtered), but I am trying to do the reverse.

Problem setting field values with filter

SteveJones — Sat, 07 Aug 2010 18:19:01 GMT

I can't get a filter to work when saving form data to the xml. My xml contains these nodes:

<my:myFields>
<my:CurrentID />
<my:Action />
...
<my:DocOwners>
<my:DocOwner> (this is a repeating node)
<my:DocOwnerID />
<my:DocOwnerAction />
...
</my:DocOwner>
</my:DocOwners>
...
</my:myFields>

DocOwner has two rows, and DocOwnerID is populated with two different user IDs. These two people receive an email note with a link to the document. When they open the form, a web service populates CurrentID with their user ID from Active Directory. Action is a dropdown list and they have to select a value prior to clicking the submit button.

There is a rule set on the Submit button that says to set the DocOwnerAction Field from the Action Field with the rule [DocOwnerID = CurrentID]. The second rule submits the form to a Sharepoint Form Library. But upon execution by the first person it sets both DocOwnerAction fields, and then upon execution by the second person it sets both DocOwnerAction fields to the new value.

Any ideas?

General

Re: Problem setting field values with filter

Problem setting field values with filter