How to access data from node of other view into node of diff view?

Question

Hi all,
              My requirement is that I have account defined in 'CLEAR_HEAD' component , view is 'CLEAR_HEAD/ClearAccountsEF'
context node is 'TARGETVALUE' and attribute is 'ACCOUNT1'. I need to access this account information in the same component but in another view 'CLEAR_HEAD/ClearAddressEL' and the context node is 'DEPLIST' and attribute is 'RADIO1'. I have one custom controller 'CLEAR_HEAD/CuCoHead'  already defined in this component. I checked the above 'TARGETVALUE' node but it is not bind to any Custom controller. And I also checked the above pre-defined custom controller  'CLEAR_HEAD/CuCoHead'  and the context node in this Custom controller is different from those of the above context nodes and the only one context node defined in this custom controller  'CLEAR_HEAD/CuCoHead' is 'LISTNODE'.
My quesitons are
1. How to bind the above context node(TARGETVALUE) to the custom controller. Can I bind it to the above existing custom controller  'CLEAR_HEAD/CuCoHead'  , if so then how can I do since the above custom controller doesn't contain this context node(TARGETVALUE) and it contains only  the context node 'LISTNODE'. If I can use the above existing Custom Controller then can I directly do binding by right clicking the context node(TARGETVALUE) -> Create binding. Then what should be the value in Target Contex Node?
2. Do I need to create another custom controller If so then can I directly follow the steps defined in this link '/people/vikash.krishna/blog/2009/12/28/crm-70-how-to--5d-custom-controller-and-binding-of-context-nodes' ? If so then what should be the Model node and Bol Entity name?
I appreciate your help..
Thanks,
Chinnu.

Answer 1

HI Chinnu, <br />
<br />
Approach 1: <br />
Bind the context node view1  TARGETVALUE with Component controller.<br />
and in View2 <br />
data lr_comp_controller type ref to X----component controller<br />
lr_entity TYPE REF TO cl_crm_bol_entity.<br />
lr_comp_controller ?= me-&gt;comp_controller.<br />
<br />
lr_entity ?= lr_comp_controller-&gt;typed_context-&gt;Y-&gt;collection_wrapper-&gt;get_current( ). Y---CONTExt node in view1.<br />
<br />
Approach 2: <br />
Declare a static attribute in the View controller of first view.<br />
Read the attribute D1 value from DO_PREPARE_OUTPUT of first View and pass it to the Static sttribute.<br />
In your 2nd view u can read this Static Atribute and use it.<br />
Static Attribute u need to call as follows . Z********IMPL(Implemantation Class)=&gt;ATTR1<br />
<br />
Approach 3: <br />
Creae a custom controller with the same context node used in view 1. <br />
Bound the custom controller context node to view 1 context node.<br />
<br />
Now in view 2, get the custome controller and read data from it.<br />
<p />
<br />
View1 context node: BTADMINH<br />
<p />
Custom controller: BT115QH_SLSQ/AdminH   context node: BTADMINH_CUCO<br />
<p />
In view 1 context class (CTXT class), go to CREATE_BTADMINH method and append the below code to bind both the context nodes,<br />
<pre class="jive-pre"><code class="jive-code jive-java">* bind to custom controller
   owner-&gt;do_context_node_binding(
            iv_controller_type = CL_BSP_WD_CONTROLLER=&gt;CO_TYPE_CUSTOM
            iv_name =
            <font color="navy">'BT115QH_SLSQ/AdminH'</font>                         <font color="red">&quot;#EC NOTEXT</font>
            iv_target_node_name = <font color="navy">'BTADMINH_CUCO'</font>
            iv_node_2_bind = BTADMINH ).
Now in view 2 get the custom controller using the below code,
Data: lr_cuco type ref to &lt;custom controller class&gt;.
lr_cuco   ?= me-&gt;get_custom_controller( controller_id = <font color="navy">'BT115QH_SLSQ/AdminH'</font> ).
lr_entity     = lr_cuco-&gt;typed_context-&gt;BTADMINHCUCO-&gt;collection_wrapper-&gt;get_current( ).
</code></pre> <br />
<p />
If you are just reading a attribute value  from view1, then approach 2 shud b easy one. <br />
Approach 1 & 3, more or less the same, except we are using component controller vs custom controller. These approaches holds good when the data required to be accessed/updated from either views. <br />
<br />
Coming to your specific scenario, I think there is already a context node available in the compoenent controller TARGETBP, which can have the required data for you. Please look into that. <br />
<br />
Cheers, Satish<br />
Edited by: Satish Reddy Palyam on Aug 13, 2011 12:50 PM