Hi, Just to provide some background, I configured a source and successfully ran both Account Aggregation and Entitlement Aggregation. A large number of accounts were brought into the system, and there were no errors during the aggregation process.
However, when I attempted to add an entitlement to an Access Profile and clicked Save, I received the following error:
“Required field ‘ENTITLEMENT’ was missing or empty.”
After further investigation, I discovered that the entitlement attribute in the schema had been mapped as a String instead of a Group. We corrected the schema configuration and re-ran both the Account and Entitlement Aggregations, but the same error still occurs.
My question is: does the source need to be reset and re-aggregated so that the corrected schema is fully applied? Given that the source contains a large number of accounts and entitlements, what would be the recommended approach to reset the source? API , VSCODE etc ?
Additionally, if the source is reset, will that action have any impact on the target system, such as propagating changes or deleting accounts from the target?
Any guidance or recommendations would be greatly appreciated.
Yes, please reset the source. This will help to bring all entitlements in proper form in the catalogue. Once done let us know if it fixes the issue. First reset the Entitlements then the Accounts.
Thanks
Before going down the reset path, try running an unoptimized aggregation first. If you re-an aggregation through the UI after fixing the schema, that would have been an optimized run by default, which skips records ISC thinks it already knows about.
You can trigger an unoptimized account aggregation via the API: POST /v2026/sources/{sourceId}/load-accounts with disableOptimization set to true. Then run a standard entitlement aggregation after that.
If that doesn’t fix it, share the screenshots of your schema configuration so we can try to troubleshoot further.
Thanks @sangeetham_sowmya , schema already fixed with correct entitlement mapping,
looking at other forum answers, I though reset is a must , but happy to run unoptimized aggregation again via API followed with entitlement aggregation
Thanks @RAKRHEEM , just curious whether running unoptimized aggregation will fix the records without a source reset as per below answer by Sowmya
as a side note we got many accounts to load and takes many hours.
Hi @lalithajay ,
we can give it a try to see if it fixes.
This worked, after schema fix, firstly remove entitlements and then remove accounts
and then do standard account aggregation followed with entitlement aggregation
Didn’t try this option as additional overhead of providing a flatfile with accounts etc. to this API