EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB219716: "The key is already associated with an element of this collection" error message appears when editing attribute forms in MicroStrategy Developer 9.4.x-10.x.


Stefan Zepeda

Salesforce Solutions Architect • Strategy


This knowledge base article explains why "The key is already associated with an element of this collection" error message appears when editing attribute forms in MicroStrategy Developer 9.4.x-10.x.

SUMMARY:
This issue has been classified as a defect by Strategy. The impact is limited to Strategy Developer 9.4.x-10.x product only with duplicate columns of different data types. A solution for this issue is available in the current releases but requires a backup of the Metadata.
 
SYMPTOM:
In Strategy Developer 9.4.x-10.x, when users try to create a report with a shortcut to an existing template object, the following error appears:

ka04W000001Iv9aQAC_0EM440000002C9y.jpeg


Unexpected error This key is already associated with an element of this collection.

 
STEPS TO REPRODUCE:
Note: Steps to Reproduce require duplicate columns with different data types to exist.
1. Log into either a 2-tier or 3-tier project source as shown below.

ka04W000001Iv9aQAC_0EM440000002C9m.jpeg

2. Open up the 'Strategy Tutorial Project' and navigate to Schema Object->Attributes->Customer as shown below.

ka04W000001Iv9aQAC_0EM440000002CA2.jpeg

3. Edit the Customer attribute as shown below.

ka04W000001Iv9aQAC_0EM440000002CA0.jpeg

4. Attempt to modify the attribute form as shown below.

ka04W000001Iv9aQAC_0EM440000002C9k.jpeg

5. Error message appears as shown below.

ka04W000001Iv9aQAC_0EM440000002C9w.jpeg

Video:
You can find a detailed video on how this issue is reproduced here:
 
 
CAUSE:
This issue occurs if duplicate columns exist with data types being different. The custom ScanMD test that removes duplicate columns does not resolve the issue when the data types are different on the affected columns.
 
ACTION:
Contact Strategy Technical Support for assistance with the issue. To verify this issue a backup of the Metadata is required to generate an Object Manager package to fix the data type inconsistencies and then the custom ScanMD test will resolve the duplicate columns. 
 
ADDITIONAL TROUBLESHOOTING:
When migrating objects from one environment to another verify that all underlying objects affected by the change are migrated over. 
 


Comment

0 comments

Details

Knowledge Article

Published:

April 28, 2017

Last Updated:

July 21, 2017