Aeon Client throws error loading appointments if the casing for a username is inconsistent between the User record and Appointment record
If a username uses different casings in the database between the User record and an Appointment record for that user, this will cause an error when loading the appointment calendar in the Aeon Client that states: "Error in the PreferredName mapping."
This mismatch can happen if:
1. A request is cloned to a user via the Clone Request to Another User option in the Aeon Client and a different casing for their username is typed into the Username field on the closing interface.
2. An appointment is then created for that user from the cloned request using the different username casing.
Bug# 25322
0
votes
released
·
AdminBrittany de Gail
(Technical Writer/Content Developer, Atlas Systems, Inc.)
responded
AdminBrittany de Gail
(Technical Writer/Content Developer, Atlas Systems, Inc.)
responded
Released in Aeon Server v5.2.6/Aeon Client v5.2.4.