cancel
Showing results for 
Search instead for 
Did you mean: 

Display selected records in another table in the next screen in WDJ?

Former Member
0 Kudos

I have to select multiple rows from a table and have to display those selected records in another table in the next screen.


Accepted Solutions (1)

Accepted Solutions (1)

vdurgarao09
Contributor
0 Kudos

Hi VREDDY,

one view to another view we are using the navigation plugins(in bound and out bound).1st view table level what are the records selected that one set to another view table while calling the navigation plugin.So this is very easy.I think your new for this.This is basic functions of the Table UI.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90ac0015-d1c5-2a10-d788-aed899908...

This is not your problem means can you share the proper information that time any one can help you.

BR,

Durga Rao.

Answers (2)

Answers (2)

junwu
Active Contributor
0 Kudos

suppose your table in first view is bind to node A

create a node B (same structure as A but different name)in component controller and map to your first view

when you navigate to next view, copy the selected node element from A to the node B

in the target view create a table which bind to the node mapped with B.

michael_voss2
Participant
0 Kudos

Even the name may be identical...

junwu
Active Contributor
0 Kudos

why? in the first view, he has to copy the selected  ones to the new node. how they can be the same name?

michael_voss2
Participant
0 Kudos

Yer, you're right. If you want to copy the elements in view A, you'd have to have a second node (with a different name) in this view which is mapped to the component controllers context and into the context of view B from there. If you wanted to perform the copying in view B, you can map the existing context node from view A to it's componet controller context (identical name), from there to the context of view B (identical name) and then have the selected elements copied to another node in view B.

Mapping the original node from view A to the component controller might make it easier to filter the table contents in view A, which in turm might make it easier for the user to find the rows he wants so select, so I was thinking in this direction and not reading your post properly.

Regards

Michael

michael_voss2
Participant
0 Kudos

Hi VREDDY!

Propably you are using some context node to provide the table data. You might want to map this context node structure to an identical structure in your component controllers context. If you map this to the following view, too, you'll have access to the table items and their selection state.

Hope that halps

Michael