Uploading Accounts and Associated Entitlements Using Schema Upload - LASTLOGONDATE

[Huddos]

Hi,

I am having issues with the LASTLOGONDATE within my csv file. I have tried a number of date and time formats in the CSV but none seem to update the LASTLOGONDATE of the account inserted or updated as part of the schema job. All other updates work ok. Example

accountname,endpointname,status,displayname,lastlogondate,customproperty31,role-adhoc-searchhead
xx@abc.com,splunk,1,Blogs Joe,03-Oct-2024 02:20:54,xx@abc.com,corp

Any ideas?

[rushikeshvartak]

Did you checked logs

[prtkrh007]

Please check on the logs and also try this 
'2024-03-01 08:31:00'

[Huddos]

That format did not work, see above reply, thanks

[Huddos]

I'm only seeing this with no mention of lastlogondate found in sav file

2024-10-23T07:17:43+10:00-ecm-worker-services.ImportUtilityService-quartzScheduler_Worker-1-wnls6-DEBUG-Setting Batch Size from config = 500

2024-10-23T07:17:43+10:00-ecm-worker-services.ImportReqsysDataService-quartzScheduler_Worker-1-wnls6-DEBUG-OVERWRITE_USER_ASSIGNED = true

2024-10-23T07:17:43+10:00-ecm-worker-services.ImportReqsysDataService-quartzScheduler_Worker-1-wnls6-DEBUG-ACCOUNT_NOT_IN_FILE_ACTION = NOACTION

2024-10-23T07:17:43+10:00-ecm-worker-services.ImportReqsysDataService-quartzScheduler_Worker-1-wnls6-DEBUG-IGNOREFIRSTLINE = YES

2024-10-23T07:17:43+10:00-ecm-worker-services.ImportReqsysDataService-quartzScheduler_Worker-1-wnls6-DEBUG-delimiter = ,

2024-10-23T07:17:43+10:00-ecm-worker-services.ImportReqsysDataService-quartzScheduler_Worker-1-wnls6-DEBUG-FILEIMPORTDELIMETER = ,

2024-10-23T07:17:43+10:00-ecm-worker-services.ImportReqsysDataService-quartzScheduler_Worker-1-wnls6-DEBUG-CORRELATEINACTIVEACCOUNTS = FALSE

2024-10-23T07:17:43+10:00-ecm-worker-services.ImportReqsysDataService-quartzScheduler_Worker-1-wnls6-DEBUG-ACCOUNTNAME found in SAV file

2024-10-23T07:17:43+10:00-ecm-worker-services.ImportReqsysDataService-quartzScheduler_Worker-1-wnls6-DEBUG-ENDPOINTNAME found in SAV file

2024-10-23T07:17:43+10:00-ecm-worker-services.ImportReqsysDataService-quartzScheduler_Worker-1-wnls6-DEBUG-STATUS found in SAV file

2024-10-23T07:17:43+10:00-ecm-worker-services.ImportReqsysDataService-quartzScheduler_Worker-1-wnls6-DEBUG-DISPLAYNAME found in SAV file

2024-10-23T07:17:43+10:00-ecm-worker-services.ImportReqsysDataService-quartzScheduler_Worker-1-wnls6-DEBUG-CUSTOMPROPERTY31 found in SAV file

[rushikeshvartak]

Share your sav file

[Huddos]

Not sure how Saviynt developers expect users to make the correct mapping here when the accounts table clearly says LASTLOGONDATE :).

As lastlogondate was not detected in logs I tried comments instead and it populated the data. I then tried (pure guess)

accountname,endpointname,status,displayname,lastlogindate,customproperty31,role-adhoc-searchhead

Saviynt detected lastlogin in logs and populated the LASTLOGONDATE which displayed in SAV gui/portal for the accounts.

I then changed to

accountname,endpointname,status,displayname,lastlogin,customproperty31,role-adhoc-searchhead

and that also worked. 

[rushikeshvartak]

So lastlogin is working ?

[Huddos]

Correct, it is now populating with the correct date however time is 00:00:00.

[rushikeshvartak]

What is working date format

[Huddos]

As example 11-Oct-2024 02:20:54 is working for the date but time is imported as 00:00:00

[rushikeshvartak · Accepted solution]

Hi @Huddos  Below is working format 2024-10-11 02:20:54

I have validated this 

Also below are columns supported 

• ACCOUNTNAME
  USERNAME
  LASTLOGIN
  ENDPOINTNAME
  VALIDFROM
  DESCRIPTION
  VALIDTHROUGH
  COMMENTS
  STATUS
  ACCOUNTTYPE
  CUSTOMPROPERTY1
  CUSTOMPROPERTY2
  CUSTOMPROPERTY3
  CUSTOMPROPERTY4
  CUSTOMPROPERTY5
  DISPLAYNAME
  ACCOUNTID
  ACCOUNTCLASS
  CREATED_ON
  CREATOR
  ORPHAN
  PRIVILEGED
  TOTALUSAGE
  UPDATEUSER
  UPDATEDATE
  USERGROUP
  USERLOCK
  CUSTOMPROPERTY31
  INCORRECTLOGONS
  LASTPASSWORDCHANGE
  PASSWORDCHANGESTATUS
  PASSWORDLOCKDATE
  ENTITLEMENTVALUE

[Huddos]

Awesome, that date/time format is working for my instance also. Thanks for validating and confirming supported columns.