Importing data into a 2nd form

The example name you give, i.e. "F[0].P1[0].EventDate[0]", is a LiveCyle form field name. Did you create this form in LiveCyle designer? If you did, then you've got a bit of a problem.

You have the right idea, giving fields in the different forms the same name, but with LiveCycle forms, the form hiearchy is part of the name. If the hiearchy of the two forms do not match, you can still make this work,

First, try simply exporting to XML from one form and then importing the XML into the other form. LiveCycle does some simple name mapping into the hierachy, so if your forms are simple enough and similar this may work. If this does not work you will need to add an extra step. Basically you need to map the form fields from the different forms in to the same name space.

There are several different ways to do this, but the easiest way is to create an XML gramar for your form data that will work for both forms. It should be as simple and straight forward as possible, and also match the generic format used by Acrobat when the unbound form is exported to XML. Make an example XML file that has fields in it for everything you need. Then use the "Data View" tab in LiveCycle Designer to connect both your forms to this example XML. Make sure all the relevant fields in both forms are "Bound" to the correct fields in the XML.

When this is done, you should be able to export data from one form to XML and import it into the other one.

I have the same thing...I am able to export data from one form and import it into a second form. On this second form though not all fields have dynamic binding..and this is where I am running into problems. The data is being imported into the right fields...but I need to export all the data from this form as well. It appears that the fields with dynamic binding is being exported. Why won't all the fields export there data.

LiveCyce forms have the annoying behavior of only exporting nodes in the data model, i.e., only field that are bound to the data model. You can change the binding dynamically, but this is a pain.

Another method is to use code to modify the data model before exporting data. but this is also a pain, and not always robust.

One way to have the appearance of different import and export binding is to use a set of hidden fields that parallel the unbound fields. These hidden fields are bound to the data model. Use code to copy data in and out of them to the non-bound visible fields.