000037827 - Another Mapping already exists for the target account attribute warning in RSA Identity Governance & Lifecycle when setting up Attribute Synchronization

Document created by RSA Customer Support Employee on Aug 15, 2019
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000037827
Applies ToRSA Product Set: Identity Governance & Lifecycle
RSA Version/Condition: 7.x
 
Issue.When defining an Attribute Synchronization target account attribute in RSA Identity Governance & Lifecycle, the following error occurs:
 

Another Mapping already exists for the target account attribute "{Name of Attribute}" on "{Application/Directory}"



User-added image
 


 
CauseThere is already a source user attribute mapped to the target account attribute. Another source user attribute cannot be mapped to update a target attribute field already being updated (synched) from a different source.

In the above example, you are trying to define the Department field in the Active Directory data source to be updated to the value of Cost_Center_Name whenever the Cost_Center_Name user attribute is detected as changed. However, the Department field in the Active Directory data source is already defined to be updated to the value of Department whenever the Department user attribute is detected as changed:

 
User-added image

The source user attribute Department is mapped to the target account attribute Department in the Active Directory application. Therefore another user attribute (in this case Cost_Center_Name) cannot be mapped to the target account attribute Department.
ResolutionChoose which user attribute should be used to update the target attribute field. This is current product behavior that helps prevent target attributes from being accidentally overwritten by the incorrect user attribute.

 

Attachments

    Outcomes