InfoPath Dev

Or is it the works for future releases?

I'm afraid that feature has been punted to a future release at this point.

Do you recommend a workaround? 

I'm using Insert in a project I'm working on now that has a nested repeat. I have a field in a secondary data connection that I use to temporarily hold the position of the parent repeat, so that when I use insert I can use a filtered XPath to the parent.

I'll post a sample later today or tomorrow (injected with a trial version of qRules).

Great, thanks. 

The template is injected with a trial of qRules 3.3 that expires in Sept. but it uses commands that have been available for a long time...

The logic starts on the button - it sets a field in the Util file. That field runs the qRules command (just a personal pref - you could run it off the button) that inserts all the parent repeating table groups. Then there is logic on the parent repeating group and on the child repeating group for the rest of the process. I didn't ask how deeply you were nesting - this only goes two levels deep. I think it could be extended deeper, need be.

Finally, it is a demo form - my secondary data source doesn't have a ton of data in it. I'm not sure how you'll find performance with a larger qty of data, or how large your 2DS is. Also note that there's a chance the logic could be further refined, this was just a quick effort (after I realized the form I was talking about simply inserted into nested repeats, didn't copy data in).

OK, I'm going to have to absorb this one for awhile.  I think I'm starting to see what you have going on.  I moved the rules from the counter filed and applied them directly to the button.  When I click the button the first time, it inserts the table rows and copies the data.  When I click it the second time, it just inserts the rows, and does not populate any fields. 

Also, would it possible to count the 2DS table on a filter?  Count just the rows that contain text, for instance?

Also, my secondary data source isn't nested.  So does this apply?  My 2DS is a list on SP.  I would like to just copy that table into repeating sections.  I noticed your schemas matched. 

Can you define your requirements a bit more clearly? I didn't know your 2DS wasn't nested.

So, your scenario is:

2DS is not nested
2DS needs to be copied into main DS nested group

And you are asking about clicking the button multiple times - so how many times would be copying from your 2DS into your main DS? Or is it that you'll need XPath filters - when you do something, you want to copy only rows that match something else?

I'm happy to adapt the sample, just would like to know what the target is before I take aim again. :-}

Thanks for your time Hilary.  What I'm trying to accomplish might be too complicated (for me). 

I'm still trying to create a gear order form.  The gear that is being ordered can possibly be going to multiple venues, therefore I will need seperate instances of the gear list.  The number of instances depends on the number of venues for the order. 

The way I have it set up is -

Gear list 2DS on SharePoint. 

Gear list repeating table in my form that is nested in a repeating section.  User can add as many sections as needed depending on number of venues. 

I have a button that copies the table over into the form.  This works great for the first section.  But when I add a second section section and copy the table over again, it adds it to the first section. 

The reason I want to filter it, is the gear list is large.  I have a category selector that narrows down the list.  This works great by setting a query field on SP before copying the table. 

If all of this isn't possible, I will probably just have them save the gear to a list first, and copy that into a different table (Saved Gear).  But then I have the issue of which table the user works off of later.  They will be confused.  They always are.  I like the idea of repeating sections with the table, as each section will represent a venue.  It will look much cleaner. 

When you say "setting a query field on SP before copying the table" - does this mean that your 2DS has ONLY the items you wish to copy in it at a give time? Or do you need to filter the items that are to be copied?

I need to filter on a category field that exists in the list.  So I set the category query field in the list, and have it match a category drop-down that the user selects.  This drop-down also initiates the copy table. 

Another question . . . I am setting up the alternatvie method of submitting the table to a list and copying back into a "saved gear" table.  The table that I need to submit to the list is the repeating table nested in the repeating section.  I keep getting an "item does not exist" error.  Is this because the nested table issue?  I've checked over my id field and mapping 100 times, and it looks correct. 

Are you talking about SubmitToSharePointList command? That command does not work with nested data....are you trying to submit the nested table?

Yes, I was trying to do a SubmitToSharePointList with nested data. 

Basically, if I can't get the repeating tables in the repeating sections populated from my gear list (as per the topic of this thread), I was going to workaround the issue, by submitting to a secondary list, pulling it back into another table in my form (saved gear), and deleting the "add new gear" table, and copying the gear list back into it.  If I have to go this route, I will just have to convert my repeating section into a non-repeating section. 

I guess this nested stuff is nasty business.

Any other suggestions? 

 All I'm trying to do is get the same table replicated.  The user will go to the gear section, pick a category, pick a venue (from another part of the form), and fill out the gear.  Then when they need to pick a new venue, they will get a fresh new gear table to fill out per the venue needs.  I wanted to do the repeating table in a repeating section, because that will make it nice and clean, with visible headings on each section. 

If I copy it to another "saved gear" table, they are going to have to much stuff scattered all over the place. 

We've had a bit of email back and forth on this and it seems the best plan for you may be to flatten your data source. I'm attaching a new simple sample form that uses conditional formatting to display things in the "grouped" manner I think you are looking for, as well as a qRules SortTable command.

Give this sample a try, see if it looks like it might help you with a flatter data structure - then your copy table & list submit problems won't be issues any more, since your tables won't be nested....