03/14/2023 01:22 AM
For performing Incremental import of Users from MS SQL server database, do we need to map the incremental column of the DB table to a Saviynt property/attribute?
In the DB Connector guide for User Import parameter, it is mentioned as :
<mapper description="This is the mapping field for Saviynt Field name" dateformat="timestamp" incrementalcolumn="updatedate">
<mapfield saviyntproperty="updatedate" sourceproperty="updatedate" type="date"></mapfield>
As we are running out of available customproperty, we don't want to map the source property of update date to any Saviynt property , will it cause any issue? Will it not be able to perform the incremental import?
Solved! Go to Solution.
03/14/2023 01:49 AM
Yes, no need to map the updatedate column from source db to saviynt columns.
Here updatedate column should be present in the target db table.
03/14/2023 08:56 AM
Thanks nimita, appreciate your quick response.
03/29/2023 05:54 AM
Hi @nimitdave circling back on the above query,
I tried to perform the incremental import with the last update timestamp not being changed in the source DB for the User but the User update/change from DB did get imported and reflected as part of the incremental import in Saviynt. Could you please confirm how Saviynt performed this incremental import without the update timestamp being changed. Does it track other value changes as well, what is the use of last update timestamp field then?
04/03/2023 12:49 PM
Saviynt will only check for the last update date in case of Incremental and no other field changes. Only the records that were updated post the last job run time will be fetched.
Can you check for the DB query in the logs that was executed when you ran the incremental import. This will help identify what the issue could be
04/05/2023 03:02 AM
So, the last update date field needs to be mapped to a Saviynt attribute in order for the incremental import to work correctly by importing any changes that occurred in those records post the date timestamp value stored in that attribute?
04/05/2023 02:53 AM
Hi @sahil , I did a few more tests using different values/ways and found that when the Last Update date property is mapped to a Saviynt property and stored in one of the attributes, the Incremental Import job is working as below:
If there is a change in the last update date value to a later date, incremental import job is able to fetch the updates but if we manually update the last update date field in DB to a prior date then the incremental import job does not fetch the changes into Saviynt.
If the last update date field from DB is not mapped or stored into Saviynt, for any updates or changes in any of the DB values, the incremental import fetches the change into Saviynt irrespective of the value of last update date not being changed.
Please let me know if the above observation is correct or not. Thanks.
04/05/2023 04:22 AM
Yes and also it considers the data for last successful run in addition to above.
04/05/2023 04:37 AM
Hi @nimitdave Could you please clarify a bit more on how it considers the data additionally? Does it track the changes in the values of the other fields apart from the last update date? I did try to change the value of a few fields without changing the last update date, but the incremental import did not fetch the updates to Saviynt when we had the last update timestamp value from DB mapped and stored in Saviynt attribute.
04/11/2023 10:38 AM
The incremental will only check for last update date to fetch the records. And any changes made to these records fetched is updated in Saviynt based on the attribute mapping defined in your config.
If the incremental import is not pulling the records based on the last update date, I would suggest to check the DB query that runs in the logs when you start the job.