Smokeball Developers,
Is there any plan to update the desktop app search functionality now that you have implemented pagination (as opposed to infinite scrolling)? Something about that update changed the search functionality such that it is unable to pick out a term from more than one field of data.
By way of example, please see the following four employment discrimination matters:
- Internal Reference: 1234; Client: Walmart; Type: Employment Compliance and Investigation; Description: Bob Smith
- Internal Reference: 5678; Client: Walmart; Type: Employment Compliance and Investigation; Description: Jane Doe
- Internal Reference: 9123; Client: Target; Type: Employment Compliance and Investigation; Description: Bob Smith
- Internal Reference: 4567; Client: Target; Type: Employment Compliance and Investigation; Description: Jane Doe
In these examples, if I type “Walmart Bob Smith” into the desktop app search feature, I get zero matters as a result. If instead, I type “Bob Smith” into the desktop app search feature, I get two results - both the Walmart case and the Target case. This might not seem like a problem, but when you have hundreds of “Bob Smith” cases instead of two, the search feature becomes no better than manually scrolling through the matters yourself. If type “Walmart” into the desktop app search feature, I get every Walmart matter which again renders the search feature unhelpful. The only way that you can reliably get the single matter for which you are interested is to memorize the internal reference code and search for that… which is not a feasible solution.
Before Smokeball implemented the pagination “update,” the search feature was able to look at more than one field of data at the same time. In other words, before the update, if I typed “Walmart Bob Smith” into the desktop app search feature, I got one result - the actual matter I was searching for.
Can you please address this problem that was introduced with the pagination update? Our firm has identified some workarounds (e.g., adding the clients name and description into the internal reference field”), but all of the workarounds are suboptimal.
Thanks!
Derek