Showing posts with label Customization. Show all posts
Showing posts with label Customization. Show all posts

Wednesday, October 26, 2011

Remove Dashboard menu from workplace area in MSCRM 2011

Hi All,

Recently I got one request to remove dashboard menu from workplace area in CRM 2011.

Solution:
1. Export your solution from CRM 2011
2. Open customizations.xml file from the exported solution folder.
3. Goto XPath: ImportExportXml -> SiteMap -> SiteMap -> Area (workplace) -> Group (MyWork)
4. Remove the below tag from the above path

<SubArea Id="nav_dashboards" ResourceId="Homepage_Dashboards" Icon="/_imgs/area/18_home.gif" DescriptionResourceId="Dashboards_Description" Url="/workplace/home_dashboards.aspx" GetStartedPanePath="Dashboards_Web_User_Visor.html" GetStartedPanePathAdmin="Dashboards_Web_Admin_Visor.html" GetStartedPanePathOutlook="Dashboards_Outlook_User_Visor.html" GetStartedPanePathAdminOutlook="Dashboards_Outlook_Admin_Visor.html" />

5. Import the solution to CRM.

Check it out that Dashboard menu will be removed from your workplace area. 

In case if you again want to make it visible, paste the above tag to the same xPath and you the menu item will again be visible for use.

Hope you find this post helpful.

Thank You !!! J

To use this saved view, you must remove criteria and columns that refer to deleted or non-searchable items

Hi,

After a long time, today I would like share one of the issue which I faced during my work with CRM 2011.
I added some new fields to my new custom entity and wanted the field level security for them. I went to Settings -> Administration -> Field Security Profiles and opened one of my existing profile. At this moment I got an error as below.

"To use this saved view, you must remove criteria and columns that refer to deleted or non-searchable items."

After searching for this error about an hour, I realized that before creating new fields of the custom entity, I have deleted another custom entity which has some of its fields having field level security enabled on them and were used in the same exiting profile which I needed for the new fields.

Solution:
Solution to this issue was really very simple. We just need to delete the fields of the deleted entity from the field level security profile.

Delete the records from FieldPermissionBase table where attribute is used (attributelogicalname) or all the fields of the deleted entity having field level security enabled.

Query to delete attributes: 

-- Replace respective entity objecttypecode with 10003 below
DELETE FROM FieldPermissionBase
where EntityName = '10003'

And finally the above error will be vanished and you are just good to go on with your work... 

Hope this solution helps you to get rid of this error and happily move on with CRM 2011. 
Feel free to post the query in case you need any aid for Dynamics CRM and this post.

Thank You !!! J

Tuesday, October 12, 2010

Error message when you export or delete entities in Microsoft Dynamics CRM 4.0:
"An unhandled exception occurred during the execution of the current web request"


Hi,


Recently one of my friend faced a weird type of error while exporting the customization. Error was something like

"An unhandled exception occurred during the execution of the current web request"

After searching for the error on the web... I encountered the link of Microsoft Knowledge Base article for the issue and solution to it. 
Find the URL for the same: http://support.microsoft.com/kb/947096

The common root cause for this issue is:
  • An entity form has an attribute that does not exist.
  • A primary entity of a relationship was missing during the previous import and because of which the relationship lookup attribute on the secondary entity form became orphan.
Solution:
1.    Firstly you need to find out the entity for which the error is arising. (In case you are using Export All Customizations). 
After finding the Entity you need to find out the culprit attribute on that entity form which is orphan. To find out the same follow appropriate method as given in the Microsoft KB link which I provided above or for your faster reference find the same below:
 Note The error message in the platform trace file does not display the exact attribute that causes the problem.
2.    Open the Form editor, and then find the attribute that causes the problem. To do this, use one of the following methods:
    • Look for an attribute that is missing a label.
    • Look for an attribute the properties of which have only the Name value and do not have the Display Name value or the Description value.
    • Create a new record for the entity that you found, and then find the attribute that causes the problem.
3.    Create a temporary attribute that uses the same name as the attribute in the entity form.
4.    If the attribute is not required for the deployment, follow these steps:
a.    Delete the attribute from the entity form.
b.    Publish the entity.
c.    Delete the temporary attribute.

Please feel free to post any queries/comments you have...


Thanks. J