Compliance Kit - User Synchronization with Existing Object

The purpose of the User Synchronization module is to create and update Employee objects based on M-Files login account and user information, so I don't think it fits your use case if I understood it correctly. You can read the full module description in Compliance Kit - User Synchronization Module - Functional Description.

If you still want to test it, you'll need to set the aliases in your metadata structure as described in the functional description and Compliance Kit - Configuration Manual so User Synchronization can use the existing elements in your vault. For instance, the Employee class needs to have alias M-Files.UserSynchronization.User and the M-Files user account property alias M-Files.UserSynchronization.UserName.

Thank you Joonas! I think I misunderstood the point of the User Synchronization module then. If we do have existing "Employee" records with a string formatted to match that of the login account, is there a way to auto-calculate it? I'm not seeing the option to search from the Users value list specifically using Property Calculator or Managed Properties but not sure if I'm missing something obvious.

Thank you Joonas! I think I misunderstood the point of the User Synchronization module then. If we do have existing "Employee" records with a string formatted to match that of the login account, is there a way to auto-calculate it? I'm not seeing the option to search from the Users value list specifically using Property Calculator or Managed Properties but not sure if I'm missing something obvious.

This may require a bit of custom development since the information is found in two places: the vault users (which you can access via the Users value list) refer to the login accounts where you have the actual AD login. Depending on the hosting environment the login accounts may reside on the server level or the vault level which adds another variable.

I recommend contacting your M-Files representative if you need help setting this up as there are a couple of factors to consider here.

I see! I appreciate your insight, thanks again