Posts

Showing posts from November, 2008

CRM 4: Report security issue when CRM database is imported

Avoid at any cost to import your CRM database if you do not want to screw up your Report security. The problem symptoms noticed: 1. New reports added are not visible to users of other business units even though the reports have been set to Viewable to Organization.  2. Existing reports viewable to organisation are visible after import, however, once modified (eg. change report area, category, etc), the report becomes not visible. 3. Existing report Owner lookup is broken. The Owner's name is gone and clicking on the Owner lookup will display 'Record is not available' screen. Although I do notice if the report is assigned to new user, the report becomes visible to that user even after the report is assigned to other user. However, I cant imagine the tedious repetitive exercise of assigning the report to hundreds of users. The solution can only be obtained via CustomerSource for now. It involves running some SQL scripts to update some GUID values in PrincipalObjectAccess and

CRM 4: Follow Up button causes script error when Form Assistant Pane is disabled

Obviously many of you have found that Form Assistant Pane is not really that useful. Therefore, CRM 4 has an option to disable Form Assistant Pane completely. However, the CRM team seems to have forgotten about the Follow Up button in the main toolbar. Clicking on the Follow Up button supposedly will expand the Form Assistant Pane and allow users to quickly create a Follow Up task activity, but instead, script error will occur because the Form Assistant Pane is no where to be found. It is possible to hide the Follow Up button using script on load of the form. if (document.all._MBdocumentallRelatedInformationPaneExpanddocumentallRelatedInformationPaneLoadContextDatafollowup)     document.all._MBdocumentallRelatedInformationPaneExpanddocumentallRelatedInformationPaneLoadContextDatafollowup.style.display = 'none';