User import via Database connector

[Ankky]

Hello experts,

We have a database as the authoritative source and this DB can have multiple rows for a single user as shown below. 

EmployeeId	Type	Status	Department
123	Employee	Active	emp_dept
123	CWR	Active	CWR_dept
123	Employee	Inactive	emp_dept1

We want to update the user information in Saviynt based on precedence set by the business requirements. In the above example, we want to set the user's department as "emp_dept".  But it seems that the database connector processes the rows one by one and if it encounters the same unique attribute again which is employeeid here, then it overwrites the previous row attributes. Can we achieve this somehow in the inline preprocessing? 

We cannot keep multiple fields as the number of rows aren't fixed.

Thanks

[Dhruv_S]

Hi @Ankky 

Could you please provide additional details about the conditions based on which you want to process the department name? 

It is expected behavior that when you will try to input a new value in a single-valued attribute, it will override the previous value.

Regards,

Dhruv Sharma

[Ankky]

Hello @Dhruv_S 

In the above example, Employee type with Active status should take precedence over CWR with Active status or Employee with Inactive status. 

How can we process multiple rows via DB connectors which are linked to same identity? Essentially, we need to get a clear picture of all the attributes/rows coming from Database for an identity before deciding the final field values.

 Regards,

Ankky

[Dhruv_S]

Hi @Ankky 

In this scenario, you want to process and merge multiple records into a single record based on some conditions before it is imported to Saviynt.

Using inline pre-processor, we can modify the columns/attributes of a particular record at the time of import in Saviynt. During the import, Saviynt will accept one record for a particular employee id and inline processing queries will be able to modify that particular record. It seems it is not possible to achieve this using merge query too in the pre-processor. However, if you have a working query to merge the record, you can try once in PREPROCESSQUERIES.

Regards,
Dhruv Sharma
If the response is helpful, please click Accept As Solution and kudos it.