# Web Services Connector Source Unable to Display Entitlements **URL:** \ **Category:** SHF Discussion and Questions\ **Tags:** sailpoint-identity-security, aggregation\ **Created:** [September 9, 2026, 3:52pm UTC](https://developer.sailpoint.com/discuss/t/web-services-connector-source-unable-to-display-entitlements/222068 "2026-09-09T15:52:51Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![abhijit\_shekki](https://avatars.discourse-cdn.com/v4/letter/a/edb3f5/32.png) [@abhijit\_shekki](https://developer.sailpoint.com/discuss/u/abhijit_shekki)\ **Post date:** [September 9, 2026, 3:52pm UTC](https://developer.sailpoint.com/discuss/t/web-services-connector-source-unable-to-display-entitlements/222068/1 "2026-09-09T15:52:52Z")
Hi everyone, I’ve created a **Web Services Connector source** and configured both **Account Aggregation** and **Group Aggregation** operations. The two operations use different API endpoints. In the **Account Schema** , I’ve added an attribute (`RoleId`) for entitlements and configured it as: - Type: **Group** - Entitlement: **Enabled** - Multi-Valued: **Enabled** The **Group Schema** contains `OrgId` and `RoleId`, with the `RoleId` attribute configured as the **Entitlement ID** and **Entitlement Name**. I’ve also configured an **After Operation Rule** for Group Aggregation to build a custom entitlement using a prefix and subsequently map it to the account entitlement attribute. The Group Aggregation API returns a response similar to: `{data=[{OrgId=Org, RoleId=Org_role}]}` The response mapping is configured as: - Root Path: `$.data` - `OrgId` → `$.OrgId` - `RoleId` → `$.RoleId` Both `OrgId` and `RoleId` are included in the Group Schema. When I run the Group Aggregation, the aggregation completes and shows that records were successfully scanned. However, the **Entitlements** page continues to display **0 entitlements**. Is there anything missing in the schema, response mapping, entitlement ID configuration, or aggregation setup that would prevent the scanned group records from being created and displayed as entitlements? Thanks, Abhijit ---
**Author:** ![Gopi2000](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/gopi2000/32/21706_2.png) [@Gopi2000](https://developer.sailpoint.com/discuss/u/Gopi2000)\ **Post date:** [September 9, 2026, 3:56pm UTC](https://developer.sailpoint.com/discuss/t/web-services-connector-source-unable-to-display-entitlements/222068/2 "2026-09-09T15:56:50Z")
Hi @abhijit_shekki , If the entitlement count is showing as successfully scanned during the Group Aggregation, but the entitlements are not immediately visible on the **Entitlements** page, it could potentially be a caching or UI refresh issue that may take some time to reflect. One way to confirm whether the entitlement has actually been aggregated into ISC is to open a **Role → Edit → Manage Access → Add Access** and search for the entitlement by name. If the entitlement appears there, it confirms that the entitlement has been successfully aggregated into ISC and is just taking some time to appear on the Entitlements page. I’ve faced a similar issue with a few connectors, where the entitlements took some time to reflect on the Entitlements page even though the aggregation was successful. ---
**Author:** ![baoussounda](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/baoussounda/32/13095_2.png) [@baoussounda](https://developer.sailpoint.com/discuss/u/baoussounda)\ **Post date:** [September 9, 2026, 6:20pm UTC](https://developer.sailpoint.com/discuss/t/web-services-connector-source-unable-to-display-entitlements/222068/3 "2026-09-09T18:20:04Z")
> [@abhijit\_shekki](#): > > - `OrgId` → `$.OrgId` > > - `RoleId` → `$.RoleId` In the response mapping, could you try : - `OrgId` → `OrgId` - `RoleId` → `RoleId` Without `$.` ---
**Author:** ![punna0001](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/punna0001/32/42011_2.png) [@punna0001](https://developer.sailpoint.com/discuss/u/punna0001)\ **Post date:** [September 10, 2026, 4:05am UTC](https://developer.sailpoint.com/discuss/t/web-services-connector-source-unable-to-display-entitlements/222068/4 "2026-09-10T04:05:34Z")
Hello Abhijit. @baoussounda’s suggestion looks correct. Since your Root Path is already `$.data`, try using `RoleId` and `OrgId` directly in the response mapping instead of `$.RoleId` and `$.OrgId`. ---
**Author:** ![abhijit\_shekki](https://avatars.discourse-cdn.com/v4/letter/a/edb3f5/32.png) [@abhijit\_shekki](https://developer.sailpoint.com/discuss/u/abhijit_shekki)\ **Post date:** [September 10, 2026, 5:44am UTC](https://developer.sailpoint.com/discuss/t/web-services-connector-source-unable-to-display-entitlements/222068/5 "2026-09-10T05:44:19Z")
Hi everyone - Thanks for your response. It looks like this may be a caching or UI refresh issue, as mentioned by Gopi S. @Gopi2000 – I validated the entitlements using the approach you suggested: **Role → Edit → Manage Access → Add Access** , and I can see the newly aggregated entitlements there. However, they are still not visible on the **Entitlements** page. Do you know how long it typically takes for the entitlements to appear on the Entitlements page? Is there any cache/index refresh that needs to be triggered, or should I just wait for the UI to synchronize? ---
**Author:** ![punna0001](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/punna0001/32/42011_2.png) [@punna0001](https://developer.sailpoint.com/discuss/u/punna0001)\ **Post date:** [September 10, 2026, 6:03am UTC](https://developer.sailpoint.com/discuss/t/web-services-connector-source-unable-to-display-entitlements/222068/6 "2026-09-10T06:03:27Z")
Hello Abhijit. Did you get a chance to try @baoussounda’s suggestion by changing the response mappings to relative paths and running the aggregation again? ---
**Author:** ![abhijit\_shekki](https://avatars.discourse-cdn.com/v4/letter/a/edb3f5/32.png) [@abhijit\_shekki](https://developer.sailpoint.com/discuss/u/abhijit_shekki)\ **Post date:** [September 10, 2026, 6:08am UTC](https://developer.sailpoint.com/discuss/t/web-services-connector-source-unable-to-display-entitlements/222068/7 "2026-09-10T06:08:56Z")
Hi Harish, Yes, I tried updating the response mapping as suggested, but the Entitlements page still shows a count of 0, even though the aggregation completes successfully. ---
**Author:** ![punna0001](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/punna0001/32/42011_2.png) [@punna0001](https://developer.sailpoint.com/discuss/u/punna0001)\ **Post date:** [September 10, 2026, 6:39am UTC](https://developer.sailpoint.com/discuss/t/web-services-connector-source-unable-to-display-entitlements/222068/8 "2026-09-10T06:39:31Z")
Since you can see the entitlements under Role \> Manage Access \> Add Access, it looks like the entitlement objects are being created successfully. As one more check, could you try the List Entitlements API filtered by your source ID? `filters=source.id eq "your-source-id"` If the API also returns those entitlements, I would not make any further changes to the schema or response mapping. Also, please clear any filters on Admin \> Access Model \> Entitlements and check again. If the API returns the entitlements but that page still shows 0, I would suggest raising a SailPoint Support case for the Entitlements page/display issue. ---
**Author:** ![baoussounda](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/baoussounda/32/13095_2.png) [@baoussounda](https://developer.sailpoint.com/discuss/u/baoussounda)\ **Post date:** [September 10, 2026, 6:53am UTC](https://developer.sailpoint.com/discuss/t/web-services-connector-source-unable-to-display-entitlements/222068/9 "2026-09-10T06:53:13Z")
Hi @abhijit_shekki , You can reset your source entitlements and try to aggregate again may be this will resolve the caching issue : If you have acces to ISC vscode plugin for example, right click on your source name then : ![image](https://global.discourse-cdn.com/sailpoint/original/3X/a/4/a420de7cd77a0236f5bf65ae8ac53ccdd337e906.png) Or you can use the API : [reset-source-entitlements-v-1 | SailPoint Developer Community](https://developer.sailpoint.com/docs/api/reset-source-entitlements-v-1/) ---
**Author:** ![Gopi2000](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/gopi2000/32/21706_2.png) [@Gopi2000](https://developer.sailpoint.com/discuss/u/Gopi2000)\ **Post date:** [September 10, 2026, 8:29am UTC](https://developer.sailpoint.com/discuss/t/web-services-connector-source-unable-to-display-entitlements/222068/10 "2026-09-10T08:29:46Z")
Hi @abhijit_shekki, In my case, it was fixed most likely after the next periodic refresh. Kindly run an aggregation today; the entitlements should be populated by now. If they are still not visible, I would recommend raising a support ticket, as it could be a backend caching issue. ---
**Author:** ![abhijit\_shekki](https://avatars.discourse-cdn.com/v4/letter/a/edb3f5/32.png) [@abhijit\_shekki](https://developer.sailpoint.com/discuss/u/abhijit_shekki)\ **Post date:** [September 10, 2026, 10:41am UTC](https://developer.sailpoint.com/discuss/t/web-services-connector-source-unable-to-display-entitlements/222068/11 "2026-09-10T10:41:10Z")
Thanks everyone. The **List Entitlements API** returns all the expected entitlements, so this appears to be a caching or UI refresh issue. I’ve opened a **SailPoint Support ticket** for further investigation.