SQLLoader Full Aggregation Issue: Why Only One Entitlement Appears

Hi there — I’m facing an issue with the SQLLoader connector where I’m unable to aggregate all entitlements during a full aggregation.

Current behavior:

  • Let’s say a user has two entitlements: ent1 and ent2.

  • During the first full aggregation, the system aggregates ent1.

  • During the second aggregation, it overwrites ent1 and only displays ent2.

  • I need both entitlements to appear together after aggregation.

Notes:

  • I have marked the entitlement attribute as entitlement and multi-valued.

  • When I run a single account aggregation, both entitlements get aggregated correctly.

  • The issue occurs only after triggering a full aggregation following a single account aggregation — only one entitlement is displayed.

Any suggestions or solutions for this SQLLoader connector issue would be appreciated.


Example CSV format (same accountId, multiple entitlements)

userId,firstName,lastName,accountId,entitlement
u001,John,Doe,acc01,ent1
u001,John,Doe,acc01,ent2

This format represents the scenario where the same user and same accountId have multiple entitlements, and both should be aggregated as multi-valued entitlements.

@Gopi2000 -

If the data for a single account spans multiple rows of a database table, you need to merge the data for a successful aggregation based on key field.

Have you implemented the data merging logic? If not, refer the below doc for reference -

2 Likes

Hi @amit_1140

I’ve enabled data merging for the entitlement attribute and set mergeRows to true. During single account aggregation everything works perfectly, but the issue occurs during full source aggregation where I’m unable to fetch both entitlements.

can you try order by clause in you aggregation query. have the result order by either userID or accountID.

2 Likes

@lampard08 for one my of connector it works fine without order by clause in query is there any work around when I need to use order by caluse, for the above issue which i’ve faced it works fine with your suggestion. thanks!

The reason it would be working is maybe the query is already returning the data with all account together. try to test for the one already working if the data resultset in not in order already.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.