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

KB226862: Trying to add new Contact Group member shows “ImageCombo1” and editing existing contacts fails with error “Object with ID XXX and type 34 (user) is not found in the metadata” in MicroStrategy Developer 9.4.x


Stefan Zepeda

Salesforce Solutions Architect • Strategy


This document discusses an issue where users are not able to add new members to a Contact Group and editing existing Contacts gives a metadata related error.

SUMMARY
This document discusses an issue where users are not able to add new members to a Contact Group and editing existing Contacts gives a metadata related error.
 
SYMPTOM
When trying to add a new member to a Contact Group, users are unable to do so, and the drop down shows “ImageCombo1”

ka02R000000kbHnQAI_0EM440000002C8l.jpeg

 
A valid drop down would look like the following:

ka02R000000kbHnQAI_0EM440000002C8k.jpeg

 
Additionally, particular Contacts give the following error when trying to edit them.
 

ka02R000000kbHnQAI_0EM440000002C8n.jpeg


Object with ID XXX and type 34 (user) is not found in the metadata

 
STEPS TO REPRODUCE
1) Create a contact and user, and link the contact to the user.
2) Create a history list subscription for this user.
3) Delete this user (from search result window), then the issue is reproduced.
4) The contact is still there, but when editing it, the error appears regarding “Object with ID XXX and type 34 (User) is not found in metadata.”
5)  When trying to add new members to a contact group, “Imagecombo1” displays.
 
CAUSE
This is a known issue in Strategy Developer 9.4.x.  The issue occurs when a user/contact has been added to a subscription and then the user object is deleted but the contact object is not.  It leads to this issue because contact objects cannot be associated with a subscription unless they are linked to a user object, which is no longer the case after the user has been deleted.
 
ACTION
Currently this issue is still being reviewed for feasibility by our Technology team and it is not scoped for any upcoming scheduled Strategy release. 
 
WORKAROUND
Deleting the now invalid Contact object will resolve the issue.  If assistance is needed in identifying the invalid Contact Objects, please contact Strategy Technical Support for further instructions.
 
This issue is being tracked by internal reference number 527750


Comment

0 comments

Details

Knowledge Article

Published:

April 10, 2017

Last Updated:

July 21, 2017