Help needed in Service Ticket view version CRM 2007

Question

Hi,
We have a requirement to replace the Service Level Agreements with Location details screen (custom defined) in the Service Ticket View. I did this in 5.0 version,but couldn’t replicate it in the CRM 2007
version.
Here is how I proceeded in the new version.
Instead of creating a new view, I approached the Adding required
context node approach and populated the fields that we need.
1. I enhanced the component ICCMP_BTCTR
2. I added Context node BTActivityH ( I did not link it to any CutomController in the wizard, but defined dependency to Higher LevelContext node BTAdminH, with BOL relation, BTHeaderActivityExt, and
activated the check box “Always Create Instance” and let the the wizard to finish off.
3. Then using the UI Config tool, I copied the standard configuration to my custom config for changes, I removed all the 3 fields that are there in the standard configuration, and replaced with the attributes
of BTActivityH using UI Config tool in the component work bench. All fields are Input ready fields (not set for Display only).
4. When I open the Service Ticket view to access these fields, in the UI of Service Ticket, I realized that they are display only fields.
5. Then I created the attributes, ( to access GET_I_S_*) methods of the attributes, and I externally set rv_disabled = ‘FALSE’ in the metod (say GET_I_S_CITY)
6. Now I am able to input values for those fields, but still I am not able to save those entries that I entered in there.
I guess I am missing some thing in the wizard, like linking custom
controller or dependency relations.
Is it mandatory for me to bound the context node to component
controller Node (BTActivityH). If so how can I bound it.
Please advice me.
Thanks and regards,
Sreekanth

Answer 1

Hello Sreekanth,
I think that the fields are read-only and not saved because your context node is not bound to a custom controller. (Even though your higher level node, BTAminH, is probably bound to a CuCo)
The code to perform the CuCo binding is mostly coded in the CREATE_BTACTIVITYH (controller class->typed_context->create_btactivityh or check create_context_nodes to see how the method is called)
like this:
  owner->do_context_node_binding( iv_controller_type = cl_bsp_wd_controller=>co_type_custom
                                  iv_name            =  <name of the CuCo>"#EC NOTEXT
                                  iv_target_node_name = '<the context node of the CuCo to bind to>'
                                  iv_node_2_bind = <your context node> ).
Now, save yourself a headache and a lot of debugging time and just create a new context node through the wizard again, this is much easier than trying to 'fix' it yourself! Once you have created your new context node you can delete the old one by deleting the attribute in the typed_context class.
Hope this helps!
Reward points if useful!
Kind regards,
Joost