SuccessFactors Single Account Aggregation issue

IdentityIQ (IIQ) IIQ Discussion and Questions
,
1

Which IIQ version are you inquiring about?

Version 8.1

Share all details related to your problem, including any error messages you may have received.

Hi,

I’m trying to run a rule for SuccessFactors Single Account aggregation. But I’m not able to build the resource object and getting an error stating “Exception running rule: The application script threw an exception: sailpoint.connector.ConnectorException: [ ConnectorException ]
[ Possible suggestions ] Ensure configuration parameters are correct with a valid format, Ensure active network connectivity between Source and Target system.
[ Error details ] sailpoint.connector.ObjectNotFoundException: No employee data found or the service account doesn’t have entitled permissions to perform complete operation. BSF info: Successfactors Single Account Aggregation at line: 0 column: columnNo”

I’ve checked the test connectivity and it is successful.

Kindly help me with this if anyone has built a rule for Success Factors Single account aggregation.

2

Hi @LalithyaReddy,

Just couple of questions -

  • Is full Account Aggregation working?
  • How is the Single Account Aggregation being triggered? Is it via Rule, if so is it working for other apps?
3

Hi James,

  • Yes, Full account aggregation is working fine.
  • Yes, For other applications the rule is working fine
4

Since the full aggregation is working, I am assuming that there are no permission related issues. Double check the whether the nativeIdentity is correct or not

5

can you tell me what patch version are u on ?

6

Hi @chaitanyav ,

We are in IIQ 8.1. There are no patches to it.

7

You can use the connectorDebug iiq console command to see whether you are able to get the resource object or not from target. Please refer the command in iiq console doc.

8

Hi @Vinod,

I was not getting resourceObject that was the issue as I mentioned previously.

Then I understood that I was not passing nativeIdentityObject correctly. Instead of passing PERSON_ID as nativeIdentityObject I was passing PERSONID_EXTERNAL.

So passing PERSON_ID as nativeIdentityObject solved the issue. Thanks everyone for your help. Appreciate it.

1 Like
9

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