Two default views in CRM

Two default views? How to get back to one

You might come across a scenario where you see that Microsoft CRM lists two different views as the "default" for an entity (as shown in the screenshot below):

Obviously this is not the intended behavior as only one view should be listed the default. Changing the default view and re-publishing the entity with the web interface does not appear to correct this issue. While we're not 100% what causes this scenario, we have figured out a method to fix it.

First you need to export the customizations.xml file for the entity. Then open the customizations file and search for the duplicated defaulted view and change the
 
"isdefault name="Yes" "1 "isdefault "
To
"isdefault name="No" "0 "isdefault"

Note that when you find the view "name" in the customizations.xml file, it is actually at the bottom of the node. This means you will need to scroll up in the file to find the "isdefault" node.

Save, import, publish and you should be all set again.

Error while Assign account to user

I had the following problem after upgrade CRM 3 to CRM 4:

Problem: general unexpected error while assigning account to user or to myself:

Solution: KB 948172  Error message when you delete a queue item from a queue in Microsoft Dynamics CRM 4.0: "Record is unavailable"

http://support.microsoft.com/default.aspx?scid=kb;EN-US;948172

Track in CRM failed due to text exceeds maximum length

Problem: Error message while track email in CRM: the text entered exceeds the maximum length.

Solution: Go to customization, email, attributes, on messageID attribute change the length for more then 100 (I changed to 256).

Cannot add product using crm webservice - Error Number: 0x80043B0A

While trying to add a new product through a webform, I get the following error:

Error Number: 0x80043B0A

To resolve this problem you should check that both "Unit" and "Default Unit" are Business Required fields.

try to place values into both of them and you will find out that the error is no longer exist.

A schema validation error has been detected

Recently i have recieved the following error :

A schema validation error has been detected at line 54409, position 16.

This error shows up if you want to import a customizations file which has been exported from a system which has the Update Rollup package 1 installed.

VisibleToPlatform 0 /VisibleToPlatform

VisibleToPlatform 1 /VisibleToPlatform

There may be multiple reasons for this error to show up, but at least one of them is the existence of one of these lines in your code:

To solve the error message, just remove the line from the code or install the rollup package 1. For information and download of the package go here: http://support.microsoft.com/default.aspx/kb/922815

Error 0x80042F09 while trying to change owner

Scenario 
When you are trying to assign diferent owner you get the following error: 0x80042F09

Cause 
The user, you are assigning has no ROLES asigned.

Solution 
Add relevant ROLE to user