Differences

This shows you the differences between two versions of the page.

--- devel:documentation:synchronization:dev:relation-sync [2022/12/21 09:24]
apeterova correlation
+++ devel:documentation:synchronization:dev:relation-sync [2022/12/21 09:28] (current)
apeterova [Correlation]
@@ Line 186: / Line 186: @@
 ===== Correlation =====
-Synchronization of contracts supports only correlation by simple text attributes. That means, if you already have some existing contracts and you want to pair them with accounts on some new source system, you have to use some e
+Synchronization of contracts supports only correlation by simple text attributes. That means, if you already have some existing contracts and you want to pair them with accounts on some new source system, you have to use some e xtended attribute of contracts which will contain the identifier usable for correlation. Specifically, the attribute mapped to the entity attribute **Owner (identity)** , can't be used as a correlation attribute, otherwise the result of the synchronization would be an Unknown state and the following exception:
-xtended attribute of contracts which will contain the identifier usable for correlation. Specifically, the attribute mapped to the entity attribute **Owner (identity)**  , can't be used as a correlation attribute, otherwise the result of the synchronization would be an Unknown state and the following exception:
 ''eu.bcvsolutions.idm.core.api.exception.CorrelationPropertyUnsupportedTypeException: Entity type [eu.bcvsolutions.idm.core.model.entity.IdmIdentityContract] and property [identity] has wrong type. Only String or UUID is supported now.''
-If you synchronize only new contracts from a source system, use simply the identifier as a correlation attribute.
+If you synchronize only new contracts from a source system, use simply the identifier as a correlation attribute and don't map the identifier to anything.
 ===== Tutorials =====