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

Account having multiple Entitlement mapping in a comma separated string format. reconciling issue

rituparna_pwc
Regular Contributor
Regular Contributor

Hi All,

I have below issue while i am importing entitlements and accounts. I am able to import entitlements and accounts along but facing issue with AccounttoEnt mapping.  target application is having user with multiple entitlements in comma separated value for single role as below. When user is having multiple entitlements in comma separated value, the account to entitlement mapping is not happening. I am pasting the ImportAccountEntJSON we are trying

Payload:

{
    "Users": [
        {
            "EmployeeID""Sav1010",
            "EmployeeName""Sav1010",
            "EmailAddress""Sav1010@test.com",
            "MobileNumber"null,
            "Country""IN",
            "StatusCode""A",
            "LastLoginTime"null,
            "DepartmentName"null,
            "DesignationCodes": "YREBPIXXXXXXXSG:LEASING_MGR,SaviyntTesting"
        }
    ]
}

ImportAccountEntJSON

{
   "accountParams": {
     "connection": "userAuth",
"includeExistingInActiveAccounts": true,
     "processingType": "SequentialAndIterative",
     "call": {
       "call1": {
"callOrder": 0,
"stageNumber": 0,
"http": {
 
"httpHeaders": {
"Authorization": "${access_token}"
},
"httpContentType": "application/json",
"httpMethod": "GET"
},
"listField": "Users",
"keyField": "accountID",
"colsToPropsMap": {
"accountID": "EmployeeID~#~char",
"name": "EmployeeID~#~char",
"status": "StatusCode~#~char",
"lastlogondate": "LastLoginTime~#~char",
"customproperty2": "DepartmentName~#~char",
"customproperty1": "EmployeeName~#~char",
"customproperty4": "EmailAddress~#~char",
"customproperty5": "MobileNumber~#~char",
"customproperty6": "DesignationCodes~#~char",
"customproperty7": "StatusCode~#~char",
"customproperty8": "Country~#~char",
"customproperty31": "STORE#ACC#ENT#MAPPINGINFO~#~char"
}
}
     },
 
"acctEntMappings": {
"Designations": {
"listPath": "${List designationcodes=customproperty6.split(',');return designationcodes}",
"idPath": "",
"keyField": "entitlementID"
}
}
   },
   "entitlementParams": {
     "connection": "userAuth",
     "processingType": "SequentialAndIterative",
     "entTypes": {
       "Designations": {
         "entTypeOrder": 0,
         "call": {
           "call1": {
"connection": "userAuth",
             "callOrder": 0,
             "stageNumber": 0,
             "http": {
               "httpHeaders": {
                 "Authorization": "${access_token}"
               },
              "httpContentType": "application/json",
"httpMethod": "GET"
             },
             "listField": "Designations",
             "keyField": "entitlementID",
             "colsToPropsMap": {
               "entitlementID": "DesignationCode~#~char",
               "entitlement_value": "DesignationCode~#~char",
   "displayname": "DesignationCode~#~char",
   "description": "DesignationName~#~char"
             },
"disableDeletedEntitlements": true
           }
         }
       }
     }
   },
   "acctEntParams": {
"processingType": "acctToEntMapping"
}
 }
[This message has been edited by moderator to mask url]
2 REPLIES 2

nimitdave
Saviynt Employee
Saviynt Employee

@rituparna_pwc , no comma separated entitlement values are not supported in rest connector for account to entitlement mappings.

@nimitdave , thanks but is there a way to split this value in import json? The target system cannot make any changes