How to force using the "new value" in an "Object matching rule" in a synchronization project ?

Hello,

We have a synchronization project which allows to update an attribute in a target system (in this case SuccessFactor).

It works fine but we have a use case where, when the key specified for OneIdentity side in "Object Matching Rule" is modified, we need to map the new value with the target attribute and not the old value. The goal is benefit from this mapping to update another target object instance.

In other words, is there a way to force using the "new value" in an "Object matching rule" ?

Many thanks for your suggestions.

Regards

Michel

Parents
  • So you are modifying one of the key attributes (used in the Object Matching rules) in Identity Manager. Still, an object in the target system already has the "new" key attribute matching but not the old one.

    Did I get it right?

    Can you explain the reasoning for this in some more detail, please?

    And (as always), can you please share the version you are using.

Reply
  • So you are modifying one of the key attributes (used in the Object Matching rules) in Identity Manager. Still, an object in the target system already has the "new" key attribute matching but not the old one.

    Did I get it right?

    Can you explain the reasoning for this in some more detail, please?

    And (as always), can you please share the version you are using.

Children
No Data