Scrolling triggers WDDOMODIFY

[Former Member]

Hi Gurus,

I have an alv table which is displaying data..

i have coded for data refresh and load on WDDOmodify Event..

But the problem is whenever i use the alv scrollbar it triggers WDDOMODIFY which is rendering the table scrolling

havin problem..

Have someone come acrross this.. What is the workaround for this..?

Kindly suggest..

Best Regards,

Navin Fernandes.

Edited by: NAVIN FERNANDES on Jan 27, 2010 3:50 PM

[thomas_jung · Accepted solution]

>Have someone come acrross this.. What is the workaround for this..?

I have a suggestion. Don't use WDDOMODIFYVIEW for data loading. You shouldn't really ever use this event for such activity. That isn't what it is intended for. It should be used for dynamic manipulation of the UI as a last resort.

Why put data loading in WDDOMODIFYVIEW? Generally you do data loading upon initialization or trigger by some action in the UI (hitting a search button).

[Former Member · Accepted solution]

Hi Thomas..

Thanks for your valuable suggestion.

But the problem is ..the scenario is like this..

I have two views View A and View B.. At the first time i select some alv rows and click a button..

Now in the initialization the data loads in the ALV of the second view..

Suppose the user is not happy with the selcted rows..he goes back to the view A and selects another rows..

Now when he clicks the button i want the newly selected rows in my View B..

So i m doin this in the WDDOMODIFY event..

Can you suggest something..?

Best Regards,

Navin Fernandes.

[thomas_jung · Accepted solution]

Is this all one component? If so it seems like this would be easier to populate the ALV Context from the Component Controller. That way just from the push of hte button on View A, you could call the method of the component controller to refresh the ALV in the View B.

[saket_abhyankar · Accepted solution]

Hi,

I think you need not use modifyview method. I think you are using plugs for navigation between 2 views. If this is so then you can use the event created for inbound plug of the view (generally starting with 'HANDLE'). This event handler will be created automatically for every inbound plug. This event will get triggered each time you will navigate to 2nd view

Regards,

Saket.

[Former Member · Accepted solution]

Hi Thomas,

Thank You for your valuable suggestion.

I took care of the data loading part in the context. as mentioned by saket in the handle event

My Problem is solved.

Best Regards,

Navin Fernandes.

Edited by: NAVIN FERNANDES on Jan 28, 2010 7:13 AM

[Former Member · Accepted solution]

Hi Saket,

Thank You for sharing the info..I was not aware of the handle event

it is indeed good way for data loading when using outbound plugs in navigation

Best Regards,

Navin Fernandes.