today I want to share a support issue with you.
I have included a summary of the case below for you to keep in your records for future reference when migrating any further CRM 4.0 system to CRM2011.
Summary symptom customer has created a custom application for CRM 2011 which allows users to select views. After migration from 4.0 to 2011 the custom 4.0 views are not non-selectable using the custom application. The views are selectable using the standard view drop down in CRM 2011.
The migrated views have a statuscode = null rather than = 1 as the 2011 view have.
Cause the statuscode values of the migrated views displayed “null” in SQL rather than the 1 value of the standard views in CRM 2011 and newly created custom views in CRM2011. Resolution updating the statuscode values to 1 allowed these views to be selected in the custom application created in CRM 2011 and still allowed the views to be selected in the accounts lists.
SQL statement used: update saved querybase set statuscode = 1 where statuscode is null