I’m glad you find my blog useful!

Regarding flowed vs positioned subforms: To make a subform repeatable (such as the “continuation pages”), that subform must be inside a flowed subform. The “continuation page” subform itself doesn’t have to have flowed content (as you can see). Look at the subform that contains the “continuation page” subform: its content should be flowed.

Regarding removing pages: You are correct in thinking that setting a minimum count would prevent instanceManager.removeInstance() from working properly. I would suggest setting the minimum to zero and the initial and max counts to 1. That would give you an instance of each page from the start and removeInstance() should work just fine after that.

I have read several times now on your site that to make a subform repeatable, it must be Flowed. And that statement does not correspond to what I am seeing in the forms I am working with. I am fairly new to LiveCycle, so would greatly appreciate clarification.

I have inherited several forms that have continuation pages. These pages are full page subforms. We start out with a minimum of 1 continuation page, but make it hidden to start. The user then can “add” one continuation page, making the first continuation page visible. From that continuation page, the user can an additional pages, which creates and additional instance with the instanceManager.

This is working very well. However, the properties of the continuation page is Positioned, not flowed. So why is this working?

Another question: I have another form which has three pages for data entry and 12 subsequent pages which are basically text. We have buttons on the form to allow the user to delete any specific page, or a multiple group of pages (to save paper for printing purposes, I believe). The programmer before me accomplished this by making these “deleted” pages hidden, but there are a few problems with his code, and I thought I would fix the code by actually deleting the pages using instanceManager.removeInstance().

I want all 15 pages to appear when the user first opens the form, which would mean I have a minimum count per page of 1. However, as I understand it from your tutorials, that would prevent me from deleting the pages. Can I set a minimum count of 0, and add the pages when the form is first created? If not, do you have any other suggestions?

Thank you in advance for your help. Your site is awesome and I am so glad you are willing to share your knowledge and experience with us newbies.

Devra

This is certainly possible, but will require some script to make it work.

Setup your table as you described it. Then select the Row2 row and make it repeatable by checking its “Object palette > Binding tab > Repeat Row For Each Data Item property”. Since all instances of a repeatable row or subform are always kept in sequence (“together”), this will ensure that new instances of Row2 appear after the last instance of Row2 and before Row3.

Add the “Add Row” button beneath the table.

Select the table and set its “Object palette > Table > Allow Page Breaks Within Content” property.

Select the page subform (named “(untitled Subform) (page 1)” in the Hierarchy palette) and set its “Object palette > Subform tab > Content property” to “Flowed”. This, combined with the previous step, will ensure that the table isn’t cut-off at the bottom of the page (a new page will be generated instead) if you add enough rows to fill a page.

At this point, the table, followed by the AddRow button, should be at the top left corner of your form. Now for the scripts.

Select the AddRow button and use the Script Editor palette to set its Click event script (make sure you set the language to “JavaScript”):

// JavaScript:
// get the last instance of Row2 to copy values from
var previousRow = Table1.resolveNode("Row2[" + (Table1._Row2.count - 1) + "]");

// add a new Row2 instance
var newRow = Table1._Row2.addInstance(0);

// copy values from the previous instance
newRow.TextField1.rawValue = previousRow.TextField1.rawValue;
newRow.DateTimeField1.rawValue = previousRow.DateTimeField1.rawValue;

The script above will add a new instance of Row2 and copy values from the last instance that was added prior to that. (Note that the names of the fields which represent the text field and date time fields in Row2 may be different for you depending on how you created your table so make sure you use the right names.)

Now select the Delete button in Row2 and set its Click event script:

// JavaScript:
// delete this row only if there's more than one row left
if (Table1._Row2.count > 1)
    Table1._Row2.removeInstance(this.parent.index);

The script above will remove the instance of Row2 to which belongs the Delete button that was clicked.

It seems you have been able to help several people and since I”m about Googled out on trying to find a solution for my problem, I would try here.

I need a table that can have static rows and then dynamically Add Rows in between the static rows.

For example, a table with 3 columns and the structure would be the following (I hope this isn’t confusing):

Header
Row1 Col1 – A place holder for the rows Delete Button (this row doesn’t actually have a button though because they shouldn’t be able to delete it)
Row1 Col2 – A static text field
Row1 Col3 – A date/time field that the user can change
Row 2 Col1 – A Delete Button to delete the Row
Row 2 Col2 – An empty text field that the user can type in
Row2 Col3 – A date/time field that the user can change
Row3 Col1 – A place holder for the rows Delete Button (this row doesn’t actually have a button though because they shouldn’t be able to delete it)
Row3 Col2 – A static text field
Row3 Col3 – A date/time field that the user can change

And then underneath I have an Add button to Add a Row. I want the rows added between Row 1 and Row 3. So basically add a duplicate of Row 2, after Row 2. I couldn’t figure out how to add the duplicate row of Row 2 instead of Row 1.

I hope this makes sense. It’s a little hard to explain.
Thanks in advance for your help.

It sounds like you’re previewing as a Static (non-interactive) PDF rather than a Dynamic PDF.

The Instance Manager will only work in Dynamic PDFs. See this post on how to ensure you’re previewing as a Dynamic PDF.

Have you ever seen instanceManager not work at all. I started with a blank form and added a table just as the scripting refernce instructed and the button does nothing. I do not even get an error or something to point me in a direction.
form is dynamic, page is flowable, table with one header row, and dynamic body rows – used the assistant to create, added the script Table1._Row1….. with and without instanceManager … .addInstance(1);

nothing – the button clicks and that is it.

I have an older form that adds rows and it works inside designer. I tried copying that over into another form but nothing.

Any suggestions would be appreciated.

Perhaps you are running into the issue where your table is being “cut-off” at the bottom of your page (and might even be running over top your footer) instead of flowing onto the next page.

If you have 2 master pages just so that you can have 2 pages, that’s not necessary. A master page is simply the “background” to all the body pages. You can get fancy and create different master pages with different setups like multi-columns, headers, footers, etc., and have body form objects flow between various master pages but that sounds way more complex than what you’re trying to accomplish.

I would start by deleting the second master page.

Then, make sure your table is allows to break between pages by checking the “Object palette > Table tab > Allow page breaks within content”.

Finally, make sure your table is within a flowed container. This will ensure that anything below your table flows down nicely as you add rows.

As for your footer, make sure the content area object on the master page doesn’t overlap your footer, otherwise body content will flow over top of it. The content area object on the master page defines where body content can flow within the page.

The dynamic form portions of my MAX 2007 tutorial explain this in depth.

Thanks for letting me know how much my tutorial helped you out!

Adobe Reader proceeds to alternate between a “Bad Parameter” error and a “Software Failure” error. I’m not sure what’s happening.

I don’t recall ever seeing such an error. Can you isolate the line of script that seems to cause it? Perhaps you should try setting the number of instances to 0, the setting it to what it should be? That might make a difference.

Tables should be able to span pages provided you checked the “Allow page breaks within content” property on the “Object palette > Table tab”.

dataroot.MainPage.SF1.SiteObSF.Dk-SpFld::initialize – (JavaScript, client)
/* This listbox object will populate two columns with data from a data connection.

sDataConnectionName – name of the data connection to get the data from. Note the data connection will appear in the Data View.
sColHiddenValue - this is the hidden value column of the listbox. Specify the table column name used for populating.
sColDisplayText - this is the display text column of the listbox. Specify the table column name used for populating.

These variables must be assigned for this script to run correctly. Replace with the correct value.
*/

var sDataConnectionName = “< value &lt”; // example – var sDataConnectionName = “MyDataConnection”;
var sColHiddenValue = “< value <”; // example – var sColHiddenValue = “MyIndexValue”;
var sColDisplayText = “< value <”; // example – var sColDisplayText = “MyDescription”

// Search for sourceSet node which matchs the DataConnection name
var nIndex = 0;
while(xfa.sourceSet.nodes.item(nIndex).name != sDataConnectionName)
{
nIndex++;
}

var oDB = xfa.sourceSet.nodes.item(nIndex).clone(1);
oDB.open();
oDB.first();

// Search node with the class name “command”
var nDBIndex = 0;
while(oDB.nodes.item(nDBIndex).className != “command”)
{
nDBIndex++;
}

// Backup the original settings before assigning BOF and EOF to stay
var sBOFBackup = oDB.nodes.item(nDBIndex).query.recordSet.getAttribute(“bofAction”);
var sEOFBackup = oDB.nodes.item(nDBIndex).query.recordSet.getAttribute(“eofAction”);

oDB.nodes.item(nDBIndex).query.recordSet.setAttribute(“stayBOF”, “bofAction”);
oDB.nodes.item(nDBIndex).query.recordSet.setAttribute(“stayEOF”, “eofAction”);

// Clear the list
this.clearItems();

// Search for the record node with the matching Data Connection name
nIndex = 0;
while(xfa.record.nodes.item(nIndex).name != sDataConnectionName)
{
nIndex++;
}
var oRecord = xfa.record.nodes.item(nIndex);

// Find the value node
var oValueNode = null;
var oTextNode = null;
for(var nColIndex = 0; nColIndex < oRecord.nodes.length; nColIndex++)
{
if(oRecord.nodes.item(nColIndex).name == sColHiddenValue)
{
oValueNode = oRecord.nodes.item(nColIndex);
}
if(oRecord.nodes.item(nColIndex).name == sColDisplayText)
{
oTextNode = oRecord.nodes.item(nColIndex);
}
}

while(!oDB.isEOF())
{
this.addItem(oTextNode.value, oValueNode.value);
oDB.next();
}

// Restore the original settings
oDB.nodes.item(nDBIndex).query.recordSet.setAttribute(sBOFBackup, “bofAction”);
oDB.nodes.item(nDBIndex).query.recordSet.setAttribute(sEOFBackup, “eofAction”);

// Close connection
oDB.close();
dataroot.MainPage.SF1.SiteObSF.CatFld::initialize – (JavaScript, client)
/* This dropdown list object will populate two columns with data from a data connection.

sDataConnectionName – name of the data connection to get the data from. Note the data connection will appear in the Data View.
sColHiddenValue - this is the hidden value column of the dropdown. Specify the table column name used for populating.
sColDisplayText - this is the display text column of the dropdown. Specify the table column name used for populating.

These variables must be assigned for this script to run correctly. Replace < value < with the correct value.
*/

var sDataConnectionName = “< value <”; // example – var sDataConnectionName = “MyDataConnection”;
var sColHiddenValue = “< value <”; // example – var sColHiddenValue = “MyIndexValue”;
var sColDisplayText = “< value <”; // example – var sColDisplayText = “MyDescription”

// Search for sourceSet node which matchs the DataConnection name
var nIndex = 0;
while(xfa.sourceSet.nodes.item(nIndex).name != sDataConnectionName)
{
nIndex++;
}

var oDB = xfa.sourceSet.nodes.item(nIndex).clone(1);
oDB.open();
oDB.first();

// Search node with the class name “command”
var nDBIndex = 0;
while(oDB.nodes.item(nDBIndex).className != “command”)
{
nDBIndex++;
}

// Backup the original settings before assigning BOF and EOF to stay
var sBOFBackup = oDB.nodes.item(nDBIndex).query.recordSet.getAttribute(“bofAction”);
var sEOFBackup = oDB.nodes.item(nDBIndex).query.recordSet.getAttribute(“eofAction”);

oDB.nodes.item(nDBIndex).query.recordSet.setAttribute(“stayBOF”, “bofAction”);
oDB.nodes.item(nDBIndex).query.recordSet.setAttribute(“stayEOF”, “eofAction”);

// Clear the list
this.clearItems();

// Search for the record node with the matching Data Connection name
nIndex = 0;
while(xfa.record.nodes.item(nIndex).name != sDataConnectionName)
{
nIndex++;
}
var oRecord = xfa.record.nodes.item(nIndex);

// Find the value node
var oValueNode = null;
var oTextNode = null;
for(var nColIndex = 0; nColIndex < oRecord.nodes.length; nColIndex++)
{
if(oRecord.nodes.item(nColIndex).name == sColHiddenValue)
{
oValueNode = oRecord.nodes.item(nColIndex);
}
if(oRecord.nodes.item(nColIndex).name == sColDisplayText)
{
oTextNode = oRecord.nodes.item(nColIndex);
}
}

while(!oDB.isEOF())
{
this.addItem(oTextNode.value, oValueNode.value);
oDB.next();
}

// Restore the original settings
oDB.nodes.item(nDBIndex).query.recordSet.setAttribute(sBOFBackup, “bofAction”);
oDB.nodes.item(nDBIndex).query.recordSet.setAttribute(sEOFBackup, “eofAction”);

// Close connection
oDB.close();
dataroot.MainPage.SF1.SiteObSF.ObDesFld::initialize – (JavaScript, client)
/* This listbox object will populate two columns with data from a data connection.

sDataConnectionName – name of the data connection to get the data from. Note the data connection will appear in the Data View.
sColHiddenValue - this is the hidden value column of the listbox. Specify the table column name used for populating.
sColDisplayText - this is the display text column of the listbox. Specify the table column name used for populating.

These variables must be assigned for this script to run correctly. Replace < value < with the correct value.
*/

var sDataConnectionName = “< value <”; // example – var sDataConnectionName = “MyDataConnection”;
var sColHiddenValue = “< value <”; // example – var sColHiddenValue = “MyIndexValue”;
var sColDisplayText = “< value <”; // example – var sColDisplayText = “MyDescription”

// Search for sourceSet node which matchs the DataConnection name
var nIndex = 0;
while(xfa.sourceSet.nodes.item(nIndex).name != sDataConnectionName)
{
nIndex++;
}

var oDB = xfa.sourceSet.nodes.item(nIndex).clone(1);
oDB.open();
oDB.first();

// Search node with the class name “command”
var nDBIndex = 0;
while(oDB.nodes.item(nDBIndex).className != “command”)
{
nDBIndex++;
}

// Backup the original settings before assigning BOF and EOF to stay
var sBOFBackup = oDB.nodes.item(nDBIndex).query.recordSet.getAttribute(“bofAction”);
var sEOFBackup = oDB.nodes.item(nDBIndex).query.recordSet.getAttribute(“eofAction”);

oDB.nodes.item(nDBIndex).query.recordSet.setAttribute(“stayBOF”, “bofAction”);
oDB.nodes.item(nDBIndex).query.recordSet.setAttribute(“stayEOF”, “eofAction”);

// Clear the list
this.clearItems();

// Search for the record node with the matching Data Connection name
nIndex = 0;
while(xfa.record.nodes.item(nIndex).name != sDataConnectionName)
{
nIndex++;
}
var oRecord = xfa.record.nodes.item(nIndex);

// Find the value node
var oValueNode = null;
var oTextNode = null;
for(var nColIndex = 0; nColIndex < oRecord.nodes.length; nColIndex++)
{
if(oRecord.nodes.item(nColIndex).name == sColHiddenValue)
{
oValueNode = oRecord.nodes.item(nColIndex);
}
if(oRecord.nodes.item(nColIndex).name == sColDisplayText)
{
oTextNode = oRecord.nodes.item(nColIndex);
}
}

while(!oDB.isEOF())
{
this.addItem(oTextNode.value, oValueNode.value);
oDB.next();
}

// Restore the original settings
oDB.nodes.item(nDBIndex).query.recordSet.setAttribute(sBOFBackup, "bofAction");
oDB.nodes.item(nDBIndex).query.recordSet.setAttribute(sEOFBackup, "eofAction");

// Close connection
oDB.close();
dataroot.MainPage.SF1.SiteObSF.AddSubform::click – (JavaScript, client)
// nSubLength stores the number of XML elements contained in SF1.
var nSubLength = SF1.nodes.length;

// nNumSub is used to calculate the number of subform objects contained in SF1.
var nNumSub = 0;

// This script uses a For loop to cycle through all of the objects contained
// in SF1.
for (var nCount = 0; nCount < nSubLength; nCount ++) {

// If the current XML element in Subform1 is of type subform, then increment
// the variable nNumSub by one.
if (SiteObSF.nodes.item(nCount).className == "SiteObSF") {
nNumSub = nNumSub + 1;
}
}

// An if-else statement is used to prevent form authors from adding more than the
// maximum number of four subform instances to a form.
if (nNumSub == 4) {
xfa.host.messageBox("Click Add Page for more Descrepencies", "Attention", 3);
}
else {

// This script uses the addInstance() method to add a new instance of the
// SiteObSF object contained in SF1.
SF1.SiteObSF.instanceManager.addInstance(1);
}
xfa.form.recalculate(true)

dataroot.MainPage.SF1.SiteObSF.RemoveSubform::click – (JavaScript, client)
var nNumSub = 0;
var nSubLength = SF1.nodes.length;
SF1.SiteObSF.instanceManager.removeInstance(nNumSub);

I can email a copy of the form if you like.

Tim

Since you point-out that your form is setup using flowed containers, I’m going to assume the issue isn’t about the subform instance being “cut-off” at the bottom of Page1 but rather that it flows into another instance of the Page1 master page rather than flowing into a Page2 master page.

In this case, you need to specify where new instances of the repeatable deficiency subform should be placed once Page1 overflows. You can do this by selecting the deficiency subform and setting its “Object palette > Pagination tab > After property” to “Go To Page > Page2″.