MUX views: Error: API-1005 when filtering for secured fields in Staffing Allocations

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

Applying Field Level Security (FLS) to the Department OBS attribute (Resource object) in the Staffing module causes an API-1005 error when users attempt to filter or load shared views which has Department OBS saved.

Error toast Message "API-1005: Attribute(s) 'obs_department' specified in query parameters are not supported or secured."
This is followed a warning message "The selected views uses attributes that are unavailable" or "Conditions referring to deleted or deactivated attributes have been removed".
The issue specifically affects "Allocations by Investment" and "Allocations by Resource" views.

As a result the following Use Case is not met:

Project Managers shall see and book all Resources. (global Resource View and Resource Soft Book Right). Project Managers do not have Right for Staffing Module.
Resource Manager: Shall see only Resources of their OBS. Resource Managers have access to staffing Module

Issue:

Project Manager is also at the same time Resource Manager. With the before mentioned setup the specific Resource Manager can see all Bookings of all Resources and hence the utilization pattern of all Resources (as requirement of Workers Council - Resource Managers are not allowed globally to see the utilization pattern of ALL Resources).

Environment

Clarity 16.4.2

Resolution

Technical review of this usability issue confirms that the observed behavior is consistent with the current product design. When a secured attribute is included in a saved view and accessed by a user who lacks the necessary Field Level Security (FLS) "View" rights, the following occurs:

Filter Bypass: The specific filter is not applied for the unauthorized user.
System Validation: Clarity performs a permission check on all attributes within a view's filter and column set upon loading. If an attribute is secured and the user lacks rights, the system treats the attribute as "unavailable" or missing for that session.
Automated View Modification: To allow the page to load without unauthorized data, the Modern UX (MUX) strips the restricted attributes. This changes the saved view to an "unsaved" state.
Warning Notification: A toast message stating, "Conditions referring to deleted or deactivated attributes have been removed," is displayed. While this message also applies to deleted fields, it is the standard notification for FLS restrictions.

Reference: MUX Views : Conditions referring to deleted or deactivated attributes have been removed

This behavior is consistent across all object grids in the Modern UX, including Projects, Ideas, and Staffing.

Recommended Actions to prevent the warning message and ensure proper view loading for users without rights to the secured attribute, choose one of the following:

Create Personal Views: After the restricted attributes are stripped and the warning appears, the user should save the modified view as a new personal "Favorite" view. This new version will load without the restricted attributes or the warning message.
Adjust Security Permissions: If the user requires the ability to filter by this attribute, an administrator must grant them "View" rights in the Field Level Security settings for that specific attribute.

If a change in this product behavior is desired, please submit feedback via the Clarity ideation event to connect directly with the Product Management team.