InfoPath Dev

Hi,

I am using qrules 3.1

I am trying to copy some data from a secondary data source to the main datasource.  The secondary datasource is data from a SharePoint list.  All items in the List are populated (I have fallen foul of that before - many thanks to Hilary for putting me right.) 

I had this working.  But have subsequently been making changes to the form :(, and now I get the error message "Failed to add copied rows to destination table" when using copy table.  I need to try and understand what is causing this error.

The data structure of the tables is the same.

One change I have made is to allow one of the columns in the SharePoint List to have multiline text - but it is plain text, so it still gets downloaded to the form.

Could this have caused the failure ?  What other things could cause this error ?

Thank you

Catharine

Hi Catharine,

Could you attach a screenshot of the data sources involved and tell us where you're copying from and to?

Here is a screen shot of the data sources .... and the copy table command I am using is....

CopyTable /dsnamesrc=StatementsForSWP /tablesrc=/dfs:myFields/dfs:dataFields /rowsrc= dfs:Statements_for_SWP  /tabledest=/my:myFields /rowdest=my:StatementsGroup /empty=yes

It's very likely that the issue is that the StatementsGroup repeating group has another sibling node (PrintGroup) after it.  Ideally, a repeating group should have a parent all to itself, but that probably is not an option at this stage of your form development, so would it be possible to move the PrintGroup node above StatementsGroup or somewhere else, so that StatementsGroup is the last node under its parent?

Thank you for your advice. 

I have added another Group at the top level  and moved my StatmentsGroup into it.  I have also put that at the end of the data structure.  I have updated the copy table command and it is now working.

 Much appreciated.  I will try and remember for the future.

Catharine

Wow.  I wish I would have read this thread about an hour ago.  Would have saved an hour of hair pulling.

We cover data source design in our InfoPath Master Class. If you notice, InfoPath always adds repeating tables and sections within their own group. There is ambiguity with repeating groups that have siblings after them and a common parent. Another issue is with fields that are added as siblings. InfoPath xpath won't work correctly if the field has a sibling that is a repeating group above it. Easy fix is to move the field up.