I’m really sorry, but this workaround seems not to work as expected.
So the best way, that the touchpointState is not overwritten on each TDI run is to comment out the fields in
Tested with the latest 7.0 fix
Some weeks ago I wrote about an workaround to prevent TDI from deleting the touchpoint status in HCL Connections.
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
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).
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