Crash on the account screen after an upgrade

Question

Hi experts.
We have made recently an upgrade from CRM 5.2 to 6.0 and we have some errors.
For example, we can't no longer access the Individual account creation screen, 3 exceptions are raised.
Cannot display view MainWindow
An exception has occurred Exception Class  CX_BSP_WD_INCORRECT_IMPLEMENT - The view controller or custom controller "" was implemented incorrectly 
Method:  CL_BSP_WD_COMPONENT_USAGE=>IF_BSP_WD_COMPONENT_USAGE~BIND_CONTEXT_NODE 
Source Text Row:  24
An exception occurred during the activation of target view Overview.MainWindow for the navigation
An exception has occurred Exception Class  CX_BSP_WD_RUNTIME_ERROR - View Overview.MainWindow could not be bound 
Method:  CL_BSP_WD_VIEW_CONTROLLER=>BIND_VIEW 
Source Text Row:  162
An exception occurred during the activation of target view Overview.MainWindow for the navigation
An exception has occurred Exception Class  CX_SY_REF_IS_INITIAL - Dereferencing of the NULL reference 
Method:  CL_BSP_WD_VIEW_MANAGER=>HANDLE_FOLLOWUP_NAVIGATION 
Source Text Row:  6
For the first exception, I have debugged the system and here is what happens. In the BP_HEAD_MAIN component controller (method WD_USAGE_INITIALIZE), at one point, the
system retrieves the context nodes available and the context node
MESSAGEFILTER is not retrieved. That's why an exception is raised.
The error occurs in the following bloc of code of the :
class : CL_BP_HEAD__BSPWDCOMPONE1_IMPLCM001
method : WD_USAGE_INITIALIZE
CALL METHOD lv_usage->bind_context_node
EXPORTING
iv_controller_type = cl_bsp_wd_controller=>co_type_component
iv_target_node_name = 'MESSAGEFILTER'
iv_node_2_bind = 'MESSAGEFILTER'.
Inside the bind_context_node method, when the system tries to get the
context node (IF_BSP_WD_COMPONENT_USAGE~GET_CONTEXT_NODE), MESSAGEFILTERis not included in the table LT_ALLOWED_NODES
Does anyone have a clue on how we can correct this ?
Thanks in advance for your help.
Regards.
Helder.

Answer 1

Helder,
All you need to do is readjust the repository.xml file after you copied in the standard so that your navigation link or viewset addition changes are put back in.  If you never added a new view to the component or changed the navigation links or did any manual edits to the repository.xml then a straight copy will work.
For example say you enhanced BP_HEAD and stored the enhancements in ZBP_HEAD.  You need to copy the respository.xml file in BP_HEAD over to ZBP_HEAD after the upgrade.  Then you need to reinsert any navigation links,component usages, etc, that you added in CRM 52.  That will then get your component back to standard.  You can also "turn-off" your enhancements by de-assigning the enhancement set to the client and run the "standard roles" to see if your issue is fixed.
Take care,
Stephen