CRM 3.0 Errors

Normally CRM 3.0 will be displaying "An Error has occured.Contact your system administrator" as the error message. A developer will not be happy with this error message as the exact cause of the error is not visisble to him.

There is a method to get the real deal displayed on the screen. But this should be done only in the developemnt enviornment as the users will not be happy with the exact error messgae they will be seeing.

To see the error message you need to make the developererorr variable in the web.config to On. you can find the web,cofig under the CRMweb folder.

Reports in CRM 3.0

When viwing reports in CRM users get so many issues. 2 common issues are
1. SQL reporting service has not been configured properly.
2. CRM web site is running under asp.net 2.0 version.

About CRM web site running under asp.net 2.0 is ok for the web forms, but for the SRS it has to be running under asp.net 1.1 version.

Microsoft Dynamics CRM 3.0 Virtual PC Demonstration - August 2007 Release

Microsoft has released a new virtual PC image of CRM. This is a 2.2 GB zip file. when extracted it will be around 7 GB.

The link to download this image is given below.

http://www.microsoft.com/downloads/details.aspx?FamilyID=57394bc8-5ecc-422e-a066-34189f48f8c8&displaylang=en

This image will get expiered on 11/30/2008.

Built in modifed and created on fields in CRM3.0

These field values gets updated automatically when we do a change to a record. but did you know when you display these fields on a form eventhough that these fields are date and time fields you can only is date part of the field.

Because of this issue i had to create a new field for modified on because my customers wanted to see the modified tme as well.

javascript Onchange event in CRM 3.0

today we had to change the value of a filed(Disabled) in a crm form when another field value was getting changed. we were able to do this firslty and when saved, the data got saved perfectly.

we were happy till we saw that when updated the disbaled field value was not changed eventhough we have actually changed the value by modifying the affected field.

after sone time we thought that since we are using javascripts the value is not getting passed to the server, because the server thinks that the value has not been changed.

So we used the followinf statement to check whether the value will be chnaged and what do you know, it worked perfectly.

crmForm.all.[fieldName].forceSubmit = true;

As i got to know this is very useful when it comes to disbaled fields. whether the field value has got chaned or not when saving the value of this field will be sent to the server.