Hi iamology,
This is an interesting idea that might be able to work, but I’d have to think about it some more. For this connector, we are also using the Reverse Entitlement Aggregation rule to correlate groups and users. The groups endpoint returns the accountIds for each member of the group and that is being compared to the user accountIds to do the entitlement association. With this setup, we can’t really change the accountId in the schema because this correlation rule won’t work as expected. We previously had a second child aggregation that ran that would do individual user membership operations, but there were performance issues with the Udemy API that led us to the Reverse Entitlement Aggregation rule.
This is a good idea though and I’ll do some testing to see if something along these lines can work in conjunction with our existing After Operation rule.
Thank you,
- Zach