Yes for the attribute paths
if I already have the response mapping set to $.response.entityModels[*], then the attributes will look as following:
but it still does not do any trick when account aggregation kicks in.
What does the aggregation error say? If you click on the right where theres an “i”.
So you already have your root path set to $.response.entityModels[*] ?
I always had the root pat set to $.response.entityModels[*] .
If the root path is $.response.entityModels[*] , then we can only copy the rest separately. but it does not do the trick unfortunately. same thing happens.
Ah ok my bad then you had it correctly set up from the beginning
Are you not getting an entitlement on an account with only 1 role? If you skip the roles
I am getting everything correct when comes about entitlements or accounts from the target system. The issue is when I try to create new ones. This is the only issue I have.
Oh ok…
So you are not having an issue with Aggregation, but rather with Provisioning of accounts?
Have you set up an operation for Create Account?
Create account
body
{
“entityModel”: {
“name”: “$plan.name$”,
“type”: “user”,
“properties”: {
“firstName”: “$plan.firstName$”,
“lastName”: “$plan.lastName$”,
“email”: “$plan.email$”,
“roles”: [
“$plan.roles$”
]
}
}
}
response mapping
The account creation works fine until the account aggregation has to be started, so that the id for each user will be provided. Once the id of the user is provided, then the user is created on the target system. But once the aggregation is ran and the ID is provided to each user, then the entitlements (role) and ownershipdata disappear.
Hi
Have you tested this in the postman? Are you able to provision the accounts with entitlments from postman? And have you get it back and observed from postman?
Best Regards,
Siva.K
It looks like you have native change detection on the source that is deleting the entitlement?
This should not be the case. Is there a way we can pass the nativeidentity to see if we rcan overcome this error ?
Ohh, can you send the JSONBody you send for this request? You need to use $plan.nativeIdentity$ as placeholder to fetch the right username, else nothing works in Web Service Connectors I have found xD
I believe this is based on the create account operation. I am sending the nativeidentity within the getobject.
Get-object body
{
“params”: {
“query”: {
“filters”: {
“typesCriterion”: [
“$plan.nativeidentity$”
]
}
},
“fields”: {
“attributes”: [
“$._ALL$”
],
“relationships”: [
“$._ALL$”
]
}
}
}
Short update. I have noticed that the account gets created immediately, before the aggregation in the target system, however, the role and ownershipdata will not be populated at all, even though the logs show that they should have data.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.