Microsoft Knowledge Base Email Alertz

(911492) - Describes how to work around a problem that occurs after you delete a custom attribute from Microsoft Dynamics CRM 3.0.

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 911492 - Last Review: August 21, 2007 - Revision: 1.3

Error message when you use a "Quick Find" view or an "Advanced Find" view in Microsoft Dynamics CRM 3.0: "No Attribute"

On This Page

SYMPTOMS

Consider the following scenario. You create a custom attribute in Microsoft Dynamics CRM 3.0. You add that custom attribute to a Quick Find view or to an Advanced Find view. Later, you delete the custom attribute from Microsoft Dynamics CRM 3.0. Then, when you use the Quick Find view or the Advanced Find view, you receive the following error message:
No Attribute
If DevErrors are enabled in the Web.config file, you also receive the following error message:
Microsoft CRM Unhandled Error Details: Server Error in '/' Application.
'Account' entity doesn't contain attribute with Name = 'crm_repro'.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: Microsoft.Crm.Metadata.AttributeMetadataNotFoundException: 'Account' entity doesn't contain attribute with Name = 'crm_repro'.
Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace: [AttributeMetadataNotFoundException: 'Account' entity doesn't contain attribute with Name = 'crm_repro'.] Microsoft.Crm.Metadata.EntityMetadata.GetAttribute(String attributeName, NameMappingType mapping) +76 Microsoft.Crm.Metadata.EntityMetadata.GetAttribute(String attributeName) +7 Microsoft.Crm.ViewCache.FixQuickFindFilter(Int32 EntityCode, String FetchXML) +149 Microsoft.Crm.ViewCache.GetView(String viewId, ViewType viewType) +873 Microsoft.Crm.Web.Tools.Views.ViewManagerPage.Setup(Object sender, DataEventArgs e) +53 Microsoft.Crm.Application.Forms.DataEventProcessor.Raise(FormEventId eventId, FormState state, User user, String objectId, Entity entity) +176 Microsoft.Crm.Application.Forms.AppForm.RaiseDataEvent(FormEventId eventId) +89 Microsoft.Crm.Application.Forms.EndUserForm.Initialize(Entity entity) +56 Microsoft.Crm.Application.Forms.EndUserForm.Execute(Entity entity) +13 Microsoft.Crm.Web.Tools.Views.ViewManagerPage.ConfigureForm() +623 Microsoft.Crm.Application.Controls.AppPage.OnPreRender(EventArgs e) +30 System.Web.UI.Control.PreRenderRecursiveInternal() +62 System.Web.UI.Page.ProcessRequestMain() +1499 Microsoft CRM Application Error Report:
Error Description: 'Account' entity doesn't contain attribute with Name = 'crm_repro1'. Error Details: 'Account' entity doesn't contain attribute with Name = 'crm_repro'.
Error Number: 0x80041103
Note The Account placeholder in the error message is a placeholder for the entity from which you added the custom attribute. The crm_repro placeholder is a placeholder for the actual name of the custom attribute.

WORKAROUND

To work around this problem, add the custom attribute again in Microsoft Dynamics CRM 3.0. When you do this, you must use the same name for the custom attribute. Delete the custom attribute from the Quick Find view or from the Advanced Find view. Then, delete the custom attribute from Microsoft Dynamics CRM 3.0.

Step 1: Add the custom attribute again

  1. Click Settings, click Customization, click Customize Entities, and then double-click the entity to which you want to add the custom attribute.
  2. Click Attributes, and then click New.
  3. Make sure that you use the same display name and the same schema name that you used for the custom attribute that you deleted. Then, click Save and Close.

Step 2: Delete the custom attribute from the Quick Find View

  1. Click Settings, click Customization, click Customize Entities, and then double-click the entity from which you want to delete the custom attribute.
  2. Click Forms and Views.
  3. In the Type column, locate Quick Find View.
  4. Double-click Quick Find View.
  5. Locate the custom attribute in the column, and then select the custom attribute. Click the Remove button, and then click Save and Close.

Step 3: Delete the custom attribute from the Advanced Find view

  1. Click Settings, click Customization, click Customize Entities, and then double-click the entity from which you want to delete the custom attribute.
  2. Click Forms and Views.
  3. In the Type column, locate Advanced Find View.
  4. Double-click Advanced Find View.
  5. Locate the custom attribute in the column, and then select the custom attribute. Click the Remove button, and then click Save and Close.

Step 4: Delete the custom attribute from Microsoft Dynamics CRM

  1. Click Settings, click Customization, click Customize Entities, and then double-click the entity from which you want to delete the custom attribute.
  2. Click Attributes, and then select the attribute that you want to delete.
  3. Click the Delete the selected attribute button, click OK, click Actions, and then click Publish.
  4. Click Save and Close.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

APPLIES TO
  • Microsoft Dynamics CRM 3.0
Keywords: 
kbmbscrm40no kbtshoot kbmbscustomization kberrmsg kbmbsmigrate kbbug KB911492
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate