Stefan Cameron on Forms
Building intelligent forms using Adobe LiveCycle Designer

Bug List

The following table outlines bugs that have been found either in Designer (on any topic) or Acrobat (related to XFA/PDF forms). Please keep in mind that I’m providing this list and maintaining it for information purposes only. Whether a known bug gets fixed or not in a future release is something I cannot promise nor comment on. I will, however, make as much information available about the status of each bug as possible. Hopefully this will help you to determine if the brick wall you’re banging your head against is really a brick wall or not and whether there’s a work-around you can use in the interim.

Bug App Ver Fix
Cannot Override Calculations A/R 7.x 8.0
“Page n of m” Custom Object Broken in Tables Des 7.1
Image Field Z-Order Problems A/R 7.x 9.1
Adding/Removing Table Columns A/R 7.05+ 8.0
Unable to Set Caption or Value Font Separately Des 7.0 7.1
Images not always embedded into PDFs A/R 8.0 8.1
Sending WSDL request using repeatable section A/R 8.0 8.1
Web service data not cleared on exception A/R 8.0
Table columns rendered incorrectly with new column width A/R 7.0.9+ 8.1
Cannot make a radio button list be “required” A/R 6.0.2+ 8.0
Field set to mandatory in list box Change event always set to mandatory A/R 7.0.9+ 8.1
List box with Change event script will not retain new selection value A/R 7.0.9+ 8.1
Cannot clear radio button list selection A/R 7.0+ 9.1
Click and MouseUp events don’t fire after sign a digital signature field (this may be in older versions of A/R although I haven’t verified it) A/R 9.0-
Designer crashes if you try to make a fragment out of a “Referenced Object” (as reported here in comment #27 by leia) Des 8.2SP2
Form files unexpectedly bloat to enormous sizes (megabytes) while editing them in Designer Des -8.2SP1 8.2SP2
Form fails to render after merging data with namespaced multi-selection list values Acro 9.1.3


  • App: The application affected by the bug.
  • Ver: The version(s) affected by the bug. A negative sign (-) before a version number indicates that version and all earlier versions whereas one following indicates that version and all going forward. Note that the bug may occur in other versions than that which is/are indicated as I’m not able to test in all released versions.
  • Fix: The version as of which the bug is fixed.
    • Nx: Indicates the bug has been fixed in the next release.
    • X: Indicates the issue isn’t really a bug (but may be perceived as one).

Reporting Bugs

The best way to report a bug to Adobe is to use the Bug Report Form. Choose Designer as the “Product name” to report LiveCycle Designer-related bugs.

I would also encourage you to post your observations here for the benefit of others. If you do, please indicate the version of the application which you believe to be affected, steps to reproduce it and a work-around, if you know of one.


If you wish to comment on a specific bug, please do so on the specific bug’s post.

Updated: April 15, 2009

Posted by Stefan Cameron on April 22nd, 2007
Both comments and pings are currently closed.

55 Responses to “Bug List”

  1. Gretchen on May 28th, 2008

    Stefan – Wondering if you’ve heard of this problem and know of a fix….
    When I open/use my Designer, my screen does this fade-in/fade-out loading thing. It does this for any step and change that I make – going from my Design view tab to my PDF Preview tab….just about anything I do, it seems to “refresh” the screen in this slow-fading way. It’s EXTREMELY time consuming and slows up my work. I’ve looked online and in the forums for a solution but can’t figure it out. What’s the deal??

  2. Stefan Cameron on May 28th, 2008


    It sounds like you’re running into performance problems on your system with respect to a new feature/effect that was added to Designer 8 which is to fade-in/out changes to the canvas area. Unfortunately, there is no way to turn this feature on/off. If you have a lot of other applications running at the same time, perhaps things would go a little smoother if you closed a few of them.

  3. superstator on July 14th, 2008

    I have the same issue. It is not a system performance problem – everything else runs fine and snappily. My machine happily runs multiple instances of Visual Studio 2008 / 2005, SQL Server test instances, VM’s and misc apps all together. LiveCycle cannot competently draw it’s cute fade-in/out running all by itself. Maybe it doesn’t like my video driver, but everything else does fine and all I want to do is turn the stupid effect off and get back to work.

  4. Eric Horde on August 25th, 2008


    I have a working PDF form that was created in Adobe and Designer
    (Livecycle). I needed to add (import) 5 pages from another PDF into
    the form. I can import while in Adobe Acrobat Pro and the new pages
    display fine, including all the form fields, buttons, etc…

    However when I switch back to Designer to add database fields to the
    newly added pages, the pages are missing/do not display.

    I open the form back up in Adobe acrobat Pro and the new pages are

    I have 36 pages visible in Acrobat Pro but when I switch to Designer,
    only 31 display. The new ones are not there.

    Any thoughts? Why can’t I see the new pages in Designer?

  5. Stefan Cameron on August 27th, 2008

    Eric Horde,

    I don’t think this is a bug. Please see my response to your comment on my Shading the caption, not the entire field article.

  6. Brian on September 15th, 2008

    Hi Stefan,

    I’d like to inquire with you regarding a possible bug with fragments. You can find a running thread of this at:

    What we’re seeing is that Designer is adding local overrides into our fragment instances ( found in the XML source code ) that are repositioning fields within the fragments when the form renders. Even when editing the XML directly, the tool seems to add the code right back in whenever the form is saved or previewed (i.e., whenever the XML Source editor palette is closed).

    Any help you can provide on the matter would be greatly appreciated.


  7. Stefan Cameron on September 20th, 2008


    This is a known bug in Designer 8.1 and should be fixed in Designer 8.2 (now released). It seems that it’s caused by the presence of text objects (a type of XFA node) in the referenced fragment. If such a node exists, some of the first-level nodes inside the reference will become “defined” in the referencing form. The result is that the order of the nodes inside the fragment reference is changed in the referencing form.

    For example, if your fragment looks like this:

        <field name="field1"/>
        <draw name="text1"/>
        <field name="field2"/>

    The node becomes defined in the referencing form and the fragment, from the referencing form, ends-up looking like this in the Hierarchy palette (the order on the Canvas may also change in the referenced fragment subform has a flowed layout):

    + subform
        - text1

    Unfortunately, the only workaround I know of is to edit the XML Source and specify all of the first-level nodes that appear in the referenced fragment so that the order remains the same as the original. After you’ve done that, the referenced fragment will look like this in Hierarchy palette:

    + subform
        - field1
        - text1
        - field2

    Because the nodes inside the referenced fragment are specified in the referencing form, Designer will allow you to select and edit them however make sure you don’t. Restrict your editing to the subform which is the fragment reference. Do not edit objects inside of it even if Designer now allows you to select them.

    PS: I’ve updating the Adobe Forum thread you referenced. Thanks for pointing it out!

  8. Tim Goodman on September 25th, 2008

    Hi Stefan,

    I just found this bug in Designer 8.2.1 with image fields – it does not occur in forms saved in Designer 8.1

    Here is what I reported on the Adobe Go/Wish site:

    This is a Bug with LiveCycle Designer v8.2.1

    ImageField Objects that are not visible during Document Rendering phases, cannot be made visible once rendered

    Steps to reproduce bug:
    1. Create a new LiveCycle form, add an ImageField, set presence to invisible
    2. Add a button, once clicked sets presence for the Image field to visible
    3. Run the form in Acrobat
    Results: Clicking the button does not make the image field visible
    Expected results: Clicking the button should make the image field visible.

    I have a sample form that demonstrates this that I can e-mail you.


  9. Tim Goodman on September 25th, 2008

    Also … On the Adobe go wish site ( there is not a specific product entry for LiveCycle Designer … there are options for Acrobat Pro OR “Designer”…

    Is the Go/Wish site the best way to report LC Designer Bugs? And if so, which product option should we use?

  10. Tim Goodman on September 27th, 2008

    Please ignore my previous posts … I developed a Dynamic form on a PC with 8.1, then set the Tab order on a PC with 8.2.1

    The default option to “Save As”, must have converted the form type from Dynamic to Static… Frustrating!

  11. Stefan Cameron on September 27th, 2008

    Tim Goodman,

    Thanks for letting me know you were able to resolve the issue. I agree: It’s way too easy to fall into the static vs dynamic PDF trap!

    As for reporting bugs, the Adobe “Wish” site is the best way to do so and you should choose “Designer” from the product list when reporting LiveCycle Designer bugs. We monitor bugs reported via that page. I’ve also updated this page to clarify this process.

  12. Zoe Fisher on December 3rd, 2008


    I’m afraid to say… Tim kinda toched the tip of the iceburg…
    I am designing in Adobe LiveCycle Designer 8.1.2… intended end user Adobe Reader 9, going through Adobe Forms 7.2.
    No matter what settings I change (both render & target), or how I save it (XDP by default, Dynamic) or custom scripting I put in – I CANNOT GET VISIBLE(PRINT ONLY) TO WORK!!
    Any help, advise or opinons welcome!


  13. Stefan Cameron on December 11th, 2008


    It’s probably the fact you’re going through LC Forms 7.2 that’s the problem. It wouldn’t support XFA 2.8 which is what you get when you target Reader 9. If you have to render through LC Forms 7.2, you’re likely restricted to targeting Reader 7.0.9 or earlier (I’m guessing here, I don’t know for sure).

  14. nep on December 13th, 2008

    Not sure if it is a bug, but it is annoying at least 🙂

    When getting a somExpression from a field programatically, we will get something like this:


    However, doing a “CTRL” OR a “CTRL +shift” we can´t get the same somExpression. If we try to make a somExpression like the first one by hand, when we do somehting like xfa[0] we will not be able to navigate all the path down using intellisense (we will only be able to get form but not form1 after). The biggest problem is that we can´t use the somExpression we get programatically to do something like this:

    eval(someExpression + “.rawValue”), because someExpression part will not be resolved. However, if we take those [0] from that some expression the eval will work fine. that is why I think it is a bug.

  15. Alexander on December 17th, 2008

    could you please clarify can we use leader subform with variable height? I mean leader subform which contains children with variable height – e.g. text fields with text that can go 1 line or 2 lines. I’ve noticed that in this case (dynamic leader’s height) problems with start position of overflowed content can occur (seems that position doesn’t depend on changes of leader’s height ).


  16. Stefan Cameron on December 19th, 2008


    That’s a very good observation and I’ll try to explain what’s going on.

    Say you have a button, Button1, and a text field, TextField1, both on the same page in the same subform (e.g. create a new form, add a new button to the page, add a new text field to the page). From Button1’s Click event in the Script Editor, if you Ctrl+Click on TextField1, you get “TextField1”, the relative SOM expression from Button1 to TextField1. If you Ctrl+Shift+Click on TextField1, you get this:


    Note the “xfa.resolveNode” function call with the absolute, yet minimal (because it doesn’t have all of the [0]’s in it), SOM expression to TextField1 from the Form DOM as a string argument. That’s because “#” is not a legal character in JavaScript so you couldn’t write


    in JavaScript and expect it to work whereas you could in FormCalc because FormCalc interprets the “#” and also interprets.

    Now the expression you get when you do TextField1.somExpression is the following:


    It’s a fully-spec’ed SOM expression complete with occurrence numbers (the [0]’s). The problem with using that expression as native JavaScript code is similar to the “#” problem in the previous example: In this case, the brackets signify occurrence numbers, not elements in an array. As such, the JavaScript interpreter is unable to understand what you mean by “form[0]”, for example.

    For this reason, you should always use xfa.resolveNode() to resolve SOM expressions you get from the somExpression property of a node object.

    Finally, to address your eval() example, it should be clear now why eval(someExpression + “.rawValue”) doesn’t work because eval(TextField1.somExpression + “.rawValue”) would evaluate to


    which the JavaScript interpreter can’t understand.

    If you did this, however,

    eval("xfa.resolveNode(TextField1.somExpression).rawValue = 'test';");

    it would work and would set TextField1’s rawValue to “test” because the SOM expression from TextField1.somExpression would be interpreted by the xfa.resolveNode function which understands “#” and “[” for what they mean in SOM expressions.

  17. Stefan Cameron on December 19th, 2008


    That’s right: Acrobat/Reader does not yet support flowed subforms (i.e. that vary in height) as leader or trailer subforms for various pagination features (overflow, conditional breaks, etc.).

  18. Peter Gaston on December 24th, 2008

    Headline: Performance problem on saving form

    Alexander – I have a moderately complicated Adobe form – it publishes out at about 2.5M in size and has about 1500 lines of Javascript – mainly to hide/show fields depending on conditions. Works fine.

    The question is around saving the form. On my development machine (Vista, Designer ES 8.2, Reader 9) it saves in about 5-10 seconds. On the end-user machines (XP, Reader 8) it takes about 3 minutes.

    Any ideas on the Problem? Whys or hows to fix?

    Thanks! Have a great holiday!

  19. Peter Gaston on December 30th, 2008

    Ah ha. I finally found the infamous
    <?templateDesigner StyleID aped3?>

    There were about 1.5 Million lines of these redundant, apparently useless processing instructions in the file! Go figure! This bug seems to have been around for awhile as well. Here’s a link to one workaround.

    Haven’t tested my file save problem – but it sure has stopped Livecycle Designer from crashing on every other command…

  20. Diego Silva on January 5th, 2009

    By the way I’ve been working around the same problem.

    See the latest post in this thread:

    He says that this bug has been fixed.

  21. Bruno on February 20th, 2009

    Hi Stefan

    I have a form that I made with Designer 8.05 where the user must answer a question, and I use “” for that. But each time the answer contain accentuated characters (é, à, ç, etc.), these characters disapear when I want to copy the answer in a field. There is the same behavior with formcalc or with javascript.

    I Wondering if you’ve heard of this problem.

    There is no bug when the form is made with Acobat (8.1.2) to do the same thing.


  22. Stefan Cameron on February 26th, 2009


    That’s news to me though I rarely use Sounds like it may very well have been a bug with Acrobat 8.0. Thanks for letting everyone know about it!

  23. leia on March 20th, 2009

    Hi Stefan,

    I’m using the Referenced Objects () to achieve a common style shared across objects.
    When comes to the point to create them as fragment, LC Designer will hit Runtime Error and then force to close.

    So i wonder if it is possible to create prototype objects and make them as fragment? The reason I wanted to make them as fragment is to share across my forms…

    Thanks in advanced!

  24. Stefan Cameron on March 21st, 2009


    In theory, I don’t see why not though Designer’s <proto> support is very limited. In fact, the only feature that uses protos is Hyphenation in Designer 8.2.

    What version of LC Designer are you using?

  25. leia on March 27th, 2009

    Hi Stefan,

    I’m using LC Designer

  26. Stefan Cameron on March 28th, 2009


    Thanks for providing the version number. It looks like you’ve installed the latest SP2 update.

    Could you expand on how you’ve used the Referenced Objects in your form?

    If I define two fields that both use the same proto for their caption font where the font node referenced (by ID) is defined in the root subform’s proto node, I get an error message from Designer when I try to create a fragment from one of the fields telling me that a referenced node is not included in the fragment but Designer doesn’t crash.

  27. leia on April 6th, 2009

    Sorry for my late reply…

    These are the steps I did:

    1. Created 1 button object (id=”protoButton”) under Referenced objects.

    2. Then, I created 2 buttons. Open XML source, and set their ‘use’ attribute to refer to the proto ID as below:
    < field use=”#protoButton”

    3. Back to Design View.

    4. Go to Form hierarchy > Referenced Objects > protoButton, right click and create fragment

    5. LC Designer then crashed…

    Thanks for helping!

  28. leia on April 6th, 2009

    Some more info…

    Yes, I hit the same message as you got too when I manually define some proto objects/nodes in the XML source (i.e. they appear in XML as <proto …… > but they don’t appear under the form hierarchy)


  29. Stefan Cameron on April 15th, 2009


    Thanks for specifying the steps to reproduce the crash. I was able to reproduce it in LC Designer 8.2 SP2 and will be reporting it to the team.

    Also, objects will only appear inside the “Referenced Objects” node in the Hierarchy if they are “complete” form objects like fields, draws, subforms, etc. If you make a proto out of a <font> node, like I did in my previous reply, it won’t show-up in the Hierarchy (as you have also observed).

  30. leia on April 17th, 2009

    Hi Stefan,

    Thanks! and the good news is… I just got a workaround from Adobe Support i.e. wrap the button object into subform (under Referenced Object), then create the whole subform as fragment.
    It works perfectly now. But thanks for reporting it to the team.. it is still a bug to be resolved.. : )

    Another issue that I reported to the support was the Designer log always complain invalid XFA whenever the form contains button AND with target version set to 7.0.5 and above:

    Anyway… waiting for their good news… 🙂

  31. Kumar on July 9th, 2009

    Is this a bug in LC Designer?

    Step 1: Drag and drop a “Document signature field” in the MASTER PAGE of the form ( not in design view)

    Step 2: Save the form as Dynamic XML form.

    Step 3: Preview the form

    Issue: The Signature field does not appear “ACTIVE” nor seen on the form. if you go over the are ayou had dropped the control the variable name will be shown – but cannot click it and load your disgital signature…

    Is this a bug?: The form virtually does this a bug or what is that I need to make this work. I cannot change the form to be static – since I load variable data on the form. but I need the header and footer of the form to be constant which is why I have put them in the MASTER PAGE.

  32. Stefan Cameron on July 22nd, 2009


    I verified with my colleagues and I’m afraid this is expected behaviour.

    In an XFA form, any field on a master page is replicated for each instance of the master page, which means you end-up with multiple instances of the same signature field. This is something that’s not supported. For the same reason, neither is placing a signature field inside a repeatable subform. Note that this is different from having 2+ signature fields with the same name on the body pages (in this case, they’re still considered distinct fields).

    If you are trying to ensure that the signature field always ends-up at the end of the document, even if new pages are dynamically added to accommodate content as it is filled-in, then I would suggest you make sure the content that precedes the field is flowed. If you really need an indication to sign the form in the header and footer of every page, then I would suggest you use buttons with a “Sign Form” caption which have a Click event that sets focus on the signature field:

    // JavaScript:;
  33. mcyaras on July 29th, 2009


    This is not really a bug in LC Designer, but in how Adobe (both Reader and other versions) deal with forms. I continue to have people not able to open forms/deal with links in a “regular” pdf to a form. Is there a fix for this yet?


  34. Nikkia Carter on August 4th, 2009

    Hey, Stefan (and all)-

    My problem is in two parts but before I go into it here is some background info:
    1. I am working in LiveCycle 8.
    2. The form is a print form (non-interactive).
    3. The form is connected to a XML schema and XML data.
    4. The form contains a master page with content area and a subform (page 1) that is actually 3 pages and contains 2 sub-subforms (Header and Main).
    5. The Main subform contains multiple subforms which contain text, textfields, and tables which are directly connected to the XML schema and data. It also has the Header subform as its overflow leader.
    6. The Header subform contains page # of ## and a textfield.

    Ok, I think that is enough detail. Now for the problems:
    1. The textfield in the Main and Header need to contain the same information. I have tried to connect them both to the same attribute value but only one will display the data. Some of the times that I got the data to display in the Header’s textfield, not only would it not display in the Main’s textfield but only display of the first page’s Header textfield. I also tried to copy the data from the Main’s textfield to the Header’s textfield via the following code (and some variations):
    CRIDHeader.rawData = this.rawData;
    2. As I said earlier, the form has one subform (page 1) which is actually 3 pages long. Because the tables and some of the textfields expand the form can range from 3 pages and up depending on the data retrieved from the XML for its data grouping. So say that have connecting to the XML and running the form the entire “form” is 84 pages. Each of the subform (page 1)s are varying lengths of 3+ pages. My problem is that I need the pages to be numbered from 1 to 3+ (ex. 1-3, 1-3, 1-4, 1-7, 1-4, 1-5, etc upto the 84 pages) instead of the entire form being number 1 to 84.

    I hope I explained the background and my problems thoruoghly. I PRAY that you can tell me the solution. After 2 and 1/2 or so weeks, I am experiencing some serious brain pain ;-P …

    Really appreciate any and all help,

  35. Kumar on August 5th, 2009

    Thanks Stefan. I agree with you totally that Embdedding a signature field in the MASTER page is not allowed by principle. That is why the control does not show up in preview. Thank you so much for clarifying to me with the concept behind.

  36. Stefan Cameron on August 6th, 2009


    I think you’re talking about trouble with Acrobat and Reader with respect to regular (i.e. non-XFA-based) documents but I don’t understand how they don’t properly “open forms/deal with links”… What is it, technically speaking, that isn’t working as you would expect it to?

  37. Stefan Cameron on August 13th, 2009

    Nikkia Carter,

    Those are interesting problems you have. Here are some thoughts:

    1. Usually this works by setting the binding on both fields to the same schema data node. Another way of doing it is to set the binding on the master page field to “None” and then add script to its Initialize event and get the value from the related body page field (rather than the other way around since there will be multiple instances of the master field, one for every page that uses that master page).

    2. This kind of pagination is tricky. Unfortunately, none of the pagination APIs really know about “sections”. They just give you the current page number or the total page count. If I were attempting to do it myself, I would use a hierarchy of subforms on the body pages to achieve it. I would have a section subform that is as big as one page which contains a page subform, again as big as one page, and then put the content inside the page subform. Both the section and page subforms would be set to repeat (or you could not allow the page subform to repeat but allow it to break across pages) such that you could achieve multiple sections, each with their own sets of pages. Then I would have a master page that has a field on it with script that uses the “” call to determine the absolute page number of that master page field stringed into a call to “xfa.layout.pageContent(, ‘subform’, 0)” to get all of the body page subform content related to that master page instance. From there, I would build a “section/page” string based on the index numbers of the instances of the section and page subforms found on that page.

    That’s quite complex so I posted a sample form that illustrates what I mean. Check-out the script on the master page field and look at how the section and page subforms are setup. Note that Acrobat/Reader 8.0 (XFA 2.5) is required for this sample to work since it has fixes to the xfa.layout pagination APIs.

  38. Nikkia Carter on September 2nd, 2009

    Thanks for the reply, Stefan! I’m sorry it took me so long to thank you. I didn’t think I had gotten a response from you because I never got an email saying that you had replied. Anyway, I had created a subform named “Header” which contained the “page # of ##” and “CRID” and included the header as an overflow header on the “Main”subform which contains the rest of the subforms. I am guessing that, from my interpretation of what you wrote, that I should have put both on the master page instead.

    Peace and Blessings,

  39. Nikkia Carter on September 8th, 2009

    Hey! Have another question, please. For some reason, the header which is set through the overflow header is only showing up on two pages. The Subform(page1) has 1.5-3 pages for my project. Even if I condense the Subform(page 1) to 2 pages, if it expands past the 2 pages, due to the size of the data each field is bound to, then the header will not show up on the pages past 2. Do you know how to make it put the headder on all pages no matter how many there are, please?

    Peace and Blessings,

  40. Stefan Cameron on September 14th, 2009

    Nikkia Carter,

    That’s strange. Is there anything special about this subform that you’re using as a header? Is it flowed (because I don’t believe flowed subforms can be reliably used as overflow leaders/trailers). Can you reproduce this in a simpler form (one that doesn’t have everything else this particular form has)? It might help isolate the issue.

  41. Nikkia Carter on September 14th, 2009

    Well, it just to be my stupidness or that “Help” neglected to mention that when you have multiple subforms (which I changed from flowed to positioned) on the “untitled Subform (page 1)” you need to set the overflow leader to the header for each subform that may overflow onto another page. (I blame the “Help” ;-P) So, anyway, no problem with that anymore. Still have the page number problem and a new problem with an extra page, which is blank, that I can’t seem to get rid of. I tried your solution but it is treating all of the subreports (aka the untitled Subform (page 1) that repeats when it is bound to a XML data file containing multiple subreports) as one whole report instead of sections. So I still get S1/P1 – S1/P64 instead of S1/P1 – S1/P3, S1/P1 – S1/P2, S1/P1 – S1/P4, etc… Anymore suggestions please? 🙂

    Peace and Blessings,

  42. Nikkia Carter on September 14th, 2009

    I meant: “So I still get S1/P1 – S1/P64 instead of S1/P1 – S1/P3, S2/P1 – S2/P2, S3/P1 – S4/P4, etc…” (and I actually want the latter, just to clarify).

    Peace and Blessings,

  43. Marcus R. on September 22nd, 2009

    Did you noticed this problem too?

    Some little example:
    On a blank form you place two fields, “textfield1” and “text”.
    Then you create a floating field within text and rename it to “textfield1”.
    Now you set the binding of textfield1 to global and your form properties to dynamic.
    Generally the text now should show the same value as you type in textfield1, but it doesn’t.
    The function will only work, if you also place a second floating field somewhere into the form, where you use one of the defaults such a “current page number” or “current date/time”.

    Here an example of the problem:

  44. Stefan Cameron on September 22nd, 2009

    Nikkia Carter,

    Can you try to better explain your subform structure? Did you try to implement my suggestion from earlier (comment #37 above)?

  45. Stefan Cameron on September 22nd, 2009

    Marcus R.,

    The reason why the floating field’s value isn’t updated in the text object when you remove the other floating field is because the other floating field (current page number) is causing a relayout on the form when the form is changed, thereby causing a relayout of the text object, thereby causing it to “grab” the text field’s new value.

    If you remove the other floating field, you need to force the form to relayout after the text field’s value is changed by putting this statement in the field’s Exit event (for example):


    This behaviour has been the same for a long time because floating fields weren’t originally designed to be interactive however, with Acrobat/Reader 9.1, the behaviour has changed such that the level of interactivity that you’re trying to achieve is supported (i.e. the text object will automatically be updated to contain the text field’s value if its value changes).

    In order to get this behaviour, your form must target Acrobat/Reader 9.1. LiveCycle Designer ES2 can target A/R 9.1 but you might be able to activate A/R 9.1 behaviours by adding the following processing instruction into the <template> node in XML Source:


    When the form is rendered in Acrobat/Reader, this processing instruction will tell it which behaviours to use. Form more on behaviours and compatibility settings, see this post.

  46. Marcus R. on September 23rd, 2009

    Thanks for this hint, Mr. Cameron.

  47. Nikkia Carter on September 25th, 2009

    I tried your solution but it is treating all of the subreports (aka the untitled Subform (page 1) that repeats when it is bound to a XML data file containing multiple subreports) as one whole report instead of sections. So I still get S1/P1 – S1/P64 instead of S1/P1 – S1/P3, S2/P1 – S2/P2, S3/P1 – S4/P4, etc… Actaully the section ends up being the whole document and the page numbers end up being the subsections. So the full document has S1 and page of the subsections say P1 then the next subsection’s pages all say P2 and so on. I know this is hard to visualize. I will talk to my boss on Monday to ask him if it will be ok to send the template to you with sample data. IF you are getting a understanding of what I’m saying, please let me know. Thanks for all your help!

    Peace and Blessings,

  48. Stefan Cameron on September 25th, 2009

    Nikkia Carter,

    The form, or one identical in structure but with different data/field names, would really help. If you’re able, you can send it to formcollateral1 at stefcameron dot com.

  49. Nikkia Carter on September 30th, 2009

    Ok. Sending it now. Thanks!

    Peace and Blessings,

  50. Debbie on October 13th, 2009

    make this site UNSTICKY!! How annoying!

  51. Marcus on January 15th, 2010

    Mr. Cameron I have just a question:
    How can I use the “accessKey” property in a XFA-form?

    As documented in the reference manual I tried

    TextField1.accessKey = “a”;

    in different scenarios, but it never worked.
    I would like to use the method for a faster navigation thru my forms.

    Any help is welcome.
    Thanks Marcus

  52. Stefan Cameron on January 20th, 2010


    While accessKey is a valid attribute of the <field> node, there is no support for it in Acrobat/Reader, which explains why you couldn’t get it to work. I can’t say whether there will ever be support for it either…

  53. Marcus on January 21st, 2010

    Thanks for letting me know.

  54. Radzmar on March 29th, 2010


    I discovered a bug with creating tables in the german version of LC Designer 8.2.
    Every cell (in german: Zelle) that is generated has a space in it’s name such as “Zelle 1” instead of “Zelle1”.
    As long there is no scripts referencing to the cells you have no problem, but otherwise you will always get the error:

    “Illegal name specified for node [Zelle x]”

    When you confirm the error the PDF viewer then only shows:
    “To view the full contents of this document, you need a later version of the PDF viewer…”.

    This problem occurs with both methods you can use to create a table (manually and wizard).

    To solve this you will have to rename all the cells manually by removing the spaces from their name. :-/

    Is this a known one?

  55. Stefan Cameron on April 5th, 2010


    Yes, this is a known issue with Designer 8.2. It was fixed in Designer 9.0.