Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
CRM error while creating attribute in CRM 4.0? RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I am working with CRM 4.0. Three were 295 attributes (including lookup) for an entity. There was client request to create the 250+ attributes to that entity and import the data. We have successfully created nearly 240 attributes including lookup, nvarchar, bit, datetime, picklist etc. Then while creating the next attribute it throws CRM error: "CRM error has occured. Please try again. If problem persist contact your Crm Administrator."

    We had researched on the google. One of the article says it can be dependent on the 8k SQL Server row limit. If this is the case then how can I overcome this problem.

    Thanks,

    Shashi

    Tuesday, May 24, 2011 2:42 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    If you enable CRM tracing, you should get more information about what has caused the error. If the error is due to a SQL limitation (of which there are a few permutations), then you don't really have much choice apart from to change your entity design to have fewer attributes for the entity (295 seems a high number), or maybe to change their datatypes
    Microsoft CRM MVP - http://mscrmuk.blogspot.com  http://www.excitation.co.uk
    Tuesday, May 24, 2011 7:55 PM
    Moderator

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    If you enable CRM tracing, you should get more information about what has caused the error. If the error is due to a SQL limitation (of which there are a few permutations), then you don't really have much choice apart from to change your entity design to have fewer attributes for the entity (295 seems a high number), or maybe to change their datatypes
    Microsoft CRM MVP - http://mscrmuk.blogspot.com  http://www.excitation.co.uk
    Tuesday, May 24, 2011 7:55 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    In addition to the 8KB row limit (which will affect the absolute number and size of attributes that can be created for a single entity type), excess picklist attributes can cause issue due to the 256 table join limitation.  When CRM creates the FilteredViews, it creates a join on the table in which the options are stored, to each picklist value.  It will perform similar joins to retrieve referential Lookup data.

    --pogo (pat) @ pogo69.wordpress.com
    Tuesday, May 24, 2011 10:32 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    We had 295 attributes before adding new ones. Now total attributes no goes to 537 after adding 242 attributes. We tried the following scenarios.

    1. We edited the one of the existing nvarchar attribute maximum length from 100 to 50 and tried to create another nvarchar attribute with maximum length 50. CRM not allowed to create the attribute and throws the CRM error: Try once again or contact your crm administrator.
    2. Then we edited the existing nvarchar attribute maximum length from 100 to 1 and tried to create another nvarchar attribute with maximum length 1. CRM not allowed to create the attribute and throws the CRM error: Try once again or contact your crm administrator.
    3. We deleted one of the existing attribute and created new one with nvarchar 100. This time CRM allowed to create the attribute.
    4. Again we deleted another nvarchar attribute and created new one with nvarchar 100. This time also CRM allowed to create this one.
    5. Then we tried to create another one without deleting any attribute. But this time CRM didn't allow us to create and throwed the same CRM error.

    After observing the behavior from the above scenarios, it seems that CRM entity has reached it's maximum limit of attributes.

    We need to add 25 more attributes on the same entity and import the data. We are stuck with creating more attributes ahead of 537 on single entity.

    Please advise how could we overcome this problem.

    Thanks,

    Shashi

    Thursday, May 26, 2011 12:24 PM