-
I think you want:string sExistingTitle = xnMyForm.SelectSingleNode("/dfs:myFields/dfs:dataFields/dfs:Request_For_Change/@Title[. = '" + sNewTitle + "']", NamespaceManager);
-
What is the logic you are using to hide the control? For example, if your control were bound to field1 and you hid the control when field2 = true, you could then set a rule on field2 with the condition 'when field2 is true' to run the action to set the value of field1 to blank.... does that make sense? I've attached a quick sample in ...
-
I've attached a simple sample form that might explain this better than I can. To use it, right click on the link in the header of this message and select 'Save as' and save the file locally. Right click the file and select design to open in design mode... Check the rules on the first two fields and the 'toggle' field...
-
Hi -- what about using rules to populate the fields? This would work if the drop down was bound to a field in the same group as the field that you want to change the value on. Otherwise, take a look at this InfoPath Team blog post on conditional defaults... it may help. I've used the second method mentioned quite frequently, and while it seems ...
-
Hi, Ian:
I know you've got several posts going on this right now, but I have to say the same thing everyone else is -- Word print views are hard. If you are using InfoPath 2007, this blog post might help you. If you are using 2003, try this.
-
Hi --
There is a post by Jimmy Rishe in this thread that I think explains what you want to do -- specify a filter on the target field for a rule. I use this technique when I need to and I really think it is slick...
-
Hi, and welcome!
I fear you'll have to also put rules on the 'expense request amount' field. Rules are bound to a field and fire when that field changes.... so there are no rules firing when the 'expense request amount' field changes.
You could put all your rules that set the month values on an entirely different field and ...
-
The file attachment control is supported in a browser form, but the base 64 data type (which is what the control stores) can't be promoted up to your SharePoint site. The documentation is simply talking about the control itself, and you are right, it wouldn't be in your tool box if you couldn't use it. But the error message you are ...
-
Hi, and welcome!
Forgive me, I'm confused. You have a drop down list bound to a field in your main data source, and the list is populated with values from a secondary data source, is that correct? The control is set to use the 'key' {1,2,3 in your sample data} as the value for the control, and the 'name' {Chicago, Paris, Sao ...
-
Well, the DB name is used in the data tree.... so XPaths will change.
To rebuild the .xsn, simply use File --> Save As and save as an .xsn. This repacks up your template files.