Epic SER Account Creation Fails When Requesting Blueprint Entitlement - Item 45 (Referral Source Type)

Identity Security Cloud (ISC) ISC Discussion and Questions
, ,
1

Hello,

We are experiencing a provisioning failure when users request only a Blueprint entitlement for Epic SER account creation. The provisioning fails with the following error:

  • sailpoint.connector.ConnectorException: Operation failed: [Begin processing of database import, Entry Person: 828-IH_SAILPOINT, TEST, Data Source: Global, Import Specification: SER,1000, Log for record 1, Warning: ID translation failed; attempting to create a new record by setting related import items from mnemonic MPI metadata LSLC5E812,-1,351., Error: Item 45: Referral Source Type is a required item. Aborting record import., This record has not been imported., End of processing of database import; 1 records processed]
  1. Schema to Item Number Mapping:
  • Added: <entry key="referralSourceType" value="45" />
  1. Blueprint Configuration:

  • Every Blueprint contains a referralSourceType attribute (e.g., “Provider”, “Non Referral Source”)

  • Blueprints are aggregated as entitlements (Account Groups)

  1. Provisioning Policy Status: Blueprint attribute is currently in disabled state in the provisioning policy

  2. What Works

    When we follow a two-step process, provisioning succeeds:

    1. First Request: User requests referralSourceType attribute

      • Account is created successfully.

    2. Second Request: User requests Blueprint entitlement

      • Blueprint is assigned to the existing account successfully

    What Doesn’t Work

    When users request only the Blueprint entitlement (single request):

    • Account creation fails with “Item 45: Referral Source Type is a required item” error

    • The Blueprint contains the referralSourceType value, but it’s not being passed to Epic during account creation

      How should we configure the provisioning policy to allow users to request only a Blueprint and have the account created successfully with all required Epic fields (including Item 45 - Referral Source Type)?

Regards,
Manish

4

Hi Manish,

Have you tried passing “referralSourceType” as an attribute using CREATE provisioning policy?

5

Hi Satyadipan,

Thank you for your quick response. Yes, I have created transform. The FirstValid transform looks for the referralSourceType account attribute, and the fallback uses the static value “Provider”. In the provisioning policy, the transform type is set to identityAttribute, the attribute name is referralSourceType, and isRequired is set to true.

When I request access to the Blueprint entitlement only, it remains in a pending state.

Thank you,

Manish