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

KB214682: Contacts for users merged per the Project Duplication setting "merge users by comparing logins if matching IDs are not found" are not correctly modified to use the merged user.


Community Admin

• Strategy


Contacts for users merged per the Project Duplication setting "merge users by comparing logins if matching IDs are not found" are not correctly modified to use the merged user.

SUMMARY

This technical note outlines an issue found with Project Duplication where contacts for merged users do not get modified to use the merged user when using the setting "merge users by comparing logins if matching IDs are not found". This setting checks for if login or Trusted Authentication ID match between environments for any users despite having different object IDs. This is necessary as login/trusted authentication ID must be unique to prevent a situation where two separate users would have to enter the same login to access Strategy and there is no way to distinguish them.
 

STEPS TO REPRODUCE

In Strategy 9.4.x Tutorial, steps to reproduce are below:

  1. Create a metadata (metadata1) with user A (login A and trusted authentication ID test) 
  2. Create a contact, address and subscription for this user in a project in metadata 1 
  3. Create a metadata (metadata2) with user B (login B and trusted authentication ID test) 
  4. Create a contact, address and subscription for this user in a project in metadata 2 
  5. Do project duplication of the project from metadata 1 to metadata 2 with the option checked to merge users by login 
  6. Check the contacts for the merged user (login B and the object ID from metadata2 should be used) and see that the contact from metadata1 is missing.

 

CAUSE

This is a known issue in Strategy Intelligence Server 9.x. Due to how duplication currently works the contacts are not correctly flagged to be modified to the new destination users Object ID leaving them as invalid in the metadata.
This is related to the issues seen in the following two tech notes:

  • KB214536: Nightly compliance check invalidates subscriptions and removes contacts from the metadata without removing the corresponding addresses in Strategy Intelligence Server 9.x. 

 

ACTION

Currently this issue is being reviewed by Strategy for a potential code fix on an upcoming Strategy release.
 
 
 


Comment

0 comments

Details

Knowledge Article

Published:

April 10, 2017

Last Updated:

July 17, 2017