A script error occurs in Workflow Designer in Microsoft Dynamics CRM 2013

A script error occurs when exiting the Workflow Designer in Microsoft Dynamics CRM 2013. This can occur for an entity when fields exist with the same schema name but one having suffix of _c. In some cases, the Dynamic options do not populate when selecting fields in the workflow designer.

Applies to:   Microsoft Dynamics CRM 2013
Original KB number:   2976454

Symptoms

One of the following three script errors may occur:

<CrmScriptErrorReport>
<ReportVersion>1.0
<ScriptErrorDetails>
<Message>Uncaught TypeError: Cannot read property 'length' of undefined
<Line>1
<URL>/_static/_forms/select.js?ver=1163742643
<PageURL>/SFA/Workflow/entityform.aspx?entityFullName=account&entityname=account&stepId=CreateStep1&workflowId=0b37c976-7e2b-4314-9901-2c6458721c42
<Function>anonymousr:Cannotreadproperty'length'ofundefined
<CallStack>
<Function>anonymousr:Cannotreadproperty'length'ofundefined
</CallStack>
</ScriptErrorDetails>
</CrmScriptErrorReport>

<CrmScriptErrorReport>
<ReportVersion>1.0
<ScriptErrorDetails>
<Message>Uncaught TypeError: Cannot read property 'undefined' of undefined
<Line>1
<URL>/_static/_forms/select.js?ver=1163742643
<PageURL>/SFA/Workflow/entityform.aspx?entityFullName=account&entityname=account&stepId=CreateStep1&workflowId=0b37c976-7e2b-4314-9901-2c6458721c42
<Function>anonymousr:Cannotreadproperty'undefined'ofundefined
<CallStack>
<Function>anonymousr:Cannotreadproperty'undefined'ofundefined

<CrmScriptErrorReport>
<ReportVersion>1.0
<ScriptErrorDetails>
<Message>Uncaught TypeError: Cannot read property 'length' of undefined
<Line>1
<URL>/_static/_forms/textinputbehavior.js?ver=401231793
<PageURL>/SFA/Workflow/entityform.aspx?entityFullName=account&entityname=account&stepId=CreateStep1&workflowId=c8c907a5-73fd-4f9e-a18f-e72d2d379bde
<Function>anonymousr:Cannotreadproperty'length'ofundefined
<CallStack>
<Function>anonymousr:Cannotreadproperty'length'ofundefined
</CallStack>
</ScriptErrorDetails>
<ClientInformation>

Cause

This occurs because of fields existing with the naming convention of _c or _d.

For example:

field1 = new_myfield_c

field2 = new_myfield_d

The <fieldname>_c naming convention in Microsoft Dynamics CRM in the form HTML DOM represents the TD containing the label. Additionally, <fieldname>_d naming convention in Microsoft Dynamics CRM in the form HTML DOM represents Cell ID for a Microsoft Dynamics CRM field.

Status

It is recommended to stay away from using this naming convention. This is being reviewed for a future Microsoft Dynamics CRM release.