InfoPath Dev

Hi all, and thinks Hilary for the support! Here is what I have learned in newbee terms: Query fields are for pulling information from your data source (particularly when you want to filter data).  Data fields can be used for both, pulling from and pushing data to your form. 

nope, no defaults... the problem has been resolved (somehow). I removed the data source from the 2nd dropdown and then re-bound the control to the Contact List again, and it's working now. Looks like rules have to be set first. Any thoughts on this account?

Rules don't fire when nodes are deleted. The On After Change event will - so you can catch it in code. You could also add a field outside of the repeating group (doesn't have to be on the form) that is set to the count of the repeating node and set to update when that changes - that would let you know a node had been deleted, but not which ...

 If you are trying to copy data from your secondary data connection into your main data source, I'm afraid InfoPath offers no out of the box way to do this. You are stuck with code (or non-dev friendly qRules).

 Sounds like you may have a default value for the Discipline field? In the data source task pane, right click the field and select properties to see....

 So - the InfoPath form submits to a library, but is a different beast than a list form, and doesn't have the same type of schema limitations. You can add a ton of data connections and drop down or list box controls (if that's what is meant by lookups here).

 Hi - out of the box, InfoPath is not going to let you set another list item from your list form. And since this is a list form, you can't add code or qRules to do this either. Are you using Office365? If not, you may be able to use the Lists web service and UpdateListItem method with a CAML query to do this.

 I think we'll need some additional information - Where is the error? It shows up in the logs? When they try to fill out the form? What version of SharePoint?

 I'm guessing that you had your cursor in a section bound to the query fields when you added the contact selector. You don't want it in the query fields. Your first screenshot shows a form with an editable schema - your second shows a form that appears to have been created from another data source - a web service maybe?

Interesting because in the method I suggested, the "key" field is set to value InfoPath "now()" function, which is roughly equivalent to what you were hoping to acheive by going to the seconds (datetime).  This key value is key (pun intended) to going back to retrieve the correct ID during the double-submit phase which ...