InfoPath Dev

You can combine repeating section fields in this way using a 'double eval' method. Here's my little 'recipe' xdMath:Eval(xdMath:Eval(<your repeating group>, 'concat(<field in repeating group to combine>,"<string or field to insert between on each combine>")'), "..") Here's ...

 Sure, make your formula in the To: field of your submit data source: concat(field1,";",field2,";",field3) etc etc The concat function tells Infopath to combine all the values you put in the comma delimited list inside the brackets. The semicolons are typically used to separate email addresses in a To / CC  field.

 hmm only 1 attachment per post allowed. Here's the datasource.

Hmm well, the datasource was all id's and people with the same name ;-) so it's hard to tell if this is working perfectly. But it looks correct. Attached. I had to add a dummy '1st level' person as the list box control wouldn't let me use the datasource with only one. Also note I've let the template have the secondary ...

I'll have a stab at it. I'm not even sure you need to use code. I'll use your first set of data. Though normally I would expect to see this kind of hierarchical data presented in a different way. I assume you get this XML from another source and this is the format it comes in? The way I usually  see it something like ...

This is just how I do things - might not work well for you. Everything I edit in a form is either inside of a section or inside of a layout table. I work on 630 pixels wide as a pretty good fit for A4. When I create section controls I immediately go to it's properties and set the margins and padding to 0 and turn off the borders. This is ...

A submit secondary datasource gives you the ability to set subject line and attachment name based on field formulas. But I'm not sure I understand how the repeating section value is to be used. Do you want just one particular value from one of the repeating sections? Is there a submit button in every repeated section? Anyway, I am betting a ...

I can't think of a way which won't involve going back through the fields on each view and adjusting the validation rules. You could try using a field to hold a 'submitView' value. Then on each view which has it's own submit button, the first rule of the button would be to set the 'submitView' field to an identifying ...

A possibility: Check for empty spaces either side of the values being returned from your datasource. A way to check is just drag the datasource onto a blank view and make a repeating table of the data. Then open the form, do a query of the datasource and change to that new view. Highlight the values in the repeating table corresponding to the ...

I'm really not sure if this will help you as I have no experience in using Web services, but the linked template shows a jScript method of merging two rich text fields. http://www.infopathdev.com/forums/storage/43/67007/joinRichTextFields.xsn Maybe the logic can be used for your service? It relies on the fact that rich text fields contain ...