Skip to Content
avatar image
Former Member

TableView Data Extraction

Hello

I am using TableView in which I am having input fields which are populated onInitialisation event by instantiating the iterator class.

The user is allowed to enter the data into the dynamically generated input field. One button is provided in which the users can Add One more line(containing input fields) to the table. I achieved this by again creating the instance of iterator class and appending a new row to the table.

What I want is when the page is again loaded, the user entered values (before clicking the button) should persists. Do I need to programatically pass those values to an iterator or can we get fetch the table view values in an iterator?

Thanks in advance.

Thanks And Regards

Rajeev Patkie

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • Best Answer
    avatar image
    Former Member
    Aug 05, 2004 at 06:15 AM

    When you say "page again loaded" do you meant that the user clicks a submit button or refresh or what?

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Aug 05, 2004 at 06:13 PM

    Hello Craig,

    Thanks for your reply.

    Actually I wanted to append a line below in a TableView control. So I had Add Line button and I guess I will have to write the code for adding line in onInputProcessing event handler or DO_HANDLE_REQUEST in case MVC.What currently I am doin is I am instantiating an Iterator class in onInputProcessing event. But I am not able to persists the data which user had entered into the first row. I want to know how that can be persisted?

    Thanks in advance.

    Thanks And Regards

    Rajeev Patkie

    Add comment
    10|10000 characters needed characters exceeded

    • Hi,

      No, the factory methods will always be there. Somehow you need an instance of the control to render it.

      We have just added (today:) an extra technique to pick up some of the more common data quickly. We do not really want people to use direct get_form_field calls (there has been problems in the past). However, we are aware of a number of groups doing this (specifically for input field), and as such will not change this code. Probably never. At this stage, it will break to much code. So for inputfield just leave things as they are.

      b.