InfoPath Dev

Unfortunately, you have to start the list form from scratch, from InfoPath, to turn this feature on. So, from InfoPath Designer, select the SharePoint List template, enter the URL, select your list and select the option to manage multiple items. That will get you the correct repeating schema....

I think you need to update your form compatibility to at least InfoPath 2010. When you try to save the form as 2010 or 2013, you should be prompted to update your data connections - which you should be able to do in the data connection window. To the best of my knowledge, FormsViewer doesn't support 2007 style SharePoint data connections.

Hmmm. I'm not sure of a way to work around this. Some controls just don't display correctly in email and it sounds like this is one. Maybe you could also include the form file with the email and just open the form that was sent?

If I recall correctly there isn't a way to "reset" a list form so it will submit another new item. The work around is to set up the form to submit multiple items, and then use some formatting & rules for setting the common fields all at once. Here is a thread that talks a bit about this approach: ...

Ick. You could try saving the form as source files and in the view file, adding a class to the elements you need to grab via JS to work around this - but I don't have an answer to your question, I'm afraid.....

As long as you are getting the data you need, sounds fine to me.

I would try creating a new data connection - modify the SQL to call the stored procedure, and just try the data connection as is (the new one) to see if data is returned to the form. Put the data fields from the new connection on the form so you can see if data is returned. Compare the schemas of the original data connection to the new one to see ...

I think this formula would be valid and may be what you are trying to achieve: substring(xdMath:Eval(xdMath:Eval(xdXDocument:GetDOM("LeadManagers")/dfs:myFields/dfs:dataFields/d:SharePointListItem_RW[contains(xdXDocument:get-DOM()/my:myFields/my:DocInfo/my:Matrix, d:Discipline2)], 'concat(d:GrantAccess/pc:Person/pc:AccountId, ...

Ok. I don't know the full XPath to either your secondary data source node or to your main data source node where you currently have the default value from the 2ds - but the code after you run the SQL query might be something like: XPathNavigator secDSNav = ...

Oh, I hope so, before this form kills us both. :)