InfoPath Dev

Does your new form have the same data structure as your old form? That is, are the XPaths in these lines correct:  var amountField = XDocument.DOM.selectSingleNode("/my:myFields/my:ChequeAmount");  var spelledField = XDocument.DOM.selectSingleNode("/my:myFields/my:AmountWords"); That would be what I'd check ...

You are using Frederik's code, is that correct? I think that one problem you are having is that you probably have a more complex data structure than his sample does. From the looks of the SQL statement to get your Region information, I'd think you'd need to modify the following lines: Instead of: string repeatingNode = ...

I would recommend you take the formula apart a bit. Start with making sure you are getting your incrementing number correctly. So try just (../preceding-sibling::*/@MilestoneDetaiID1) and see what you get. It sounds like right now you are getting '0', which explains one of the '1's in your '11'. What field in your data ...

I'm afraid I don't have very good news for you in this scenario. This is most easily done when the form is submitted someplace where the data is accessible -- like a database or sharepoint. Even then, you'd have to use code (or qRules, if you use IP 2007) to copy the repeating data into your new form. You can do this entirely with ...

Have you run your code in debug to verify that newQuery.Command is exactly what you'd expect it to be?

Hi -- I'm not sure of the answer to your page break question, but you have a few choices for your 'N/A' text boxes. The simplest would be to add two expression boxes for each field that might hold text or be blank. Set conditional formatting on one expression box to hide if the field is blank, and for the XPath, bind it to the field. ...

Hi, and welcome. As I recall, you'll need to do this with rules instead of default values for this to work in IP 2003. I'd guess that you'd set the rule on your 'Approver' field, from your XPath -- whatever makes sense for your form. What field changes that would give you a different email? That's the field to set the rule ...

Hi -- So you have a drop down list control that is bound to a query field, and you get this error when you set the control to use that secondary data source for your list items? Actually, I can replicate this -- if I choose a data field from the Main data source as the values for my drop down list.... but if I choose my secondary data connection, ...

Hi -- and welcome. I'm not certain why you are doing this in code. You can use XPath to filter the second dropdown instead. Check out this Office Online tutorial for more information.