Addition Attribute Aggregation from NERM User Connector

[deepakarora]

Hi,

NERM OOTB User connector doesn’t have the title attribute in the account schema. However, I can see the attribute from the API call and in the UI as well. I added the “title” attribute to the account schema, but it’s not getting aggregated. Is there any other way to pull the additional attribute, or is it not possible?

Thanks.

[vikaspawar0303 (vikas pawar)]

@deepakarora A few things to check:

1. Verify the API Response

   • Confirm that the title attribute is returned for the endpoint being used by the connector during account aggregation.
   • Sometimes the UI displays values from a different API call than the one used for aggregation.

2. Check Account Schema Mapping

   • After adding the attribute to the schema, ensure:
     • Attribute name exactly matches the API field name (case-sensitive).
     • Data type is correctly defined.
     • Attribute is marked as searchable/multi-valued if required.

3. Run a Full Aggregation

   • Perform a full account aggregation after updating the schema.
   • Incremental aggregations may not pick up newly added schema attributes.

4. Review Connector Configuration

   • Some SaaS connectors have a predefined attribute allowlist and only aggregate attributes explicitly supported by the connector.
   • Even if the API returns the attribute, the connector may ignore it unless SailPoint has exposed it in the connector’s aggregation logic.

5. Check Aggregated Account JSON

   • Use:
     • Search → Accounts → Select Account → View Account JSON
   • Verify whether the title attribute exists there. If not, the connector is not ingesting it during aggregation.

Alternative Approaches

If the OOTB connector does not support aggregating title, you can consider:

• Before Operation Rule / Web Services Connector

  • If flexibility is required, a Web Services connector can pull the additional attribute directly from the API.

• Identity Attribute Sync via Workflow/API

  • Create a workflow that calls the NERM API and updates a custom identity attribute with the title value.

• Connector Enhancement Request

  • If the API returns the attribute but the OOTB connector does not aggregate it, raise a SailPoint Support ticket. SailPoint can confirm whether title is a supported attribute for aggregation in the NERM connector and may provide an enhancement or workaround.

In my experience, when an attribute is visible in the API response and UI but does not appear in the aggregated account after a full aggregation, it is often due to a connector-side limitation rather than a schema configuration issue. I would recommend checking the account JSON first and then opening a SailPoint support case if the attribute is still missing.

[punna0001 (harish Punna)]

Hello Deepak. The NERM Users connector uses a predefined account schema that doesn’t support custom attributes. Adding title to the schema manually in ISC won’t help because the connector itself doesn’t read that field from the API response during aggregation, so it will always come back blank.

You are right that the NERM Users API does return title on the user object, and the UI shows it. The gap is purely connector-side.

If title is already available from an authoritative source (HR system, Workday, etc.), map the identity attribute from there instead. Otherwise, I would raise a SailPoint Support case requesting title be added to the connector’s predefined schema. The connector is still relatively new (released Dec 2025), so there’s room for schema expansion in upcoming updates.

[deepakarora]

Thanks, Harish. As of now, I will set up the ISC workflow to update the title for users.

[punna0001 (harish Punna)]

Sounds good, Deepak. Just a quick heads up before you build the workflow.

The workflow can call the NERM API and retrieve title, but it can’t populate title on the NERM Users account because that connector uses a fixed predefined schema.

Identity attributes also need to be derived through the identity profile mappings, so the value should be stored on another source account that ISC can aggregate and then mapped to the identity attribute from that source.

If you specifically need title to appear on the NERM Users account, SailPoint would need to add it to the connector’s predefined schema through a product enhancement or Support request.

[schattopadhy (SHANTANU CHATTOPADHYAY)]

@deepakarora

RM OOTB User connector doesn’t have the title attribute in the account schema. However, I can see the attribute from the API call and in the UI as well. I added the “title” attribute to the account schema, but it’s not getting aggregated. Is there any other way to pull the additional attribute, or is it not possi

@deepakarora yes you can pull those attributes but make sure those attributes are added in the person schema for nerm and in the isc connectivity setting add those additional schema attributes it should come to Sailpoint .We have added many attributes similar way

[deepakarora]

I believe you are talking at the profile level, and that we can do. But I am adding the NERM User connector.