Impact:
all users
Analysis
I have done nearly some 50 combination testing to find the root
cause and have replicated the same issue today in the QA environment and found
the root cause is custom field attribute which is “included in database table “mspfield” and not there as per guideline CA and
may be some update happen unknowingly.
Root cause
There is a table called “mspfield” in database and
found many custom fields are stored.
Work Around
Deleted all the custom fields in MSPField
table, the attribute which is not available in “cmn_attributes” table.
Permanent solution
I am in the process of finding system or
someone. who was added the custom fields in “mspfield” field.
