ApplicationException from MasterPersistence.getLookUpEntity isn't displayed on the UI nor logs.
Steps to reproduce:
1. Rename 'CitizenShip' to 'CitizensShip' in the lookup_entity table
2. Try to enter 'Define Lookup Options' page
AFAIK this is related to mysql collation, when the default collation is set to utf8_bin this error is encountered in Mifos.
Default collation utf_general_ci should be used to avoid this error.
utf8_bin is case sensitive and utf_general_ci is case insensitive.
Another collation is utf8_unicode_ci.
Need to investigate what happens with different utf8 collation.
I just want to stress the fact, that this might be a more general issue. Probably ApplicationExceptions thrown from Mifos internals (like the one from getLookUpEntity) are caught and there is an error message displayed on the UI (nothing is logged). The problem is that these exceptions from Mifos internals do not contain valid message keys, so in the UI there is only a red dot(and nothing is logged).
reducing priority on it for now.
In Release 2.2, page with stack trace is displayed when trying to open 'Define Lookup Options' page.