InfoPath Dev

I am looking to Insert two repeat sections from infopath in one SharePoint list.... where the first repeat section is based in account own by the requestor and the second repeat section is when the requestor is doing backup time for some one else where need to log the amount of time that spend in the peer account. Let me know how much pain full is going to be or not.. –Q1: Is possible to do this ? With codeless or not –Q2:What steps I need to do to accomplish this? or just provide a basic guide if this can be feasible or not... Attaching picture of what I am looking to get

Hi perezcotaiza,

Were you pertaining to a repeating table? If so, then yes this is possible without code, however this approach will have blank rows, require default data (not good for large tables), require ID fields, etc.. See attached form for a sample (download XSN > right click > open in design mode). If you wish to avoid code, you might want to check out qRules. It has a Copy Table, Move Table, and Insert row command (and lots more). Hope this helps.

Could you provide more details about how complicate is going to be ? * the part that I am worry about is that you said "not good for large tables" And I am looking to deploy a lot of records in the SharePoint list ,then push that data to SQL server. I am looking to compare the advantage to use Qrules

Hi perezcotaiza,

With the approach I have provided you with, the target rows where items will be inserted where already inserted. If you will be working with hundreds or thousands of data, using a codeless approach is not feasible since you will be generating a lot of blank rows.

You may want to check Jimmy's guide on how to add rows to repeating sections:

http://www.infopathdev.com/blogs/jimmy/archive/2009/03/06/automatically-adding-rows-to-repeating-sections.aspx

Using qRules on the other hand allows you to manipulate data without writing code. Using simple commands such as CopyTable, MoveTable, and Insert command along with the set value copy technique on the form I provided you with is a lot easier. Using the insert command lets you insert a row without worrying about blank rows (data).

I hope this helps.

Hi Donstephen, Understanding your suggestion... Do you mean that first empty row come when the user is submitting data in the repeating table ? Do you have some real cases that can demonstrate the Qrules can allow to maintain easily this type of project and accelerate the time of development? regards, Cristina P.