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

Date Unparseable error during user import via Actionable Analytics

jralexander137
New Contributor III
New Contributor III

Hi. I have the following userImport Config:

{
"connection": "userAuth",
"successResponses": {
"statusCode": [
200,
201,
202,
203,
204,
205
]
},
"url": "https://removed-dev.saviyntcloud.com/ECM/api/v5/fetchRuntimeControlsData",
"httpParams": "{\"analyticsname\": \"DUO Update Last Login\"}",
"httpMethod": "POST",
"httpHeaders": {
"Authorization": "${access_token}"
},
"httpContentType": "application/json",
"userResponsePath": "result",
"colsToPropsMap": {
"systemUserName": "NAME~#~char",
"customproperty50": "DATE~#~string"
},
"pagination": {
"offset": {
"offsetParam": "offset",
"batchParam": "displaycount",
"batchSize": 500,
"totalCountPath": "completeResponseMap.total"
}
}
}

The problem is that I keep seeing the following error in the logs when running the user import: 

"2024-06-13T12:53:27.781+00:00","ecm","services.SaviyntCommonUtilityService","http-nio-8080-exec-24-99k6w","DEBUG","contentType - text/json"
"2024-06-13T12:53:27.782+00:00","ecm","services.SaviyntCommonUtilityService","http-nio-8080-exec-24-99k6w","DEBUG","contentTypeFromConfig - application/json"
"2024-06-13T12:53:27.846+00:00","ecm","analytics.AnalyticsHistoryService","http-nio-8080-exec-5-99k6w","DEBUG","Inside retrieveColumnsAndFilters"
"2024-06-13T12:53:27.846+00:00","ecm","analytics.AnalyticsHistoryService","http-nio-8080-exec-5-99k6w","DEBUG","returnMap:: [leftFilterWithDefaultFeildList:[], columnAndTypeMap:[DATE:1, NAME:1], selectedFilterCols:[NAME, DATE], selectedCols:[NAME###1, DATE###1]]"
"2024-06-13T12:53:27.846+00:00","ecm","analytics.AnalyticsHistoryService","http-nio-8080-exec-5-99k6w","DEBUG","Exit retrieveColumnsAndFilters"
"2024-06-13T12:53:27.847+00:00","ecm","analytics.AnalyticsHistoryController","http-nio-8080-exec-5-99k6w","DEBUG","result list size 657"
"2024-06-13T12:53:26.691+00:00","ecm","analytics.AnalyticsHistoryService","http-nio-8080-exec-7-99k6w","ERROR","Unparseable date: "2024-04-17""
"2024-06-13T12:53:26.691+00:00","ecm","analytics.AnalyticsHistoryService","http-nio-8080-exec-7-99k6w","ERROR","Unparseable date: "2023-10-25""
"2024-06-13T12:53:26.691+00:00","ecm","analytics.AnalyticsHistoryService","http-nio-8080-exec-7-99k6w","ERROR","Unparseable date: "2023-05-12""
"2024-06-13T12:53:26.691+00:00","ecm","analytics.AnalyticsHistoryService","http-nio-8080-exec-7-99k6w","ERROR","Unparseable date: "2024-06-03""
"2024-06-13T12:53:26.691+00:00","ecm","analytics.AnalyticsHistoryService","http-nio-8080-exec-7-99k6w","ERROR","Unparseable date: "2024-05-20""
"2024-06-13T12:53:26.691+00:00","ecm","analytics.AnalyticsHistoryService","http-nio-8080-exec-7-99k6w","ERROR","Unparseable date: "2024-06-06""
"2024-06-13T12:53:26.692+00:00","ecm","analytics.AnalyticsHistoryService","http-nio-8080-exec-7-99k6w","ERROR","Unparseable date: "2023-05-19""
"2024-06-13T12:53:26.692+00:00","ecm","analytics.AnalyticsHistoryService","http-nio-8080-exec-7-99k6w","ERROR","Unparseable date: "2024-06-07""
"2024-06-13T12:53:26.692+00:00","ecm","analytics.AnalyticsHistoryService","http-nio-8080-exec-7-99k6w","ERROR","Unparseable date: "2024-05-10""
"2024-06-13T12:53:26.692+00:00","ecm","analytics.AnalyticsHistoryService","http-nio-8080-exec-7-99k6w","ERROR","Unparseable date: "2024-06-07""
"2024-06-13T12:53:26.692+00:00","ecm","analytics.AnalyticsHistoryService","http-nio-8080-exec-7-99k6w","ERROR","Unparseable date: "2024-06-07""
"2024-06-13T12:53:26.692+00:00","ecm","analytics.AnalyticsHistoryService","http-nio-8080-exec-7-99k6w","ERROR","Unparseable date: "2023-05-08""

When I execute the adv analytics standalone the time stamps look fine:

jralexander137_0-1718283478406.png

Any thoughts on why this error is occuring and how to fix it?

 

EDIT: Selected wrong sav version, proper sav version is 24.3. Issues still persists

4 REPLIES 4

rushikeshvartak
All-Star
All-Star

Don’t keep column name as date 

change to dat and try


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

This gives a slightly different result. Also, I accidentally selected the wrong minor version on post submission, environment is 24.3 not 24.5.

I see a bunch of errors like this now:

"2024-06-13T17:22:10.301+00:00","ecm-worker","rest.RestProvisioningService","quartzScheduler_Worker-7-qchg6","ERROR","Missing username for the record : [NAME:blane, DAT:2024-06-07]"
"2024-06-13T17:22:10.301+00:00","ecm-worker","rest.RestProvisioningService","quartzScheduler_Worker-7-qchg6","ERROR","Missing username for the record : [NAME:agarvin, DAT:2023-12-07]"

Analytics is being executed and results returned but not updating to user records now.

 

{
"connection": "userAuth",
"successResponses": {
"statusCode": [
200,
201,
202,
203,
204,
205
]
},
"url": "https://removed-dev.saviyntcloud.com/ECM/api/v5/fetchRuntimeControlsData",
"httpParams": "{\"analyticsname\": \"DUO Update Last Login\"}",
"httpMethod": "POST",
"httpHeaders": {
"Authorization": "${access_token}"
},
"httpContentType": "application/json",
"userResponsePath": "result",
"colsToPropsMap": {
"systemUserName": "NAME~#~char",
"customproperty50": "DAT~#~char"
},
"pagination": {
"offset": {
"offsetParam": "offset",
"batchParam": "displaycount",
"batchSize": 500,
"totalCountPath": "completeResponseMap.total"
}
}
}

username is mandatory column for API

 

{
"connection": "userAuth",
"successResponses": {
"statusCode": [
200,
201,
202,
203,
204,
205
]
},
"url": "https://removed-dev.saviyntcloud.com/ECM/api/v5/fetchRuntimeControlsData",
"httpParams": "{\"analyticsname\": \"DUO Update Last Login\"}",
"httpMethod": "POST",
"httpHeaders": {
"Authorization": "${access_token}"
},
"httpContentType": "application/json",
"userResponsePath": "result",
"colsToPropsMap": {
"username": "NAME~#~char",
"customproperty50": "DAT~#~char"
},
"pagination": {
"offset": {
"offsetParam": "offset",
"batchParam": "displaycount",
"batchSize": 500,
"totalCountPath": "completeResponseMap.total"
}
}
}


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

Raghu
All-Star
All-Star

@jralexander137 

try below

"pagination": {
"offset": {
"offsetParam": "offset",
"batchParam": "max",
"batchSize": 500,
"totalCountPath": "completeResponseMap.total"
}

 

Thanks,
Raghu
If this reply answered your question, Please Accept As Solution and hit Kudos.