• State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 96 subscribers
  • Views 475 views
  • Users 0 members are here
Options
Related

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

michel.gruau-ext
1 month ago

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

  • 0 1 month ago

    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.

  • 0 1 month ago

    If I get your problem correctly, you had the same issue as I had.... If you use the AdHocProjection component in your process pushing data to your target system, it is the parameter ForceSyncOf that does the trick!
    Just enter the column you want to force send everytime you do adhocprojection like this: Value = Table.<yourtablename>.<tablecolumn>


    Example on Person table: Value = Table.Person.InternalName

    This will send the value in InternalName of Person everytime you trigger the adhocprojection process, even if it is changed or not. It is also possible add multiple columns too.