A script error occurs during lead qualification or leads cannot be qualified in Microsoft Dynamics CRM

This article provides a resolution for the issue that you may receive a script error during lead qualification or the leads cannot be qualified in Microsoft Dynamics CRM.

Applies to:   Microsoft Dynamics CRM
Original KB number:   2808214


After a Microsoft Dynamics CRM Online organization is upgraded to the December 2012 Service Update, but has not applied the latest Product Update, users may notice a script error that will occur during lead qualification. As a result of the script error, the lead is not qualified.

The same issue can also occur in Microsoft Dynamics CRM 2011 On-Premise deployments with Update Rollup 12 applied.


This problem can occur when the transactioncurrencyid (Currency) or the companyname (Company Name) fields are removed from the form prior to the December 2012 Service Update. Microsoft is aware of this symptom and will be addressing this issue in a future update.


As a workaround, the transactioncurrencyid (Currency) and/or companyname (Company Name) field(s) can be added to the form.

  1. Select Settings, select Customizations, and then select Customize the System.
  2. Under Components, expand Entities, and then expand Lead.
  3. Select Forms.
  4. Open the form(s) where the issue reproduces.
  5. In the Field Explorer, locate and drag the Currency field onto the form. Repeat this action for the Company Name field if this is also missing from the form.
  6. Optional: To hide the fields on the form, double-click on the field as it exists on the form, and under the Visibility section, uncheck Visible by default, and select Ok.
  7. In the form editor, select Save, and then select Publish.

More information

Script Error Contents:

<Message>Unable to get value of the property 'id': object is null or undefined</Message>
<BrowserUserAgent>Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; InfoPath.3; MS-RTC EA 2)</BrowserUserAgent>