ERROR: No match found for enum value
Information in this Brief applies to:
The following error is encountered when changing a field that has a dynamic default set:
This error occurs when the value assigned by the dynamic default is a custom field that has only white space for its value. The current workaround for this issue is to assign a real value to the custom field beyond just white space for the value. Borland is looking into alternate methods of attempting to handle "blank" values for future releases, but currently, it is not supported by StarTeam Extensions.