Chris,

When working with the Instance Manager (IM), it’s important to note that this object controls the instances of its pertaining repeatable subform which currently exist at runtime.

When you add instances, you use the IM’s addInstance method and you must do the same when removing instances.

For example, if you had a simple form with a repeating subform and two buttons: an “add” and a “delete” button. These buttons are outside the repeatable subform named “RepSF” (they’re siblings to it). The “add” button’s Click event would have JavaScript like this:

_RepSF.addInstance(0);

and the “delete” button’s Click event would have script like this:

_RepSF.removeInstance(0);

Based on your question, I think you’re probably following me at this point. I think where you’re going wrong is you’re expecting to call “removeInstance(0);” on the actual instance of a repeatable subform, which you’ve renamed, in order to remove it.

Your attempt is definitely a logical one but it’s not quite how things work with the IM and since you need to make sure you only remove the instances that pertain to a specific policy number, you’ll need to use a different approach.

I would recommend you use a hidden field inside the repeatable subform. Let’s call it “PolicyNumber”. When you add a new instance of that subform, you would do this:

var oNew = _RepSF.addInstance(0);
oNew.PolicyNumber.rawValue = “123″;

Remember that the “addInstance” method returns a reference to the new instance so you can access the fields it contains just like you would a normal subform using that reference.

Later, when the user clicks on the delete button, you would do something like this:

for (var i = _RepSF.count; i >= 0; i–)
{
  var oInstance = this.parent.resolveNode(”RepSF[" + i + "]“);

  if (oInstance.PolicyNumber.rawValue == “123″)
    _RepSF.removeInstance(i);
}

Note that the loop reverses through the instances because we’re removing some. Removing instances while looping forward through the set will get you in trouble because the “count” property will change on you and you’ll end-up walking over the edge of the array pretty fast.

smvo,

1. I agree, being able to see the initial number of instances as defined by the min and/or initial properties at design-time would be very nice. Unfortunately, that’s not something that Designer is capable of doing at this time.
2. In order to properly reference instances of subforms (whether they’re “plain” repeating subforms or they’re repeating rows in a table), you shouldn’t use the “nodes.item” method (since it doesn’t only iterate through child nodes but also child elements which are properties of the node itself).

   To do this properly, you should use the resolveNode method on the container of the repeating subform like this:

   var oItem = ItemSet.resolveNode(”RepeatingItem[" + i + "]“);

   The above JavaScript code will return a reference to the ith instance of the “RepeatingItem” subform inside the “ItemSet” container (e.g. replace “i” with “2″ and you’ll get the 3rd instance since they’re zero-based).

Raul,

This sounds like a data binding issue with the “address” schema node to me.

I tried defining a little schema that had a repeating section named “invitedTown” with a nested complex section named “address” containing some more children. I was successful in creating a form with an “add” button that would let me add instances of the repeating subform representing the “invitedTown” node, enter some information, save the data, close the form, re-open the form and succesfully import the data I had previously saved. This would restore all data, including the data from the inner address section.

I would suggest dragging and dropping the “invitedTown” node from the Data View palette onto a form, looking at the way the bindings are setup and trying to replicate that in your form in case one of your data bindings for an “address.?” node isn’t properly setup.

Snehal,

It sounds like you might either be previewing or have saved your form as a static PDF form. In that case, you won’t see new instances appear but they’ll be added to the data which explains the discrepancy between what you’re seeing on the form and what you’re getting in the submitted XML data file.

I would recommend you check-out my article on previewing as dynamic PDF. It has tips on previewing and saving your form as a dynamic PDF form, which is what you’ll need to do in order to see the instances appear on your form in Acrobat.

Snehal,

For your first question, I think Designer’s Conditional Breaks feature might be able to solve this problem.

You can use it to specify that an instance of the “IMAGE FILLER SECTION” should be placed after each instance of a “Client” section without necessarily causing a break to a new page. Simply define a conditional break set to “after” (the Break property), “No Break, Just Leader & Trailer” (the To property) and with its Trailer property set to the “IMAGE FILLER SECTION” subform.

As for your second question, if you always want to show the “Total Info” section at the bottom of a new page, then all you need to do is place it at the bottom of its own page. Inserting instances of the other subforms in between will simply cause the page to automatically be pushed to the end. If, however, you want the section to always be placed at the bottom of an existing page, whatever page it may end-up on, that’s a different story which I don’t have an answer for.

Snehal,

A few days ago, I said I didn’t have an answer to your question about placing a particular subform at the bottom of the last page in a form.

I did a little investigating and it turns out that there’s a way to achieve this but it’s not perfect. New features being released in the next version of Designer will make this possible in the “correct” way but for now, we have to deal with what we’ve got in Designer 8.0 or earlier.

In order to demonstrate this and give you something to work with, I’ve posted a form which I believe resembles the type of form you’re trying to design.

First, run it in Acrobat (7.0.5 or later), enter 2 for the client count and notice where the blue “total” subform ends-up: At the bottom of the first (and only page). That’s not difficult to do. Now, enter 3 as the client count and notice what happens: The first page isn’t quite long enough to fit the last “image filler section” so it overflows onto the next page and the “total” subform ends-up at the bottom of the second (last) page.

If you check it out in Designer (7.1 or later), you’ll be able to see how it works:

• The Master Page named “Page1″ contains two content areas which define where content (the subforms) will flow when the number of instances of the “client info” subform is modified.
• The root subform (named “form1″ at the top of the Hierarchy palette) has a conditional break and an node set on it which specifies that its content should flow into the first content area named “ClientInfoCA”. Unfortunately, I had to specify these manually in the XML Source view since Designer doesn’t let you edit properties of the root subform in its palettes.
• The “ClientInfoSF” subform also has a conditional break to specify that the “ImageFillerSF” subform should be placed immediately after every instance of the ClientInfoSF subform. This ensures that the image filler section always appears after every client info section.
• The “TotalSF” subform has a conditional break which specifies that it should break to the “TotalCA” content area before it’s rendered on the form (which means it’ll always show-up in that content area which is located at the bottom of the page).
• Because the “TotalSF” subform is last in document order (or at the bottom of the hierarchy tree), Acrobat will only attempt to render it once it has finished rendering all prior instances of the “GeneralInfoSF”, “ClientInfoSF” and “ImageFillerSF” subforms, which means that it’ll only show-up once and it’ll always be at the bottom of the last page.

The only draw-back to this design is that the two content areas can’t overlap or else the subforms may overlap in the rendered form. This means that you get an empty section at the bottom of every page before the last one where the “TotalCA” content area is located.

If the “TotalCA” content area in your form is small enough, then this might be a viable option for you (the amount of blank space at the bottom of all pages prior to the last one might be negligible).

I realize it’s a very complicated concept to explain in a comment on a blog so please don’t hesitate to ask more questions if there’s something you don’t understand.

Hi Stefan,
I have a form where users can add subforms by clicking a “add_subform” button. when the subforms are added they are given subform numbers in increasing order.
Each subform has a delete button which when pressed should delete the subform and re-order the subform numbers.
how can i delete the subforms at runtime.
what parameter is to be passed to the removeInstance(int) at runtime.

Stefan,

Scripting and instance manager are totally new to me, so any assistance would be greatly appreciated.

Question on referencing instances. I have a 2 page form. The first page is a summary table and the second page provides details. So, I have it that I can add (and remove) instances on the summary table. This correspondingly adds pages to the document. Ideally, the way this should work is that the user adds a row in the summary, enters some summary information in the instance that is created and when he/she goes to the corresponding details page, the summary information has auto populated on that page as well (making it easy to find). For example, the first row of the summary table has an Item labelled #1, and in the detail pages, there is a page with a field that has #1 in it as well. So, there is a 1 to 1 relationship between the summary row and a details page.

Now the question is, how do I push the data in the fields from the summary table instance to the fields in the corresponding details page instance? I can’t figure out how to find and reference the fields in each instance of the subforms so that I can get them to equal each other.

Thanks in advance for any insights to can provide!

Hi Stefan,

Thanks for the help on this, it is greatly appreciated! Please pardon my lack of knowledge on this subject matter and my (probably) very basic questions. I’ve followed what you have advised above - I’ve created a script object (InstanceCnt) within which I have declared the following:

var oDetailPageRef = null;

In my “add instance” button, I have added the following code:

InstanceCnt.oDetailPageRef = _page2.addInstance(0);

To double check that the oDetailPageRef variable is getting populated, I outputted the variable value to the console and got the following:

[object XFAObject] (Which I assume is correct).

Now, just to show my lack of experience and knowledge, I’m stuck at how to reference the variable to populate the fields (referencing things seems to be my nemesis). You state in your previous answer that “each field would have a script on its Exit event which would refer to the variable in the script object and use it to access the pertaining fields in the detail page it references in order to set values…”.

As a result, I’ve tried to reference the variable a number of ways and keep getting an error stating that what I have referenced has no properties. So, I’m guessing that I am not correctly referencing the variable and associated field in the details page in order to set its value to the corresponding field in the summary table. What is the proper syntax to accomplish this?

Thanks again for the help!

MK,

It looks like you’re off to a good start. Before we takle synchronization between the summary rows and detail pages, let’s concentrate on getting the detail pages populated with the summary rows (one way).

What I’m thinking is that each field in the summary row would have JavaScript like this on their Exit events (which get executed when the focus leaves the field — when you tab out or hit the Enter key):

InstanceCnt.oDetailPageRef.{FieldName}.rawValue = this.rawValue;

where {FieldName} is the name of the field within the detail page whose value should get the same value as the field into which the user has entered a value.

Let me know how you do with this. Hopefully it works and we can proceed to the synchronization.

MK,

Could you re-post your last comment? Some of your script got cut-off and I’m having difficulties understanding exactly what you’re trying to do without proper context.

Stefan,

I thought it may not have gone through - below is my submission:

Thanks again - this site is great! Okay, in the interim, I started playing around with some advice you had given another user, along with the advice you’ve given me. In the process I noticed something wierd - Acrobat gives me the “no properties” error when I reference (just as you showed above) the variable if I am referencing off of the container that has “Flow Content” (i.e., page 2). However, if I put a subform on page 2 of the same size as the margins, put my content there, and have that subform called by the instance manager - the referencing works beautifully. I’m not sure I explained that correctly - so let me show you my code:

1. I added a field asking for how many instances I want (TextField1)
2. On that field’s exit, I put the following code:

var j = TextField1.rawValue
_summary.setInstances(j)
page2._Details.setInstances(j) // you’ll note that I’m not increasing the number of instances for page 2, but for a subform in page 2
for (var i = 0; i

MK,

Unfortunately, it didn’t go through again. I think the problem is the < bracket in your “for” loop statement. Try changing the angle bracket to “&lt” (and other instances if they exist), then post your comment. That’ll prevent my submission form from thinking the angle bracket is the start of HTML mark-up.

Sorry about that! Hopefully it’ll work next time…

Stefan,

Thanks a lot for the info it help a whole lot. I have one more question thought, how would I add a button that would remove the last subform, like say a member accidentally clicked the button and didn’t need to.

Thanks

Thanks a lot Stefan! It makes sense and works perfectly.

Hi Stefan,

I ran into another problem along the way. The code you gave me to build a dynamic header row worked perfectly, but when I try to add a new row I run into trouble. I can get as far as adding the actual row itself, but I can’t seem to add an instance of the cell inside the new row. So for example, the following will build both the header row and row 1 just fine:

var myColumns = “Col0Name,Col1Name,Col2Name,Col3Name,Col4Name”;
var arrMyColumns = myColumns.split(”,”);

for (i = 0; i &lt arrMyColumns.length; i++)
{
//Create a New Column
var oNewCol = Table1.HeaderRow._Col3SF.addInstance(0);
oNewCol.ColNameTxt.rawValue = arrMyColumns[i];

Table1.Row1._Col3SF.addInstance(0);
}

When I try to build the second row, though, it looks like one long row with no individual columns. I can build the third row with the following code:

Table1.Row1.instanceManager.addInstance(0);
or
Table1.Row1._ColSF.instanceManager.addInstance(0);

When I try to split that row up (like how the header and row are divided), I run into problems. If I try

Table1.Row1._Col3SF.addInstance(0);

I just end up adding another column to the table. So my question is, “How do start adding cells in row 2 to start making a complete row?”

Thanks a lot,
Brent

Stefan,

You’re a genius! I’ve been struggling with this for the past few days, and I can’t believe how simple you made it. Anyway, the code works great. Thank you so much for your help.

Toylar,

Sounds interesting. What I can suggest is that you use the xfa.layout.page method to determine which instances of the subform are on specific pages. Using the xfa.layout.pageCount method, you can determine the number of pages in the entire form. If you combine the two, and make use of the subform’s Instance Manager’s count property, you might be able to achieve what you’re trying to do.

For example, it might look something like this in JavaScript (note that I have not tested this script so I cannot guarantee that it will work):

var nTxtPage = xfa.layout.page(this); // 1-based page index of page that contains "this" instance of the text field
var nSFCount = _ParaSubform.count; // number of instances of the repeating paragraph subform throughout the form

var sFirstParaNumber = null;
var nLastParaSFOnPage = -1; // index of last instance of paragraph subform on same page as text field instance

for (var i = 0; i < nSFCount; i++)
{
    var oSF = this.parent.resolveNode("ParaSubform[" + i + "]"); // get a reference to the i'th instance of the paragraph subform
    var nSFPage = xfa.layout.page(oSF); // page number of the instance

    if (nSFPage == nTxtPage)
    {
        if (sFirstParaNumber == null)
            sFirstParaNumber = oSF.ParaNumberField.rawValue; // get first paragraph number (but not subsequent paragraph numbers)

        nLastParaSFOnPage = i; // remember index of last paragraph (instance of the repeating subform) on page
    }
}

if (sFirstParaNumber == null)
    this.rawValue = "there are no paragraphs on this page";
else
{
    var oLastParaSF = this.parent.resolveNode("ParaSubform[" + nLastParaSFOnPage + "]");

    // set text field value to "Paragraph X through Y" using first paragraph number found in FOR loop and
    //  paragraph number from last instance of paragraph subform on same page
    this.rawValue = "Paragraph " + sFirstParaNumber + " through " + oLastParaSF.ParaNumberField.rawValue;
}

This script should be placed in the text field’s Layout:Ready event so that the “this” keyboard refers to a particular instance of the text field (assuming there’s one per page in the form, according to your description). You should be aware that the Layout:Ready event is fired every time something causes the form to need re-rendering which means it may fire very often. You might need to use a boolean variable to guard against executing it too often. Also, this script assumes that the repeating paragraph subform and text field objects are in the same scope. Otherwise, you’ll need to add the necessary SOM paths to access the paragraph subform from the scope of the text field.

Please let me know if it helps!

Adobe LiveCycle Designer 8

Basically it is a list of several entries, each row with a minus-sign to remove the row and a plus-sign to insert a row AFTER the row the plus was pressed at.

The minus works fine and as long as rows are added by addInstance at the bottom the plus is also fine.

The problem starts when inserting rows somewhere in the middle. I tried this with insertInstance and addInstance+moveInstance and everytime an instance gets added, but the content of all the other rows gets cleared (and also in another flowing subform with instances to add and remove).

At time the code looks like this:

r = Allgemein.Seite1.Mitversicherte.Liste.Eintrag.instanceManager.count;
s = this.parent.index;
Allgemein.Seite1.Mitversicherte.Liste.Eintrag.instanceManager.addInstance(false);
Allgemein.Seite1.Mitversicherte.Liste.Eintrag.instanceManager.moveInstance((r-2), s);

I have no idea, why all the other fields get cleared. Do you have an idea?

I have looked endlessly on the web and cannot find an answer to this question. I know I must be overlooking something.

I essentially have a line item subform. It is nothing too complicated. The only interesting thing is that I import the products, units, unit prices, etc. from a pre-made xml.

Well everything goes smoothly. I import the price list, add the necessary lines for each line item to be added, I total up the price correctly, I even delete erroneous line items well.
But if the users saves the form and reopens it, all instances except for the first one are gone. I’m bashing my head because it seems like this is a simple fix but I have checked every property and it all seems correct.

Please advise. By the way, best livecycle resource. I wouldn’t have gotten the form this far without this blog.

Adam Frey,

Thank you for the compliments. I’m glad you find my blog useful!

Normally, when you’re using straight data binding, any data that you import into the form will be saved when you save it in Acrobat (or Reader if the form has been Reader-Extended).

If you’re using script to add/remove instance of your line item subform and you’re processing the XML data manually, then this could explain what’s happening. What you need to do is either add more script to figure-out if you need to re-initialize the form to the previous state (but then I suppose this implies you stored the imported XML as data in a hidden field somewhere in the form) or you could try using the “Preserve scripting changes to form when saved > Automatically” option in the “File > Form Properties > Defaults” dialog (available at least in Designer 8.1, perhaps in 8.0).

Mark J,

I’m afraid I can’t tell what could be happening based on your explanations. I would need a little more detail about your form. For instance, is the table inside a series of flowed subforms all the way up to the root subform? Are the headers grouped together as a table section? What do you mean by “none of the header rows appear like they do on the 2nd page”?

Mark J,

Sorry for the delay. We’ve been heads-down lately working on some code.

You’ve provided a very good explanation of your form and I was able to replicate the issue you’re having. It looks like you’ve uncovered a bug where if the object being used as an overflow leader (which is what the table “header” section becomes with respect to the table when you choose to have the section repeat on subsequent pages) has flowed content (in this case, two header rows are flowed within the table section), the rows end-up positioned on top of one another on subsequent pages. It’s strange that it only happens after the second page for tables but I think the underlying issue is the same.

My only suggestion at this point is that you replace the section and two header rows with a single row, make all cells span the 13 columns, make the cell into a single subform with positioned content, make that row the height of two rows and insert the necessary form objects to get your table title, column titles and button into it. Then mark that single row as a header row and see if it will repeat correctly on all pages.

As for the bug, I will definitely report it so that it gets fixed in a future release. Thanks!

I don’t know where to write about my problem, so I will try here. I have a repeating subform, with dynamic captions, for both romanian and english language. The problem is, that when the second instance of the subform is generated, the captions are not loaded from the XML file that has them, but they present the text that was entered in designer when the form was first drawn. Can you help me? Thank you!

Stefan,

Your blog is a great resource and has helped me tremendously to create a working dynamic form. Could you please help with a problem I have with a repeating subform using instance manager.

I have a form with two master pages (’portrait’ and ‘landscape’). the majority of the form is laid out as ‘portrait’. On these pages the instance manager works just great to repeat subforms.

I have one dynamic subform on the ‘landscape’ master page. After this subform, the remainder of the form is set up on ‘portrait’ master pages.

So, here’s the problem: when I use the instance manager and repeat the ‘landscape’ subform (which then overflows to another page), the subform is generated on a ‘portrait’ page, instead of a ‘landscape’ page.

In the pagination for this repeating ‘landscape’ subform, I have the “Overflow” set to “Go to Page’landscape’” . However, when I test the form, it still generates the subform onto a ‘portrait’ page. I have tried many combinations of pagination settings and none have produced the desired outcome: the subform repeated onto a ‘landscape’ master page.

I am new to livecycle. Is there something here I am overlooking? Any help would be greatly appreciated

Stefan,

Thank you for responding so quickly. I don’t think I expressed my problem clearly. I have the pages configured as you suggest (on body pages, with master pages assigned using the pagination tab). It seems the problem lies with switching between ‘portrait’ and ‘landscape’ then switching back to ‘portrait’. The form works well when I place the ‘landscape’ body page at the end of the form (so it’s the last page). However, when the ‘landscape’ body page is sandwiched between two ‘portrait’ pages, a ‘portrait’ body page is generated for overflow, regardless of the configuration on the pagination tab.

Here’s the simplified hierarchy of my form (this arrangement always generates a ‘portrait’ page, despite the pagination overflow being set to ‘landscape’):

-Master pages
-portrait
-landscape
-subform1(flowed)
-Body page1 (pagination=portrait)
-subform2(flowed)(repeated)
-Body page2 (pagination=landscape;overflow=landscape)
-subform3(flowed)
-body page3(pagination=portrait)

However, when I rearrange the hierarchy as follows, the form works properly (i.e. a landscape page is generated for overflow):
-Master pages
-portrait
-landscape
-subform1(flowed)
-Body page1 (pagination=portrait)
-subform3(flowed)
-body page3(pagination=portrait)
-subform2(flowed)(repeated)
-Body page2 (pagination=landscape;overflow=landscape)

I have found another post on a forum suggesting that this is a bug. However, I cannot find confirmation (or a fix) if this is the case.

Stefan, you may be my last hope. Livecycle is new to me and I’ve been learning a lot in a short amount of time. I’ve exhausted my search online for help and I have come to you as a last resort. What I want to do seems so easy, but I’m having trouble repeating row data from one row to the next.

I have a repeatable form that a user will fill out. I am able to add/delete a new row w/o a problem. Some of the fields in the rows will stay the same. I am trying to creat an instance of a new row, capture the data from one field (lglIdentity[0]) and paste it in the next (lglIdentity[1]) and so on and so on. here is my code:

details being my table name, detail being my row name and lglIdentity being the cell to copy and past to the next row.

var lglIdentity
lglIdentity = details.resolveNode(”detail”).lglIdentity.rawValue;
xfa.host.messageBox(”legal is: ” + lglIdentity, “Debugging”, 3) //this captures the object just fine

var inst = details._detail.addInstance(1);

var lglIdentity1
lglIdentity1 = details.resolveNode(”detail[1]“).lglIdentity[1].rawValue;
inst.lglIdentity1.value = lglIdentity

This is only half the problem though. Eventually I will need to copy this data to multiple rows, depending on the number of rows. I’m assuming I’ll need some kind of loop, is that correct. How do I go about this all? I’m at a dead end right now.

Is there something here I am overlooking? Any help would be greatly appreciated, thank you.

troy seiler,

I understand what you’re seeing looks like a bug but I can’t exactly pin-point whether it is or not. I am wondering, however, why you’ve structured your form as you have. Why did you put page subforms inside other subforms, as in

subform1
    body page 1

I would try removing those body pages and just using the subform1, subform2 and subform3 subforms (which I believe are parented to the root subform given the hierarchy you listed). You can make subform2 repeatable just like you could “body page 2″. Then set your pagination on the subforms and see if that fixes the issue. I have a feeling that the layout engine is getting confused on which master page should be used for the following subform (i.e. it finishes rendering “body page 2″ with the landscape master page and then renders subform3 — which likely uses “following previous” as its pagination — and puts it onto the landscape master page even though the subform inside subform3 says that it should go on the portrait master page).

Stefan,

I see your point. I believe I tried what you are suggesting, with the same results. But, I will play around with the hierarchy as you suggest and see if I can get this to work. Thanks for your input.

Just to explain. . . and I apologize for making you pull the complete story out of me piece by piece. . .

The reason I have the subform within a subform hierarchy is that I have designed the form with the ability to repeat a group of several pages AND to individually repeat a single page within the larger group. It is a very large form, and basically, I found it slightly easier to work with using the current hierarchy.

-Troy

Jeff Maughan,

First, the calculation should be inside a Calculate event on the field that needs to show this percentage value.

Second, you’ve scripted your calculation in such a way that you’re circumventing XFA in order to get field value. I believe this is bypassing the Calculation Engine which means it won’t be able to establish dependencies on this field to other fields such that when their values change, this calculation is run again.

Try it like this (where you access field values from within XFA):

if ((Provident_YSP.rawValue + Check_Total.rawValue - AppraisalrawValue) * 0.2 > 450)
    Superior_Lending_File_Fee.rawValue = 450;
else
    ...

where the pattern of

this.getField("FieldName").value

becomes

FieldName.rawValue

Stephan,

Thanks for the great blog i have found many useful solution to issues and found it to be a great resource for my education in form design.

I’ve be challenged with something that i though would be an easy solution but cant for the life of my figure this one out. My employer has asked me to create a radio button set at the top of a form that repeats on to each page but each repeat must retain the value of first radio button set. I put the radio button set on the master page and repeats as expected but doesn’t retain any of the values from the first set on the new page. I’m thinking i should have put the radio button set in a subform and used the instancemanger to copy the previous set while maintaining the same values if that is possible. I would appreciate any incite into this that you could offer a rookie. :)

thanks,

Mark

Hi Stephan - I’ve found your blog very helpful. Thank you! You seem to be very willing to help, so I’m gonna ask … I can’t get my dynamic form and instancemanager to work.
Here is what my form looks like:
PurchaseAuthorizationForm
>(Master Pages)
>page1 (flowed subform)
>>PrintButton
>>Title (positioned subform)
>>AuthorizationAgreement (flowed subform)
>>>items (flowed subform)
>>>>item (positioned subform, on Binding tab the ‘Repeat Subform’ is checked)
>>>>>2 text fields (that I want to repeat)
>>>>addAnotherItem (flowed subform)
>>>>>btnAdd (the button that runs: xfa.PurchaseAuthorizationForm.page1.AuthorizationAgreement.items.item.instanceManager.addInstance(true);)
rest of the form is incomplete

What I want to happen: when user clicks the btnAdd, the item subform and it’s two text fields are repeated.

What am I missing?!?!?!?! This is driving me crazy. I’m using the Allegiance multiBeneficiary sample as an example with no luck.

THANKS!

Stefan,

Great to see your site, you are really helpful!

I have a growing table, user can press Add button to add rows while each row can have different height (the cells allow multiple line) just depends on what they input.
What I wanna get is the whole table’s height, (I cannot get the height for flowed subform). So instead I decide to add up all the rows’ height for that.

Although I can get the total row counts for it:
var oRow1 = xfa.resolveNode(”Subform1.Table1.Row1″);
rowcount = oRow1.instanceManager.count;

I have problems referencing each instance row’s cell
(suppose the body row consists of a Name and Address field):
I think somehow the code should look like:
oRow1.Name[0].h (for row 1)

Thanks a lot.

Stefan,

Thanks for your reply, I can finally handle it.

Yet there is another problem I encounter now.
My form is a dynamic one with data flowing. After filling the form, it has to be rendered such that a new layout comes out for printing.

It is ok if I separate these actions:

0) Originally the first original page is displayed for filling data. Data may span on next page. While pages used for rendering a new layout will be hidden at the beginning.

1) There is a Preview button on the first of original page(s), and on click, scripts will run to hide the original page(s) while the new rendered page(s) become visible.

2) On the rendered pages (read only), there is a Print button for printing which simply codes:
xfa.host.print(1, “0″, (xfa.host.numPages -1).toString(), 0, 0, 0, 0, 0);

3) There is also a Preview Close button so that on click, the fields of the rendered pages will be cleared and hidden, while the original pages will reappear again.

However when I intend to use a Print button to combine all above steps (Print Preview -> Print -> Close Preview) in one script, when the print dialog comes out, it just display a blank page for printing.
It seems that xfa.host.print occurs not on the right time.

Any idea?

Hilary,

It could be a delay in the rendering of the pages for print as a result of your “print preview” script. You could try forcing a re-layout of the form just before you issue the xfa.host.print call:

xfa.layout.relayout();

The relayout() call should be blocking and should take place immediately which means that by the time your script executes the print() call, the pages should be rendered.

If that doesn’t work, try having your button no do the “close preview” step to see if you can print what you want. If that works, then it’s the xfa.host.print command that is asynchronous and executes only after the script has finished executing, at which point your “close preview” step has removed all of the pages meant to be printed…