Hello,
I noticed a bug when filtering by exact match. This specifically occurred when using setValueMap and I believe that is where the problem lies. Eventually we figured out a work around, but its rather awkward and I feel like this is still a bug that needs to be reported.
I've attached a test case, should be able to see any time you try exactly filtering to a name in the database.
Seen in Chrome.
SmartClient Version: 'SNAPSHOT_v12.1d_2019-10-02/LGPL Development Only'
I noticed a bug when filtering by exact match. This specifically occurred when using setValueMap and I believe that is where the problem lies. Eventually we figured out a work around, but its rather awkward and I feel like this is still a bug that needs to be reported.
I've attached a test case, should be able to see any time you try exactly filtering to a name in the database.
Seen in Chrome.
SmartClient Version: 'SNAPSHOT_v12.1d_2019-10-02/LGPL Development Only'
Comment