and more in a single search tool across platforms. Read the announcement here. |
07/25/2023 08:52 AM
07/25/2023 10:01 AM
Hi @ChrisBellobuono ,
Did you added incremental recon configurations in User Import XML? Can you share the user import xml, you are using. Also, share the field which will hold the update date in the target DB.
07/26/2023 06:06 AM
If you are referring to this section of USERIMPORT:
<importsettings>
<zeroDayProvisioning>false</zeroDayProvisioning>
<generateEmail>false</generateEmail>
<userNotInFileAction>NOACTION</userNotInFileAction>
<checkRules>false</checkRules>
<buildUserMap>false</buildUserMap>
<generateSystemUsername>false</generateSystemUsername>
<userOperationsAllowed>CREATE OR UPDATE</userOperationsAllowed>
<userReconcillationField>USERNAME</userReconcillationField>
</importsettings>
Then yes, it is set.
07/26/2023 06:17 AM - edited 07/26/2023 06:18 AM
Hi @ChrisBellobuono ,
Can you follow below steps and try.
1. Make sure, you fetching column/field (UPDATED_DATE ) from target in select statement present in user import xml.
2. dateformat and incrementalcolumn should be present as an attribute under mapper tag as below. incrementalcolumn value should be the target column holding updatedate:
<mapper description="This is the mapping field for Saviynt Field name" dateformat="timestamp" incrementalcolumn="UPDATED_DATE">
3. Map the target field holding recent update date in updatedate column of user like below:
<mapfield saviyntproperty="updatedate" sourceproperty="UPDATED_DATE" type="date"></mapfield>
07/28/2023 09:12 AM
I had it that way once before except mine had the defaultrole="" in mapper. Unfortunately, I get the same result without it.
07/25/2023 01:05 PM
The incremental import woks on the last update date of the user. In case you are setting the update date as current date by default in your query, it may not be able to identify the user. Is there a field in the target DB that does store the actual update value?
07/26/2023 06:10 AM
Yes, there is, but as I stated we do not have write access to the client DB so to avoid constantly going to them to make changes each time we test, we forced the SQL to fake the date. That said, we have tried this for that field as well:
to_timestamp(trim(UPDATED_DATE), 'YYYY-MM-DD HH:MI:SS') as updatedate,
Where UPDATED_DATE is the DB column name containing when each user's record was last updated.
07/26/2023 09:21 AM
can you hardcode the update_date field value to a date in the past and then try your incremental import job.
07/28/2023 09:32 AM
I tried both of these:
'2023-07-28 16:18:43' AS UPDATED_DATE
to_timestamp('2023-07-28 16:18:43', 'YYYY-MM-DD HH:MI:SS') as UPDATED_DATE
Neither worked. Do the timestamps need to be in a particular format for this to work?
07/29/2023 07:00 AM
Just give date and try
09/08/2023 11:29 AM
Per support's request, I am posting an updated summary of where we are.
Our current configuration:
When we run the incremental update job (Users Import (Incremental) from Database (UserImportIncrementalJob)) the statistics always show that all users (almost 7k) have been updated. This happens regardless of whether or not we include the above Map Field or if it is mapped to updatedate or some random Custom Property.
We wrote a report to list all the users that have been recently updated and it always lists all users after the incremental job is run with SAVUPDATEDATE showing the current timestamp.
select u.username, u.Firstname, u.Lastname, u.CREATEDATE , u.SAVUPDATEDATE from users u where u.CUSTOMPROPERTY20 = 'XXXXXX' AND DATEDIFF(NOW() ,SAVUPDATEDATE) < 3
When we pick any of those users at random and look at their update history nothing shows up for the current date:
We are not sure what the problem is.
Also, we were on version 23.4 when we first reported the problem and are now on 23.8.
09/08/2023 05:04 PM
Can you share full xml
09/11/2023 07:39 AM