Could not read: null for class Artifact for class Artifact

book

Article ID: 74827

calendar_today

Updated On:

Products

CA OPS/MVS Event Management & Automation CA Agile Central On Premise (Rally) CA Agile Central SaaS (Rally)

Issue/Introduction



What could be causing the error; "Could not read: null for class Artifact for class Artifact" on the Iteration Status page after the Workspace Admin added several Custom Fields?

Environment

Release:
Component: ACPREM

Resolution

This was caused by a name conflict of Custom field being named 'Requirement' which is already in use in the application.  Note that this was reported in an older version of Agile Central On-Premise which allowed creation of the field with a conflicting name.  Renaming the custom field eliminated the error.