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
  • 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.

Reply
  • 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.

Children
No Data