Unable to create New Financial Plan in New UX - API-1006 Error

book

Article ID: 206677

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

Whenever I try to create a New Cost Plan in the Financial Plan tab of the New / Modern User Experience (UX), I get the following error message:

"API-1006 : The value ''undefined'' for Attribute 'startDate' is not in expected format or is invalid."

In the Financials module, the window on the right hand side is blank with no option to attempt to create a new plan.

Steps to Reproduce (Using financial Plan module):

  1. In Classic Clarity, go to Administration->Studio->Objects-Project->Attributes
  2. Add additional attributes to the project object so that there are at least 500 attributes ahead of the Start field alphabetically
    • Important: Ensure the attributes all have an API Attribute ID
  3. Create a new project in the Modern UX
  4. Populate the Department to financially enable the project
  5. Click on the Financial Plans tab
  6. Click the New Plan button

Expected Results: Popup window is generated to enter cost plan details

Actual Results: The following error is generated and the cost plan cannot be created: "API-1006 : The value ''undefined'' for Attribute 'startDate' is not in expected format or is invalid."

(In the Financials module, the window on the right hand side is blank with no option to attempt to create a new plan.)

In a developer tools trace, the following error is shown: {"resourceId":null,"httpStatus":"400","errorMessage":"API-1006 : The value ''undefined'' for Attribute 'startDate' is not in expected format or is invalid.","errorCode":"api.invalidAttrValue"}

Cause

This issue is caused by DE59678 and happens if there are more than 500 attributes (with API Attribute IDs) ahead of the Start field alphabetically on the Project object.

Environment

Release : 15.8.1, 15.9

Component : CA PPM SAAS FINANCIAL MANAGEMENT

Resolution

This issue is under review as DE59678.

Workarounds:

  1. Create the cost plan in Classic Clarity

OR

     2.  Deactivate unused attributes alphabetically ahead of the Start attribute on the Project object (the amount required depends on how many active attributes with a API Attribute ID are above the Start field alphabetically)

OR     

    3. Make attributes not used yet in the New UX secure in the New UX Attributes section (the amount required depends on how many active attributes with a API Attribute ID are above the Start Date field alphabetically)

  • Steps for workaround 3:
    1.  As an Administrator, log in to the New UX
    2. Click on the Administration menu icon
    3. Click on Attributes
    4. Check the check box under the Secure column for attributes that are currently not needed in the New UX and alphabetically are before the Start Date field
Powered by Wolken Software