Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

Secondary reconciliation field

Regular Contributor
Regular Contributor

Our HR import currently has been set to validate a number of attributes.

During the UserImport one of the CustomProperty attributes is being set to a concatenation of multiple fields (first name, last name, date of birth), which is then checked against the concatenation of attributes in the source system. For this we have our job set to use this CustomProperty as Reconciliation Field.

Because there is no Unique ID (yet) in our source system, we want to use the Saviynt UserKey as an additional reconciliation check:

- If user.CustomProperty64 is filled, use that as reconciliation check
- If user.CustomProperty64 is not filled, or if no match is found, check for the concatinated values (CustomProperty63)
- If the concatinated values (CustomProperty63) have no match, create a new Saviynt user

As far as I can see, there is only the option to select a single attribute from the Saviynt users to check. Is there any option to add an extra reconciliation check before this one?

If we just change reconciliation to the Saviynt UserKey, there will no longer be a check on the name and DoB, and if we add the Saviynt UserKey to the concatinated value there will not be any match as long as the UserKey has not been written back to the source system yet.

The main reason for doing this is so that HR can update the names and DoB if required (due to legal stuff for example)


Valued Contributor II
Valued Contributor II

@Marcel there can only be one unique recon field.


Reconciliation field can be only one. Please raise idea for multiple reconciliation field 

Rushikesh Vartak
If you find this response useful, kindly consider selecting 'Accept As Solution' and clicking on the 'Kudos' button.