InfoPath Dev

Got it - yep, same thing happens on mine. So - here's what worked for me. On the rule on the repeating group (my:SharePointListItem_RW), add a condition to only run the rule if the DisplayName field is blank. I think when the form loads in the browser to edit, the rules on the repeating group are executing, setting the first instance to blank, ...

Wow - yeah, it does sound to me like this data collection may be better suited to SQL than SharePoint, just because of the mass of data. However, as a work around, maybe you could use a REST query? That would give you much better filtering options. Be sure to add indexes to your list / library columns to improve performance, and talk to your ...

 You'll either need to add conditional formatting to display only the row you want or instead of letting the data connection query on load, use rules to set a query field and run the query, so that the secondary data source has only the data you need.

 It sounds like perhaps your field binding is incorrect. Your screenshot doesn't show for me - can you attach it under the Options tab in a reply, or even better, attach a copy of your form?

 Maybe hide the submit button entirely & add a "check form" button that has postback enabled? That button can validate everything and then display the submit button if the form is ready to submit?

So - you are saying when you re-open an existing item to edit, the people picker appears blank? Or am I misunderstanding? I want to see if the same issue exists in my test form - for some reason I have a vague recollection of something similar with InfoPath Browser forms (not just list forms).

I think I would add a trigger to my SQL table to create the rows in the billing database table. InfoPath doesn't have a way for you to insert rows via rules, so you need code... But if you have access to the SQL tables, a trigger may do what you need.

Wonderful, that's half the battle. InfoPath got a lot easier to me when I started dragging my data sources onto the form where I could see them while I was doing my design work, by the way. Just make some room at the bottom of your form and put whatever you need on there to see what's going on - you can delete it all when you get ready to ...

Well, InfoPath doesn't have any built in way to filter the target of a rule. But we can do this with some helper fields. I added a helper to the repeating group & a form logic XML file to this version - take a look and let me know if you have any questions on the rules.

 Hi! So here's your form back with some changes - hopefully some of them are right, since I'm guessing a bit. On the Form Load & the Course Code field, I have added rules to query for the right course code for the data connection that the Quotas section is bound to. Since we are only querying for those that match on course code ...