Some weeks ago I wrote about an workaround to prevent TDI from deleting the touchpoint status in HCL Connections.
During some research on TDI I found Mapping fields manually in the HCL Connections documentations. This document describes how to add additional fields to the TDI synchronisation. On point 11 I found something new for me. You can add additional fields and then add the content with an Javascript function for example.
Then TDI does not make an LDAP call to get the attribute from there, instead it uses the function. So an additional workaround for the Touchpoint state problem is to add the five fields defined in conf/LotusConnections-conf/tdi-profiles-config.xml
to map_dbrepos_from_source.properties
and set it to null. Setting attributes to null does not delete the content in the database, but just does nothing (no update, no creation).
map_dbrepos_from_source.properties
extattr.recommendedTags=null
extattr.departmentKey=null
extattr.privacyAndGuidelines=null
extattr.touchpointState=null
extattr.touchpointSession=null
That’s way easier than commenting out the field definitions and if you ever need to set the fields, you can just add the attribute or function to map_dbrepos_from_source.properties
.