-
I'm a little confused -- the first part of your post suggests that your web service will return only the correct values for the given login name -- so wouldn't you just create an InfoPath data connection to receive data using that web service, then in a rule in the form (like an open rule) set the value of the query parameter to the ...
-
Euw, then I'm afraid I don't have very good news. The only way I know to do this would involve writing code. I'd probably add an XML data source to my form and use it for my drop down values, then use code to populate it with the data from the repeating section and the static field.....
-
The only way I know to do this is to use code, and add the item to the secondary data source that the dropdown is bound to. Does the value of the single static field change vary per form? Is the repeating section you mention from a secondary data source? If it is a SQL data source, and the additional field is a single, unchanging value, you ...
-
Both changing to what? If you use the Design Checker on your form, are there any errors? This could be because of the filtered XPath for the rule targets....
-
Looking back at your original post:
XPathNavigator DOM = this.DataSources["Customers"].CreateNavigator();
XPathNavigator group1 = DOM.SelectSingleNode("//Customers", NamespaceManager);
XPathNavigator field1 = DOM.SelectSingleNode("/my:myFields/my:CustomerName2", NamespaceManager);
You've declared your ...
-
See how in your expression for the ID field you have a filtered XPath?
expression="xdXDocument:GetDOM("Regional Servers")/dfs:myFields/dfs:dataFields/d:SharePointListItem_RW/d:ID[xdXDocument:get-DOM()/dfs:myFields/dfs:dataFields/my:SharePointListItem_RW/my:Title = ../d:Title]"
While in your expression for the ...
-
You can definitely do something like this with InfoPath. The labs should help you get started, and forum can help when you get stuck.
-
I'm sorry, I forgot about that IP limitation for rules. Here's a blog post that explains how to do this in the manifest.
-
Put a control on your form bound to your update datasource, so you can verify what your resulting CAML looks like after your rules run. You also need to add another Field node to your XML for your update data source -- as I mentioned early on, you need <Field Name="ID"></Field>.
Your CAML should probably look something like ...
-
If the "Customers" group is in your main data source, I'd expect it to use the "my" namespace, like your "CustomerName2" field is. Just right click the group in the data source task pane and select "Copy XPath" and use that instead of "//Customers".