Please share any images or screenshots, if relevant.
[Please insert images here, otherwise delete this section]
Please share any other relevant files that may be required (for example, logs).
[Please insert files here, otherwise delete this section]
Share all details about your problem, including any error messages you may have received.
[Does anyone know how to setup a custom schema attribute for EPIC. We want to set up manager attribute and also push it in the target when applicable. Has anyone ever done it ? Any insights would help]
Hello Swati. Neel’s link covers the read/aggregation side. Treat this as two parts, since adding the attribute to the IIQ schema does not by itself mean the connector can write it.
SailPoint’s ISC Epic connector release notes list PrimaryManager as an account attribute. On 8.3p2 I would first confirm your connector build supports it, then check the Epic application’s account schema (Configuration > Schema tab). If it is supported but not listed, add it there with Add New Schema Attribute using the supported name and type, then aggregate a test account and confirm the value lands on the Link, with connector debug logging on if it does not.
To push it, the connector has to support a Modify on that field. If it does, Attribute Synchronization is the clean path: under gear > Global Settings > Identity Mappings, add a Target Mapping from the identity attribute to the Epic attribute, with a transformation rule if Epic expects an ID rather than a name. For manager changes that come in through aggregation, run Identity Refresh with Synchronize Attributes enabled (IIQ 8.3 docs). Test one account and confirm IIQ generates the Modify and Epic accepts it, since a target-side rejection can look like a mapping gap.
Are you working with Epic EMP or SER, and does PrimaryManager already show in your account schema?