Hello everyone,
I’m looking for some guidance regarding a Siebel integration using the SailPoint IdentityIQ OOTB Siebel connector.
Environment:
-
SailPoint IdentityIQ: 8.4p2
-
Siebel CRM: 23.1
When using the default Employee Business Object (BO) and Employee Business Component (BC) without any filters, all provisioning operations and business requirements work correctly, including:
-
Account creation
-
Account updates
-
Assign/Remove Position
-
Assign/Remove Responsibility
-
Disable account
However, because the default Employee BC contains a very large number of accounts, the Siebel team created a custom Business Object and Business Component with a filter to return only the required accounts:
-
Business Object: SailPoint Employee BO
-
Business Component: SailPoint Employee BC
After switching the connector to use these custom BO/BC objects, all operations continue to work as expected except Assign Responsibility, which fails with the following error:
SBL-DAT-00523: The selected record has been modified by another user since it was retrieved.
Interestingly, this is the same error we encountered previously, but it only occurs when using the replicated BO/BC with the filter. If we switch back to the default Employee BO/BC, the Assign Responsibility operation completes successfully.
Has anyone experienced a similar issue with a customer when using custom Business Objects/Business Components with the SailPoint OOTB Siebel connector?
I’m trying to understand:
-
Why would this behavior occur only with the custom BO/BC?
-
Is there any additional configuration required in either Siebel or the SailPoint connector when using custom Business Objects and Business Components?
-
Are there any best practices or known limitations for using filtered/custom BOs and BCs with the OOTB Siebel connector?
I would really appreciate any insights or recommendations from anyone who has faced a similar scenario.
Thank you!