Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Last revision Both sides next revision
tutorial:adm:systems_db_treenodes [2021/02/04 12:17]
soval 		tutorial:adm:systems_db_treenodes [2021/03/12 12:39]
apeterova parent and type
Line 81: Line 81:
 Fill "code, name, parent" as in the picture: Fill "code, name, parent" as in the picture:
  
-<note warning>Attribute parent has to be type String in IDM!!!</note>+<note warning>Attribute parent has to be type String in IDM! If it's e.g. java.lang.Integer or BigDecimal in the schema, use a transformation script from the system when mapping the attribute: 
 +<code>if (attributeValue != null) { 
 + return attributeValue.toString(); 
 +} 
 +return attributeValue;</code></note>
  
 {{ :tutorial:adm:sync_08.png |}} {{ :tutorial:adm:sync_08.png |}}
Line 99: Line 103:
  
 <note>Thank you for trying this tutorial, I hope it was useful.</note> <note>Thank you for trying this tutorial, I hope it was useful.</note>
 +
 +===== Troubleshooting =====
 +
 +==== The number of organizations is too low (when using parents) ====
 +
 +The synchronization processes only organizations, that have consistent values in the attribute **parent**. It means, that if the value in the attribute doesn't correspond to any **identifier** of any other organizations, such organization won't be processed at all by the synchronization. The only exception is the NULL value, which means that the organization is the root organization.
 +
 +Note that the values in the parent attribute must be the identifiers of the accounts. (That may be different from the codes of organizations in IdM.)
  • by apeterova