There are some attributes on CRM default forms which you cannot remove. This post will show you how you can do this anyway. While doing so, please keep in mind that Microsoft must have good reasons to fix attributes on the form. Removing this might have implications, as always have a good backup ready.The steps you need to follow to remove are:- Export customizations for the specific entity-
Monday, 29 June 2009
Wednesday, 17 June 2009
Changing default organisation
Posted on 08:10 by Unknown
You can change the default organisation by opening the configuration manager. In this tool you can rightclick on the organisation which you want to set as default and click "set as default". You'll see that the name of the organisation has changed to: Orgname (default).After you perform an IISReset you would expect the new default organisation to open up when you browse to your CRM server.
Wednesday, 29 April 2009
Change the CRMAppPool Identity
Posted on 07:45 by Unknown
Most likely this is recorded in a thousand places, but I had a hard time finding info about what steps need to be taken to change the identity of the CrmAppPool. All you need to do is:- Create a user in Active Directory- Make sure the user has Domain User rights- Add the user to the PrivUserGroup of CRM- Make sure the user has 'log on as a service' priviledgeThe last step can be executed on two
Automatic provisioning of Organizations
Posted on 02:36 by Unknown
Microsoft CRM does have a separate webservice for doing deployment related activities. There is a Deployment SDK especially for this webservice. You can download that here. One of the activities you can execute is automatic provisioning of new organizations. In this post I'll dive into the code required for this as well as some of the common issues while doing so.Basically following the next
Thursday, 23 April 2009
Walk through all elements on a form
Posted on 01:08 by Unknown
In some cases it is required to set all attributes on a form to disabled or do some other logic like checking which attribute has been changed. To do this you do need to walk through each attribute of the CRM form. My fellow MVP Mitch Milam has posted the technique to do this more than a year ago:http://blogs.infinite-x.net/2007/11/21/disabling-all-fields-on-a-crm-form/The most important piece of
Thursday, 16 April 2009
401 Unauthorized when accessing the webservice
Posted on 15:02 by Unknown
While there are many situations in which you can retrieve the error message 401: Unauthorized, there are some more difficult to find than others. Of course you have After you have checked the basic settings including:- Are the default credentials used- Does the user have an account in CRM- Does the user have enough priviledges in CRM- Is Windows Authentication enabled for the CRM website- Is
Hiding elements: the next evolution
Posted on 14:35 by Unknown
One of my colleagues, Richard McCormick, has written a blog post for the Avanade internal employees. He has asked me to make this post publically available since it might be interesting for more people. Read on and get great code samples on how to hide attributes, elements and sections.Hiding Links & Controls in CRM 4 Before I go on, I should point out that this solution is technically
Subscribe to:
Posts (Atom)