locked
Customization import error RRS feed

  • Question

  • I am getting the following error when trying to import a customization file to an existing CRM.  I cannot find any differences in the fields and I cannot find what is causing this error.  Any ideas?  CRM2011 rollup 14.  I am able to import this solution into a new CRM without any issues.

    -<Row ss:AutoFitHeight="0" type="Form">

    - <Cell ss:StyleID="s137"
    name
    ="Time">
      <Data ss:Type="String">11:25:32.14</Data>
      </Cell>
    - <Cell ss:StyleID="s137"
    name
    ="ItemType">
      <Data ss:Type="String">Form</Data>
      </Cell>
    - <Cell ss:StyleID="s137"
    name
    ="Id">
      <Data ss:Type="String" />
      </Cell>
    - <Cell ss:StyleID="s137"
    name
    ="Name">
      <Data ss:Type="String">Tw_employees</Data>
      </Cell>
    - <Cell ss:StyleID="s137"
    name
    ="LocalizedName">
      <Data ss:Type="String">Employee</Data>
      </Cell>
    - <Cell ss:StyleID="s137"
    name
    ="OriginalName">
      <Data ss:Type="String">Employee</Data>
      </Cell>
    - <Cell ss:StyleID="s137"
    name
    ="Description">
      <Data ss:Type="String" />
      </Cell>
    - <Cell ss:StyleID="s137"
    name
    ="Status">
      <Data ss:Type="String">Failure</Data>
      </Cell>
    - <Cell ss:StyleID="s137"
    name
    ="ErrorCode">
      <Data ss:Type="String">0x80044150</Data>
      </Cell>
    - <Cell ss:StyleID="s137"
    name
    ="ErrorText">
      <Data ss:Type="String">An item with the same key has already been
    added.
    </Data>

    Kristen Elliott

    Friday, January 31, 2014 5:09 PM

All replies

  • Hi Kristen -

    A couple of thoughts / questoins:

    1. Is the environment where you got the customizations file on the same rollup as the one you're installing it to?
    2. What type of components are you importing?  If an entity, see if the entity already has the field that you're importing but of a different type.
    3. Is this in a Production environment or a test environment?  If in a test environment, you can easily identify what component is causing the issue by importing pieces of the customizations at a time (only a particular entity, security role, etc.).  Then you can delete that object in your target environment (for example if it's a security role) and import the one from the file.  You'd have to reassign that role to people which is why this is less of an issue in a test environment.  You don't want to do this in production without carefully analyzing what you're deleting (e.g., if it's a field you'll need a migration strategy as data will be lost).

    Good luck!

    Pete

    • Proposed as answer by Pete Majer Friday, January 31, 2014 5:15 PM
    Friday, January 31, 2014 5:14 PM