Known issues in v3.1.0
There are several issues reported so far since the 3.1 release, we will post the update with all fixes in February. Meanwhile, here is the detailed list and workarounds.
- Client dialogs to setup criteria filters have a problem with exceptionally long strings used in value combo. This is because the default combo's in SWT don't have horizontal scroll bar. We fixed this - just take an update from client Help menu.
- Mongo indexes. Here we did something not very clever by trying to manage the indexes automatically. Some users would prefer to do this manually by tuning up composite indexes, this is particularly relevant for very large databases. Also, we are using the non-composite indexes and this clashes with composite indexes which you might already have. So, the workaround for now would be to drop the indexes you have and let logFaces create them for you. In the next update there will be an option to disable the logFaces fiddling with your indexes.
- We are now managing mongodb.properties file automatically, there is no need to edit it. But conversion from previous version got some issue with boolean properties. If your server doesn't get connected to MongoDB, check the mongodb.properties and make sure that there are no blank values and no duplicates.








