I’m working on setting up entitlement aggregation on a webservices source in my tenant and have been struggling on how to configure it properly.
The scenario I’m dealing with is that the users endpoint doesn’t contain any of the entitlement data. Instead, I have to setup a child operation to the entitlement aggregation where each group pulled back by the primary aggregation is called again in the child to pull all the users who are assigned to that group.
The child call looks like this:
The response is just a list of accounts that are a member of the group.
What I’m struggling with is how to configure the response mapping so the entitlement is assigned to the account. I tried setting this up both as a group aggregation and as an account aggregation.
In my group aggregation, I didn’t have a response mapping configured because, as far as I know, there isn’t a “members” attribute on an entitlement and it doesn’t look like I can create one.
In my account aggregation, I tried having the groups attribute mapped to $response.id$ with the root configured as $.items to try and map each account returned to the entitlement that was being queried but that didn’t work either.
Has anyone else ever done something like this that could point me in the right direction?