Unable to create new financial plan in New UX - API-1006 error

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

I can't create a new Cost Plan in the Financial Plan tab of the New / Modern User Experience (UX), I instead 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"}

Environment

Release : 15.8.1, 15.9, 15.9.1

Component : CA PPM SAAS FINANCIAL MANAGEMENT

Cause

This issue is caused by DE59678. The defect was reproduced with around 500 attributes created that stood before Start Date field alphabetically. The issue could appear if the Start Date field is placed around the 500th place.

Resolution

Fixed in 15.9.2 and 15.8.1 patch 5.

Workarounds:

• Option 1: Create the cost plan in Classic Clarity

• Option 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

• Option 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 this workaround:

1. 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