Error occurs when creating appointments from a request using improper username casing
If a transaction is created with a casing for the user's username that does not match the value used on the user record in the database, the following error will appear when creating appointments from the Request form for that transaction:
"Database Error
Error refreshing appointments:
Error in the PreferredName mapping
Some appointments could not be loaded. Please contact support."
Bug# 27423
0
votes
