Issue: Saving dynamic form as reader extended (to allow saving) causes certain header rows to repeat

[#1]

I use LiveCycle to create electronic forms/worksheets for the group I support at work.  I've had two worksheets have this issue recently.  One I was able to fix by going to my previous version, re-editing, and re-saving.  The other continues to be a problem.  The worksheet is dynamic, and has several add row features.  The form continues to work fine, but the header rows in certain tables repeat when saved as a reader extended file which allows my users to save the form (required for our work).  I've completely re-done the worksheet from scratch, as well as re-editing from previous versions with no luck.  The best I can do is get repeats to change header rows.

This is the dynamic file prior to saving as a reader extended document:

And after:

Any suggestions on how to fix this issue?  I can't spend hours re-creating the entire document if its just going to happen again...

Thanks.

[jasotastic81 · Accepted solution]

You said it's in certain tables. Just considering the tables that are affected:

• Are there scripts set up that create the table dynamically? Or do the tables already exist and the additional rows are added dynamically?
• Look at the name of the header rows. Are there any scripts that reference the header rows?

[#3]

The entire worksheet was created in Design View - so all the script written was done automatically by LiveCycle - The tables all exist with a single row to start, and rows have the ability to be added dynamically.  As far as the scripts referencing header rows, I do notice that the header rows in each table are all named the same ("header row") in the script - could this have caused a glitch?  In the hierarchy chart, they are separated out by a bracketed number, so it seems to realize they are separate.  But let me try renaming each one separately...

Well that worked!  Its the first time I've been able to Extend the document without extra rows on this version of the worksheet!  So all I did for future users, was to make sure each Header Row was specifically named differently - so HeaderRow1, HeaderRow2, etc.

Thank you so much!