Error 'One or more parameters are not API-enabled' received in Modern UX

book

Article ID: 210325

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

Receiving error 'One or more parameters are not API-enabled.  You may see unexpected results."

Steps to reproduce

In Classic View

  1. Create a new Subobject with Master Object as Idea
  2. Create new attribute Type - Lookup and Lookup - SCH_BROWSE_DEPT
  3. Enter API Attribute ID
  4. Map the attribute IDs to odf_entity_id
  5. Save

In New UX

  1. Go to Administration>>Blueprint
  2. Create new Idea blueprint
  3. Add the Subobject under the modules
  4. Save
  5. Go to Ideas
  6. Create new Idea
  7. Add Blueprint attribute to the column from the flyout
  8. Associate the new Idea with the newly create Idea blueprint
  9. Open the Idea
  10. Go to the Subobject created
  11. On the flyout, check the Lookup attribute created to show in the columns
  12. Select the drop down on the attribute

Expected Result - All departments will be available
Actual Result - Receive error 'One or more parameters 'param_entity_id_constrain, param_entity_id' are not API-enabled.  You may see unexpected results."

Cause

Working as designed

SCH_BROWSE_DEPT is used for Chargeback Debit Rules.  It is not recommended to use in the Modern UX.

Environment

Release : All supported releases

Component : CA PPM SAAS STUDIO

Resolution

If the Project Department ID fieldis needed, then use the lookup ID = LOOKUP_PARAM_DEPT_CODE with the constraint of [--Object ID--]. 

Or use SCH_BROWSE_DEPT_CODE which does not use the parameter. 

If the attribute cannot be changed, below is a workaround.

WORKAROUND

Create another lookup attribute using SCH_BROWSE_DEPT_CODE and associate this Attribute ID with the original lookup attribute

Steps for Workaround

  1. Create a new attribute on the SubObject
  2. Make note of the Attribute ID you enter
  3. Data Type - LookupString
  4. Lookup - SCH_BROWSE_DEPT_CODE
  5. Enter the API Attribute ID
  6. Save
  7. Go to the Impacted Department
  8. Under Object Attribute ID select Attribute ID of the lookup attribute you just created for both entity_id and  entity_id_constrain
  9. Save