REST Connector : Receiving Null Response with dynamic attributes/User attributes.

[Madan]

Hi Team,

We are trying to provision  Account through REST connection using Dynamic attributes.

We are getting below null response from REST call, but if we hardcode the dynamic attribute values in JSON, provisioning call is getting processed successfully and accounts are getting created. 

----------------

{"auditDetails":{"call1":[{"headers":null,"message":"","statusCode":null,"description":null,"status":"Failed"}]},"call1":{"headers":null,"message":"","statusCode":null,"description":null,"status":"Failed"}}

-------------

[quartzScheduler_Worker-8] ERROR rest.RestProvisioningService - Call response: null
[quartzScheduler_Worker-8] ERROR rest.RestProvisioningService - header: null
[quartzScheduler_Worker-8] ERROR rest.RestProvisioningService - callResponseMap: [:]

----------------------------------------

Create Account json is configured as  below.

########################

{
"accountIdPath": "call1.message.UserRoleDataAssignmentId",
"responseColsToPropsMap": {
"accountID": "call1.message.UserRoleDataAssignmentId~#~char"
},
"call": [
{
"name": "call1",
"connection": "acctAuth2",
"url": "https://xyzxyzxyzxyzzzz.com/fscmRestApi/resources/11.13.18.05/dataSecurities",
"httpMethod": "POST",
"httpParams": "{\"SecurityContext\":\"${requestAccessAttributes.get('CONTEXT')}\",\"SecurityContextValue\":\"${requestAccessAttributes.get('VALUE')}\",\"RoleCommonName\":\"${requestAccessAttributes.get('ROLE')}\",\"UserName\":\"${user.employeeid}\"}",
"httpHeaders": {
"Authorization": "${access_token}"
},
"httpContentType": "application/vnd.oracle.adf.resourceitem+json",
"successResponses": {
"statusCode": [
200,
201,
204
]
},
"unsuccessResponses": {
"statusCode": [
400,
403,
401,
409,
501,
500
]
}
}
]
}

#################################

Any inputs/suggestion regarding above issue will be of great help.

Thanks and Regards,

Madan 

[rushikeshvartak]

Syntax is correct. Are you storing dynamic attribute value to accounts columns ?

[Madan]

Hi Rushikesh

Thanks for the response!

Yes, they are going to account columns.
It is working when we try with hardcoded values instead of variables?( tried url encoding $ with %24 in httpParams, but still giving null response ).

Thanks and Regards,

Madan J Y

[rushikeshvartak]

correct syntax is ${requestAccessAttributes.get('customptproperty1')}

Example : ROLE dynamic attribute is getting stored in CP1