Unable to Remove Deactivated/Inactive Resource from Multivalued Lookup Field in New UX (MUX)

Products

• Clarity PPM On Premise
• Clarity FedRAMP
• Clarity PPM SaaS

Issue/Introduction

In Clarity PPM New UX (MUX), a deactivated resource cannot be removed from a multivalued lookup (MVL) field that is configured with a dynamic/browse lookup type (e.g. SCH_BROWSE_RESOURCE). The deactivated resource's name continues to display in the field after the resource is deactivated, but attempting to remove it from the field has no effect.

Preconditions

• A multivalued lookup field exists on an object (e.g. Project) with lookup type set to a dynamic/browse resource lookup (e.g. SCH_BROWSE_RESOURCE).
• The field is added to a blueprint/layout and is populated with two or more resource values.
• One of the selected resources is subsequently deactivated in the system.

Steps to Reproduce

1. Create a new multivalued lookup field on the Project object with lookup type SCH_BROWSE_RESOURCE.
2. Add the new field to a blueprint.
3. Populate the field with two active users. Both values save successfully.
4. Deactivate one of the two users.
5. Refresh the page.
6. Attempt to remove the deactivated user from the field.

Expected Results:The deactivated resource can be removed/deselected from the multivalued lookup field.

Actual Results: Both resource names still display in the field after the refresh, and the deactivated resource cannot be removed from the field.

Environment

Clarity 16.2.x, 16.3.x,16.4.x

Applies to any object attribute using a dynamic/browse lookup type where the Studio-configured Lookup Filter restricts results to active resources only.

Cause

Dynamic/browse lookups (such as SCH_BROWSE_RESOURCE) do not support an "include inactive" override, unlike static lookups. The lookup's Studio-configured filter (e.g. on user_status_id) restricts the browse query to active resources only, by design. Because the deactivated resource is excluded from the lookup's fetched result set, the New UX multivalued lookup control has no matching option to bind its remove/deselect action to, so the stale value remains displayed and cannot be removed from that screen.

Resolution

This is expected/by-design behavior for dynamic/browse-type lookups, which do not support surfacing inactive values for removal in New UX. Customers requiring native removal support in New UX should log a new enhancement with product management team.

Workaround: Remove the deactivated resource from the multivalued lookup field using Classic PPM UX, which does not gate the removal action on the resource's presence in the active-only browse result set:

1. Navigate to the object instance (e.g. the project) in Classic PPM.
2. Open the page/layout containing the multivalued lookup field.
3. Remove the deactivated resource from the field and save.

Once removed via Classic UX, the field will correctly reflect only the active resource(s) in both Classic and New UX.