Submitted by 334 on
Symptom
When adding a name with a name type where the code has mixed case characters, example STMail, the name for this respective type is used in the header name information instead of the existing preferred name.  All reports, exports and locations where default preferred name is used will display the incorrect name type.



Cause
This is by design. Not all customers wish the preferred name to be the name that displays, they set that up by using a code value character that is less than ‘a’, Capital Letters are less than ‘a’.


 
 
Resolution
Workaround:  The code of the Name Type needs to be lowercase characters. This tends to not place the new name type as the first name type in the Name display and prevents the header from using this name type when it should be using the Preferred name type that already exists. Due to the fact that you cannot change an existing code value, and you can’t delete a code if it has been used in the data, back-end updates would have to be done to remove the mixed case code and add a new code with lowercase characters and then updated with the new value on the same records in the database.

Status:  Please refer to KB article 4771-Scheduled fixes  to see if this is scheduled for a fix.
Article Type
Product Defect
Product Line
Millennium
Product Module/Feature
Biographical
Product Version
2016.1.3
2016.1.2
2016.1.1
2016.1
2015.2
2015.1.3
Ranking
No votes yet