Review crashes after a new custom field is added - WKB227310

SYMPTOMS

• Review crashes when manually integrating a peak 
• Processing Method Editor does not start ("Failed to start application")

ENVIRONMENT

• Empower 3 Feature Release 1
• Empower 3 Feature Release 4
• Empower 3.6.1

CAUSE

Customer created a custom field with the same name as one of the fields used in the formula. In this case, it was CConst1, which was defined as Peak Level custom field with a formula of CConst1 * 1. Removal of this custom field from the customer's project prevents the crash and allows successful operation. The behavior was reproduced by GSS in Empower 3 Feature Release 4 and Empower 3.6.1

This issue was entered as CRI-4346.

FIX or WORKAROUND

1. Delete custom fields meeting this criteria.
2. When creating new custom fields, do not name the custom field the same as any of the internal fields used in the formula.  

ADDITIONAL INFORMATION

Updated 13Aug2024: CRI-4346 was rejected in Feb 2022, because it is a user induced processing error by creating a custom field which had an identical name to a default field (CConst1) in Empower processing method. Conclusion, inform users to not name CF using a field name that is available for use in the list of custom fields.