-
Your expression box is most likely sitting in a section bound to a node higher up the tree than your text box. So, definitely, the expression box would use the XPath my:projectLead and your text box would use ../my:projectLead. The ../ is taking you up the tree - so let's say your text box is bound to a field under the myFields folder called ...
-
You can use the CreateFolder method of the SharePoint Lists web service to create your new folders. Then use qRules ChangeSubmitUrl to point the SharePoint Library submit data connection to your newly created folder. Finally, submit and you're done!
-
I'm going to assume this means you've got this sorted... ;-}
It takes some time getting used to IP - here's your new best friend - an MSDN page...
One thing you will probably find different (read "annoying" is that you aren't going to be able access the controls on the form programmatically - just the data in the XML. ...
-
You aren't a pain, I'm just cranky today. :-}
You need to get Year 2 again using a relative path...
So:
e.Source.SelectSingleNode("../my:Year2", NamespaceManager)
The ".." takes you from Year1 back up to SemesterDetailInformation, and from there you can select Year2.
-
This is why I keep asking where your button is located.
At any rate, it sounds as if you are saying that the button is in Year 1? Is that the case? If so, just e.Source would get you the Year 1 node. Again, you should run debug, see what the value of e.Source is.
-
e.Source.SelectSingleNode("YearSelection", NamespaceManager)
-
Where is your button? Is it in Specialization?
Run in debug, and take a look at e.Source to see what node it is.
-
You said your button was in a section - the section is bound to your repeating group, Specialization, right? So you could get a node like this:
XPathNavigator yearDDL = e.Source.SelectSingleNode("my:SemesterDetailInformation/my:Year2/my:YearSelection", NamespaceManager);
-
You are using absolute XPath to get your node - that will always return the first node. Look into the ClickedEventArgs.Source property and use relative XPaths.
-
Thanks for the update - I'll add that originally your form was set to:
Submit XML to SharePoint library
Submit to SharePoint List via qRules
Close the form
Since the XML was submitted before the qRules command was run, the id fields were blank when the XML was saved in the library. You then switched the order, so you were using the ...