Hmmm. This should be possible, but might be dependent on how you configured your parent and child account aggregations. Let me share an example of a similar scenario that I encountered and maybe it will help you spot any differences you might have in your configuration.
I am working on a web service connector for this very community forum, which runs on Discourse. I need to aggregate all SailPoint accounts in the forum so I can track and manage SailPoint employee’s access to this forum. The API for Discourse provides a list endpoint to get all accounts, and I can use this to get each account’s id, username, and title. However, this list endpoint doesn’t return the email address for each account. To get the email address, I have to call the get single user endpoint, which returns a lot more information about each user, including their email address.
To implement this in IdentityNow, I have to create two Account Aggregation operations. The parent aggregation will use the list endpoint to get all accounts and their basic attributes. It has the following configuration in the UI:
The response from the list endpoint looks like this:
[
{
"id": 10921,
"username": "john.doe",
"avatar_template": "https://avatars.discourse-cdn.com/v4/letter/s/b28a4f/{size}.png",
"active": true,
"admin": true,
"moderator": false,
"last_seen_at": "2021-08-31T13:41:46.161Z",
"last_emailed_at": "2021-09-28T15:57:50.727Z",
"created_at": "2021-08-17T14:16:07.856Z",
"last_seen_age": 2520721.489948948,
"last_emailed_age": 93356.923058227,
"created_at_age": 3728259.794119657,
"trust_level": 4,
"manual_locked_trust_level": null,
"flag_level": 0,
"title": "Developer Relations Team",
"time_read": 394,
"staged": false,
"days_visited": 6,
"posts_read_count": 10,
"topics_entered": 4,
"post_count": 0,
"akismet_state": null
},
...
]
The child aggregation will use $response.id$ to call the single user endpoint for every account that was returned by the parent. It has the following configuration:
