Webdynpro Iview Refresh as F5 through WD Code

[Former Member]

I have Iview having links as,

ADD.

REMOVE.

Application is designed as each module as individual component being called or embeded in MAIN Component.

It is found there are 5 records exists in sap bapi output.

a) 2 records were added through "ADD" component.

b) User is navigated to REMOVE component. Before trying to remove it is found only 5 records as initially.

But with the above ADD operation there should be 7 records (5 old + 2 recently added).

But if the user REFRESH the browser after ADD operation

(

browser refresh by F5 button

OR

Click the "Iview" hyperlink in Detailed Navigation in Enterprise Portal

)

as per above scenerio in REMOVE before removal it is showing 7 records in BAPI output.

We haved added all code related to

1. "REFRESH" - view.refereh() in wdModify of all the defult Indexviews of each component

for "MAIN", "ADD" and "REMOVE".

For these views we have also set "When_visiable" property for the index/default views of these

components.

2. "Context"

Model Nodes: invalidation code for Model nodes input and output

we have invalidated all input and output model nodes.

3, Controller Context RESET.

There is code to reset the context for all individul view and component controllers in

onPLug if each Component index/default views.

We are using Standard BAPI's as Funtion Modules.

In WD code it is reviwed context is cleared at appropriate places.

We need suggestion in which direction we need to analyse for problem resolution.

[Former Member]

Hello Buddy,

You have mentioned that you invalidated the o/p nodes. But the point in your case is that you need to invalidate the nodes in the source component(used component) as well as the o/p nodes in the using or calling component too.

When you refresh the browser screen new instances of the component controllers are created and hence they have the most recent updated data. This can be done explicitly by invalidating the o/p nodes in both the used and using component.

Hope it helps.

Regards,

Prasanna

[Former Member]

Hi prassana,

Thanks for response.

I have seen your replies on other threads.

But is there possibility of resetting the child component to default state when navigate to the parent component.

In my scenerio,

Imagine you are in ADD operation of ADD component.

After adding record,user is navigated to ADD_HOME .From here user can either add new record or Navigate to Parent Component(Application Iview).

During this state is it possibility of resetting the ADD child component to default state when navigate to the parent MAIN component.

is there anything to be done in interface controller ?

[Former Member]

Hello,

I'm not too sure if there's any API provided for this purpose to reintialise the child component. But you can of course do this explicitly.

Just fire an event during navigation from child to parent component. Place your context intialization/invalidation code in the handler.

This is just a possible idea. Hope this helps you.

Regards,

Prasanna