API-1005 : Attribute(s) 'attributeID' specified in query parameters are not supported or secured.

Products

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

Issue/Introduction

The user encounters the error “API-1005: Attribute(s) 'attributeID' specified in query parameters are not supported or secured” when attempting to access a task module under project workspace. This occurs when an attribute under task object is protected under Field Level security restrictions, and the user is not a member of the group that has the required view or edit permissions for that attribute.

1. Create a new user
2. Grant below rights to the newly created user for a project
   • Global Rights
     • Project Management - Navigate
     • Tasks - Navigate    
   • Instance Rights
     • Project - View
     • Project - View Tasks
     • Project - Edit Assigned Tasks
3. Navigate to MUX --> Administration, search for task object and secure couple of attributes
4. The newly created user is not part of Admin --All Rights groups
5. Now login with the newly created user and navigate to MUX --> Project Workspace
6. Click on the Project Instance and navigate to Task module 

Expected Results: The user should be able to view the tasks without any error 

Actual Results: The user is unable to view the task's and gets a toast message of the error and app ca log also has relevant errors logged

ERROR 2025-11-04 01:50:51,794 [http-nio-8080-exec-944] ppm.rest (clarity:[email protected] user:XXXX-XXXX-XXXX-XXXX-XXXX\:PPM_REST_API) (XXX-XXX-XXX-XXX-XXX) 
com.ca.ppm.rest.exception.BadRequestException: API-1005 : Attribute(s) 'hasAssignments' specified in query parameters are not supported or secured.
 at com.ca.platform.osf.object.rest.adapter.ODataODFObjectAdapter.populateSelect(ODataODFObjectAdapter.java:1059)
 at com.ca.platform.osf.object.rest.adapter.ODataODFObjectAdapter.populateQueryInfo(ODataODFObjectAdapter.java:782)
 at com.ca.platform.osf.object.rest.adapter.ODataODFObjectAdapter.getObjectInstances(ODataODFObjectAdapter.java:297)
 at com.ca.platform.osf.object.rest.adapter.ODataODFObjectAdapter.getObjectInstances(ODataODFObjectAdapter.java:269)
 at com.ca.platform.osf.object.rest.provider.ODFResourceProvider.getResources(ODFResourceProvider.java:2116)
 at com.ca.platform.osf.object.rest.provider.ODFResourceProvider.getEntities(ODFResourceProvider.java:272)
 at com.ca.ppm.rest.resource.BaseResourceHandler.retrieveResources(BaseResourceHandler.java:278)
 at com.ca.ppm.rest.resource.BaseResourceHandler.retrieveResources(BaseResourceHandler.java:238)
 at com.ca.ppm.rest.resource.ResourceHandler.getSubResources(ResourceHandler.java:192)
 at jdk.internal.reflect.GeneratedMethodAccessor364.invoke(Unknown Source)
 at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

Environment

Clarity 16.3.3, 16.3.3.1 

Cause

DE178253

Resolution

Fixed in

• Clarity 16.4.1 
• Clarity 16.4.0 Patch 1 (16.4.0.1)
• Clarity 16.3.3 Patch 3 (16.3.3.3)

Workaround: 

• User can navigate to Task Workspace and will be able to see the tasks without errors 
• Mark the field's View Access = All Users.  This will allow the field to be secured for Edit Access.