Looking for help with repeating table rows and subform | Community
Skip to main content
F
Figitout
New Participant
November 19, 2013
Solved

Looking for help with repeating table rows and subform

  • November 19, 2013
  • 12 replies
  • 8123 views

I’m hoping someone might be able to help me figure out how to accomplish some things with a repeating table subform in a form I’m building.  I’ve attached the file here. 

https://workspaces.acrobat.com/?d=2nUNZuTf2T4tsdSykMTlXw

I have a table (AssessChart1Table) it set up on pg 7 (Analysis) and have built in buttons(AddRowAssesChart1 and DeleteRowAssesChart1) so the user can add or delete additional rows of data as needed. 

The problem is that the user also enters data going across in the header row (AssessChart1HeaderRow1) of this table.  There are 10 columns available; however, they may need to add more data than that. Therefore, I made a button (AddMoreCourses) for the user to click to add another instance of the table subform (AssessEvalChart1) and also undo the adding of the subform with this button (UndoAddMoreCourses).

In addition, I have it setup that whatever data the user enters into the cell (Prog-DeptObjChart1) cell of that table gets automatically transferred to another table (AssessChart2Table),  cell (Prog-DeptObjChart2), which is located on the next page (AnalysisCont1).

All of the above works fine except that whenever the user presses the button (AddMoreCourses) I don’t want it to automatically fill in the text field cells that are copied over from (AssesChart1HeaderRow3) because I need the user to be able to enter different values in lieu of adding more columns to fit their data.  Additionally, I would like the values from the cells in the left column to repeat though because these values won’t change. Currently the values from the cells in the left column that carry down to (AssessChart2Table) get messed up on (AssessChart2Table) anytime I the user pushes Add More Courses button or Undo Add More Courses button.

In summary the tables would look like the attached screenshots:

:

Any help would be so greatly appreciated.  I am not experienced with Livecycle Designer.  The form I've built by reading examples and forums. 

In case you need this, I'm using Livecycle Designer v. 9.0.0.2.20120627.2.874785 on a Windows 7 Pro platform.

Thank you!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by jasotastic81

They'll need to copy over in a similar way as the other rows did. I would suggest on the exit event for the Prog-DeptObjChart1 field, add code that copies the rawValue from it to the second chart. Your code has something there, now, but it doesn't take into account that there will be multiple instances of the same row.

So, in your action builder, add another result to the AddRowAssessChart1.click condition: Add a new instance of AssessChart2Row1.

Then in the exit event for Prog-DeptObjChart1, add this code.

xfa.resolveNode("AnalysisCont1.AssessEvalChart2.AssessChart2Table.AssessChart2Row1["+this.parent.index+"].Prog-DeptObjChart2").rawValue = this.rawValue;

Now when you exit the field you typed in, the text is copied to Chart2.

12 replies

Show previous replies
F
FigitoutAuthor
New Participant
November 20, 2013

Thanks!  I was wondering about that.  I set "header3" to have global binding so that if the user adds enough rows or their text expands the rows enough that the table continues on the next page it would repeat those same headers they entered at the top of the next page.  However, I can see how that would cause a conflict with repeating the subform.  I can eliminate the global binding if both can't be done as it is much more important to me that the other things carry over correctly than to have those "header3" text fields automatically populate if the table happens to span more than one page.

jasotastic81
jasotastic81
New Participant
November 20, 2013

I figured out one of the problems. Your form uses global binding for "header3", so each time you make a form, you automtically populate the same items, and since it's global, if you change it in another table, it will change the original, too.

    Terms & ConditionsAccessibility statement

    Loading footer...