-
For next time - there is a Options tab, and you can attach a screenshot there - glad it downloaded correctly this time. :-)
-
How do you usually open your templates in design mode?
-
Can you tell me what you mean by "returning values" - do you mean that the values of your higher level items aren't being populated in your list?
I'm pretty sure, given the previous sample you showed, that you have one too many "../" in your relative paths.
Did you try the syntax I suggested in my earlier ...
-
The relative path is the path from the repeating node. Your repeating node is: my:expenseReport/my:items/my:item
Your relative path would be:
<my:Mapping>
<my:FormField ...
-
Okay, so back we go to my original post - type in the relative path to the non repeating field you want. You can type in the field text box. You do not have to use the node picker. I am not sure how else to explain this.
-
I must have misunderstood you. You need to submit to two separate lists? Is that what you are saying? If so, then you do need to create two mappings - one for each list, and two submit connections - one for each mapping file. Does that make sense?
-
You can use relative paths in the mapping - so, one mapping with relative paths to the fields outside of the repeating table.
Say you want to map the Buyer field - the relative path from the ItemDetails group would be ../my:HeaderInfo/my:Buyer. So you would just hand enter that in the Field column in the mapping tool.
-
I'm not finding much for this error online, and I can't reproduce it. Can you try the command in your form w/out the /id parameter? And if you can access the SharePoint logs to see if there is more info in the log files, that would be great.
-
You bet - I'm happy you got it all sorted out!
-
You bet - glad you got it working!