User id is the AccountID of the source, when passed directly in the create account body in and provisioning plan line$plan.userId$ , the request failed, so had to create another variable empid in create policy and pass in the plan $plan.empid$ and now while trying to map the userid in the create response mapping its not working though the API is returning userID. In the create account completed request .
Is there any way I can pass userid in the provisioning plan directly and keep it as accountid in the schema as well .thanks
Can you please share the create account form
Are you mapping any identity attribute for user id in create form or any transform for calculating the value
Just for testing pass static value for user id in create form if that works
Then issue with populating value
Have you tried to replicate the issue in Postman? Were you able to create account in target just by passing “userID“ in the body? Doesn’t it require any other attributes to be passed?
How the response body look like when you try to create the account using postman? I doubt this is because of response mapping. Make sure you give correct root path and attribute name in response mapping.
Hi @SrideviJaya ,
First, in create account define the mapping like for userId account attribute, mapping should be empId identity attribute.
now, in the create account pass like
{
“userId”: “$plan.userId$”
}
Make sure there is No comma after “$plan.userId$” and in Account Schema userId is account id.
Createaccount is working fine , along with userid other attributes are being passed.
When $plan.userid$ is being set its not going through, instead $plan.nativeIdentity $ is working my issue is userid is not being mapped back as part of create account response though the response mapping is configured.
Hi
Make sure the data type of userId is defined correctly in Account Schema.
Also try using response mapping as $.userId as attribute path and leave root path as empty
