# NERM – Error while updating Person Profile (Assignments already linked to another profile)

**URL:** <https://developer.sailpoint.com/discuss/t/nerm-error-while-updating-person-profile-assignments-already-linked-to-another-profile/210800>\
**Category:** SHF Discussion and Questions\
**Tags:** nerm, non-employees, sailpoint-identity-security\
**Created:** [May 29, 2026, 4:05am UTC](https://developer.sailpoint.com/discuss/t/nerm-error-while-updating-person-profile-assignments-already-linked-to-another-profile/210800 "2026-05-29T04:05:51Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![sunildhawaleT](https://avatars.discourse-cdn.com/v4/letter/s/bb73d2/32.png) [@sunildhawaleT](https://developer.sailpoint.com/discuss/u/sunildhawaleT)\
**Post date:** [May 29, 2026, 4:05am UTC](https://developer.sailpoint.com/discuss/t/nerm-error-while-updating-person-profile-assignments-already-linked-to-another-profile/210800/1 "2026-05-29T04:05:51Z")

</div>

While modifying the contact assignment(Update Workflow for Person Profile) for a user associated with multiple other type of profiles, the system throws an error and does not allow saving the profile.

The issue appears to be related to assignment linkage validation, where the system detects that certain assignment IDs are already associated with other non-employee (Person) profiles.

This behavior is blocking updates to supplier user contact assignments and may indicate a data integrity or uniqueness validation issue in NERM assignment handling.

 ![image](https://global.discourse-cdn.com/sailpoint/original/3X/e/c/ec6a2ae28eac2d1a07369003e3e6376558982429.png)

---

<div class="post-metadata">

**Author:** ![BBR1](https://avatars.discourse-cdn.com/v4/letter/b/c57346/32.png) [@BBR1](https://developer.sailpoint.com/discuss/u/BBR1)\
**Post date:** [May 29, 2026, 6:43am UTC](https://developer.sailpoint.com/discuss/t/nerm-error-while-updating-person-profile-assignments-already-linked-to-another-profile/210800/2 "2026-05-29T06:43:37Z")

</div>

This happens when the same assignment/account relationship is mapped to another Identity profile. Hence, during update the Identity correlation detects duplicate linkage.

Check:

- Duplicate Asignmnets
- Identity Profile Correlation
- Account Linkage

---

<div class="post-metadata">

**Author:** ![sunildhawaleT](https://avatars.discourse-cdn.com/v4/letter/s/bb73d2/32.png) [@sunildhawaleT](https://developer.sailpoint.com/discuss/u/sunildhawaleT)\
**Post date:** [May 29, 2026, 7:17am UTC](https://developer.sailpoint.com/discuss/t/nerm-error-while-updating-person-profile-assignments-already-linked-to-another-profile/210800/3 "2026-05-29T07:17:20Z")

</div>

Hi Bharani Reddy, Thanks for quick response. We have a custom **Update Workflow on Person Profile** is implemented to store plant-related information.

1. A **Profile Select Attribute (Plant Profile Type)** is added on the form:
  - Allows selection of one or more Plant profiles.

  - Stores plant references at the Person level.

  - This attribute has reverse relationship with Person Profile Type attribute which is also can store multiple person profile on plant profiles. This is working for we users and getting error few user.

---

<div class="post-metadata">

**Author:** ![kannan\_sb85](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/kannan_sb85/32/35971_2.png) [@kannan\_sb85](https://developer.sailpoint.com/discuss/u/kannan_sb85)\
**Post date:** [May 29, 2026, 7:37am UTC](https://developer.sailpoint.com/discuss/t/nerm-error-while-updating-person-profile-assignments-already-linked-to-another-profile/210800/4 "2026-05-29T07:37:07Z")

</div>

@sunildhawaleT Hi Sunil - I think the error occurs when modifying contact assignments via an **Update Workflow for a Person Profile** for a user associated with multiple other profile types. NERM’s assignment linkage validation detects that certain assignment IDs are already associated with other non-employee (Person) profiles and that blocks the save. you need to check the one by one.

1. Identify conflicting assignment records via API

Query NERM REST endpoint: `GET /non-employee-records?filters=accountName eq "<user>"`. Find assignment IDs appearing on more than one Person Profile are the conflicting records.

1. Break duplicate linkage on affected Plant Profiles

Open each conflicting Plant Profile → clear the Person Profile Type reverse-relationship attribute → save. This unblocks the Person Profile workflow from re-saving cleanly.

1. Add a pre-condition check to the Update Workflow

Before each link action, check: _“Does this assignment ID already exist on another Person Profile?”_ If YES → skip (link already valid). If NO → proceed to create. This prevents re-collision on future executions.

1. Switch from “Add” to “Update/Upsert” in workflow steps

In NERM workflow designer, change the reverse-relationship write operation from `Add` to `Update` so it overwrites rather than duplicates the assignment link reference.

1. Verify profile attribute relationship type.

Regards,

Kannan

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\
**Post date:** [July 28, 2026, 7:37am UTC](https://developer.sailpoint.com/discuss/t/nerm-error-while-updating-person-profile-assignments-already-linked-to-another-profile/210800/5 "2026-07-28T07:37:20Z")

</div>

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