[Follow Up]<br /><br />After a bit of trial and error I figured it out!<br /><br />For those that need help and are new to Lifecycle, perhaps these tips will help. I'm not certain if these tips work in Lifecycle 7.x as I am using Lifecycle 8.x.<br /><br />****<br />NOTE: If you look at the XML and schema above, I changed the tag <record> to <transaction_detail> as far as my tips are concerned below.<br />****<br /><br />Tips if you need to loop through a complex type element XML feed with XPAAJ:<br />1.) Subforms and tables act the same as far as binding. A subform is an object that allows you to tie elements within the boundaries of the subform to XML field binding and PDF form placement rules. Tables act like subforms from a object binding perspective and in fact can also be placed in a subform.<br /><br />2.) Insert a table or subform or both and then drag the subform or table to the parent form on the hierarchy tab. ****The "Pagination" tab and repeat options will be grayed out if you do not place the subform on the same level as the main PDF form.**** I do not think this is true with Lifecycle 7.x, but it appears to be true with Lifecycle 8.x<br /><br />3.) Select the "Repeat ..." option. Be careful to select repeat on the objects that you want repeated. A repeat on a subform will repeat the entire subform! (All objects within the subform will be repeated). If your just after a table with body rows that repeat. My suggestion is to place your table in a subform (this is so you can more easily resize the width of the table, as it appears the width is locked to the Master page width if a table is not placed within a subform). On your table header row within the hierarchy tab, do not select repeat. On the table body row, seek the repeat check box and go over the various options.<br /><br />4.) Save your PDF as "Dynamic...XML PDF" before you run the Java.<br /><br />5.) On the table or subform, name your binding for the parent complex element tag. My complex element is named "transaction_detail" so my main object table bind is named: "transaction_detail." Then under default binding either choose "normal" or in my case "$record.transaction_detail[*]." <-- I have no idea why this "$record.YOURCOMPLEXELEMENTTAG[*]" is not documented better. It appears "$record.xxxx..." is a reference to a XML complex element and the "[*]" refers to the child elements that fall within the parent complex element. So "$record.transaction_detail[*]" as my main table default binding is telling my table that it is tied to the transaction_detail complex element and the colums within the table are represented by the "[*]" wild card. You then need to bind each child element to each respective cell within that table. Use the hierarchy tab to navigate between objects and feel free to drag and drop objects to where they should be.<br /><br />6.) Now for your table header row (if you have one), Name it and then choose "None" for default binding as you will probably not want any dynamic insertions for your colum descriptions. Play around with the options if you need the header row to repeat on over flow pages, etc.<br /><br />7.) Name each cell with the element name that corresponds within your XML and set default bind as either normal or in my case use the same name. "Normal" just means that the bind is to seek out the respective named element within the XML. TextField or Cell named "XYZ" with default binding set to normal will seek element tag "XYZ" within the XML for data insertion. You can of course over write this match by default binding to any XML element name of your choice.<br /><br />8.) If your repeating a subform with textfields, it's the same concept.<br /><br />9.) No need to import a new data connection (schema) if know your schema, it just helps for drag and drop options from the hierarchy tab.<br /><br />Run your java code and voila! It should work. <br /><br />So for those of you wondering if you can use XPAAJ to extract XML data and insert into a PDF dynamically and also incorporate repeating rows of data, yes it can be done!<br /><br />Hope this helps,<br /><br />Thank you,<br /><br />John
