InfoPath Dev

Success!!! Thank you for all of your help Jason

I've already included the updated mapping in the XSN I included. But here's a copy in case you need it....

do I need to update my mappings.xml file? Thanks, Jason

You were correct!  Thank you. The actual field in question wasn't a lookup - but (using the example I provided) the store number was.    The list was recently migrated from Sharepoint 2007 - maybe something was affected there. I deleted the column, recreated it as a text field and entered the values again - worked ...

Wow - that's kind of interesting. What are the postback settings on the controls concerned? Have you tried adjusting those? I mean, because in order for the rule to fire on the textbox, the text has to have changed (which means, to the best of my understanding, the selected control will no longer be the textbox, but, in this scenario, the ...

Generally, the syntax of {number};#Text means the column is a lookup. Is the column the same type in all your lists? I'd probably put a rule on the field that is being set - that if the field itself (after being set) contains ";#", set it the substring after the # symbol. In a lot of cases, you can shoot yourself in the foot with ...

I did fix the item you mentioned. About half my code is based on some examples I've seen, and that is where it was inherited from. I did have some luck with the nested loops method, but either one is a toss up. I can submit all the items individually or together. Currently, with the code as it is above, I get the last ID field updated from ...

You made this easy - thanks! I updated your mapping for the task items to include the non repeating nodes from the corp events group. Your new mappings node now looks like this:   <my:Mappings>     <my:IsRepeating>true</my:IsRepeating>     ...

second mapping file

[quote user="Patrick Halstead"] Sorry, CopyTable requires an exact match. Insert isn't that hard to set up... let us know if you have any questions. [/quote]   Copy that.  Thanks.