InfoPath Dev

Good day

I’m developing a form that has a repeating table in a repeating section. I was hoping to use qrules to populate the repeating table from a filtered SharePoint list (the filter will be in the repeating section). I can get the first repeating table to populate but not subsequent repeating tables in the repeating sections.

Anyone know of any syntax to use with qrules to get data copied to a repeating table in a repeating section without code?

I found this post which I think is close to what I’m after…
http://www.infopathdev.com/forums/p/12405/43578.aspx#43578

Given that my button/filter is inside the repeating section, can preceding-sibling be used and if so how?

This I my current syntax. I'm thinking something around the /rowdest=my:Tests should be changed...
CopyTable /dsnamesrc=Tests /tablesrc=/dfs:myFields/dfs:dataFields /rowsrc=dfs:Tests /tabledest=my:myFields/my:Products /rowdest=my:Tests /empty=yes

Any help appreciated.

Hi Jonathan,

Could you post a screenshot of your source and destination data sources?

Thanks!

Hi Ernesto

I've attached a zip containing 3 images showing the data connection/form layout, rule to update the data and the previewed form.

I'm not a developer which is why I was hoping qRules and an as yet unknown to me syntax may help in populating the repeating table in the repeating section.

Thanks

 Thanks for the screenshots. You can drag the error node into the view to temporarily debug the issue. Can you do this and let us know the error that is getting returned in that node? Thanks!

I get the error "An error has occurred executing the rule. Failed to select the source node." when I use the Replace command.

When I use copy I get "An error has occurred executing the rule. Invalid command specified: Copy". Using both commands the data loads into the first repeating table.

I placed the error node outside the repeating section but it generates the same error inside the repeating section.

 Any ideas?

 The command you want to use is called CopyTable, not Copy. Can you try using that command and let us know the result? Thanks.

Hi Ernesto

Sorry about that. I've tried many different approches in an attempt to get it working.

When I use the CopyTable command I do not get an error message. I have however noticed that when I set /empty=no and I add repeating section, it copied entries to the first repeating table.

CopyTable /dsnamesrc=Tests /tablesrc=/dfs:myFields/dfs:dataFields /rowsrc=dfs:Tests /tabledest=my:myFields/my:Products /rowdest=my:Tests /empty=no

Hope this helps!

Thanks

 

Hi Jonathan,

I think we've made some progress, but I'm afraid I don't understand the current issue. You mention that no error is returned and that a copy operation is taking place. If the issue is that the operation is appending data, simply change the command to /empty=yes in order to clear the table before copying. If I misunderstood the issue, let me know and I'll try to address the question again.

Thanks.

Hi Ernesto

I have attached a test form that will hopefully explain my issue better than me! Data is preloaded into the form so you shouldn't need a connection to the server to see the results.

The scenario is that I need a form that is capable of having prefilled tasks in repeating sections. The tasks are going to be broken into sets that will need to load when a user selects a particular product. The way I was approaching this is to load all the tasks into a SharePoint list (for easy business user management) with a product column. When a product is selected in a repeating section, the tasks are displayed in the repeating table. This works OK for the first table but not others....

I may be going about this in the wrong way (I realise that filtering rows base on the product is not ideal) but the approach seems logical to me!!!

Thanks

Hi Jonathan,

After investigating, CopyTable will not work in this scenario. We will consider this idea for a future enhancement (i.e. specifying a position parameter that allows the user to specify where they want the new table inserted).

Thanks for the information. Saves me pulling my hair out!

Cheers

ErnestoM:

We will consider this idea for a future enhancement (i.e. specifying a position parameter that allows the user to specify where they want the new table inserted).

I understand that this post is 2 years old. Any idea when this feature (specifying a position parameter that allows the user to specify where they want the new table inserted) will be introduced in qRules? Thanks!

It has been two years, hasn't it! Time flies....

I'm hoping to get it in for the next release (4.2, coming June 15, 2012). There's another CopyTable change I'm hoping to implement this release as well.

Until then, I'm afraid you'll need to Insert and copy.... or, if you are comfortable with XSL, I'm turning into a huge fan of the Transform command.....

Instead of adding a position parameter, I added one called xpathdest - like xpathsrc in the Insert command, it allows you to use filters - in this case, the xpathdest would be the full path to the destination row, and used when there are filters on the /tabledest param - like in the case of the initial poster, where his repeating table was inside a repeating group. We'll see how it fares through testing. :-)

Thank you for the inputs, Hilary. I took a different route and found a different solution to my problem. As the solution is not relevant to what has been discussed above, I am not posting it here.