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

no update of attributes when importing entitlements

jugourta
New Contributor II
New Contributor II

Hello everyone, we are currently in the ombording process of an application on saviynt and in the entitlement part we are managing a data repository which can be imported from an API.
we encounter a problem when we modify, for example, in the API the description value of an entitlement, the latter is not updated at the end of the data import job at the level of the entitlement, however at the first launch we not encounter the problem when importing all the entitlements with their description values.

Please can you help ?  

I will attach the entitlementParams section of the ImportAccountEntJSON:

"entitlementParams":{
    "processingType":"SequentialAndIterative",
    "entTypes": {
        "CostCenter": {
            "entTypeOrder": 0,
            "call": {
                "call1": {
                    "callOrder": 0,
                    "connection": "userAuth",
                    "listField": "Outputs.CostCenter",
                    "keyField": "entitlement_value",
                    "http": {
                        "url": "http://demo0667338.mockable.io/ReferentialAOS",
                        "httpMethod": "POST",
                        "httpContentType": "application/x-www-form-urlencoded",
                        "httpParams": {
                            "scope":"standard_operations"
                        },
                        "httpHeaders": {
                            "Authorization": "${access_token}"
                           
                        }
                    },
                    "colsToPropsMap": {
                        "entitlementID": "#CONST#${String CostCenter=response.split(\",'\")[0].split(\"' :\")[1];return CostCenter.substring(2, CostCenter.length()-1)}~#~char",
                        "description": "#CONST#${String CostCenterDesc=response.split(\",'\")[1].split(\"' :\")[1];return CostCenterDesc.substring(2, CostCenterDesc.length()-1) }~#~char",
                        "customproperty2": "#CONST#${String CCPlant=response.split(\",'\")[2].split(\"' :\")[1];return CCPlant.substring(2, CCPlant.length()-2)}~#~char",
                        "entitlement_value": "#CONST#${String CostCenter=response.split(\",'\")[0].split(\"' :\")[1];return CostCenter.substring(2, CostCenter.length()-1)}~#~char",
                        "customproperty1":  "#CONST#FRANCE~#~char"

                    }
                }
            }
        }
    }
 }
6 REPLIES 6

Raghu
Honored Contributor
Honored Contributor

@jugourta  look like directly mapping entitlment list value to colsToPropsMap , need get via list those

sample check below:

"entitlementParams": {
"connection": "acctAuth",
"processingType": "SequentialAndIterative",
"entTypes": {
"Roles": {
"entTypeOrder": 0,
"call": {
"call1": {
"callOrder": 0,
"stageNumber": 0,
"http": {
"httpHeaders": {
"Authorization": "${access_token}",
"Accept": "application/json"
},
"url": "https://domain-test.coupahost.com/api/users?id=329 ",
"httpContentType": "application/json",
"httpMethod": "GET"
},
"listField": "roles",
"keyField": "entitlementID",
"colsToPropsMap": {
"entitlementID": "id~#~char",
"entitlement_value": "name~#~char",
"description": "description~#~char"
}
}
}

 


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

jugourta
New Contributor II
New Contributor II

we cannot directly use the mapping in the colsToPropsMap part we first do a parsing as indicated on the json because the API response returns us a list of strings and we use the same process in the account reconciliation part and it works very well even in this part of reconciliation of entitlements the first import is done well but it is the update which does not work.

rushikeshvartak
All-Star
All-Star

Please share postman screenshot and curl command [Refer https://codingnconcepts.com/postman/how-to-generate-curl-command-from-postman/ ]


⚠️‼️‼️Do not upload any attachments that contain sensitive information, such as IP Addresses, URLs, Company/Employee Names, Email Addresses, etc.‼️‼️⚠️


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

as indicated on the json we parse the API response because it returns us a list of strings as shown in the screenshot of the Postman response and we use the same process in the account reconciliation part and it works very well even in this part of reconciliation of entitlements the first import is done well but it is the update which does not work. and we have errors in the logs that I shared with you in the screenshot

[This message has been edited by moderator to mask sensitive info]

colsToProp is mandatory and this is similar to crowdstrike application which is currently not supported.

https://ideas.saviynt.com/ideas/EIC-I-5499


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

jugourta
New Contributor II
New Contributor II

hello, thank you for your reply but I don't understand why we manage to import the entitlements the first time with their description and the rest of the other attributes without error but the problem occurs when an entitlement is already imported and a modification has been made at the level of the api at this time the modification is not taken into account during reconciliation .

do you have an explanation for this problem?