InfoPath Dev

Hi,

I have searched all over the web to try and find the solution to the repeating table form I am trying to build.

In a SharePoint list I have a template data table showing a build up of project milestones by category type.

In the header of my InfoPath form, users type in their project number which then automatically fills out the relevant fields linked to the project using a REST Web Service such as Region, Engineer etc.

Below that I have an expanding table (set so users can't add rows) which automatically loads the template (from the SharePoint list mentioned above) using a rule that says if category type in the header (main) is equal to category type (secondary) then it loads all the milestones associated with that project template type.

I then need 3 extra columns - estimated date, completed date and status which the users will complete themselves.

I will then need to get the project information and the milestone information into a third SharePoint list which will allow me to set up conditional formatting and workflows.

As I already have the rows pulling through from my secondary data source, my struggle is how can I get the extra rows added to the repeating table which when populated by the user saves the content?  Secondly, what do I then need to do to get all this parent/child data into a SharePoint list.

Thank you in anticipation of your help. 

 I'm a little confused, but it sounds like you want to add data to a SharePoint list from your InfoPath form? Is that correct? Unfortunately, InfoPath does not make this easy. You can write custom code for this, or you can use qRules, but it won't do it out of the box.

Thanks Hilary.  If we decide not to get the data into a SharePoint list, is the first part possible? i.e. the repeating table being populated from a data connection (which I already have working) with the ability to add in custom data and status fields to track progress?

Many thanks

 In order for data to be saved in the XML, you have to have the controls bound to fields in the main data source. Do you have a general idea of the max number of rows your secondary data source will return? If so, you could add that number of rows to a main data source table by default, and use default values to populate the info from the list, allowing the user to fill in their portion in the form. You may be able to find some examples of this technique on the Qdabra YouTube channel - we generally refer to this design pattern as being "data driven".