Android Capture app offline (local) analytics - Filters not working?

We have configured several Line Listings in the offline (local) analytics in Capture app. For all of them a three-dot menu appears in the upper right corner indicating all header names. But it seems that none of them actually have any effect.
Is this a known but and is there a JIRA ticket already?

Hi @George_McGuire!

We were trying to replicate the issue but we were able to filter by items on the line listing. Could you give us more details? Is it happening in a particular value type (dates, for example)?

Thank you!!

Hi Nancy, thanks a lot for the quick follow-up. I had encountered the problem during the on-site support in a health centre but was able to replicate the issue only partially on my own tablet.
The filters in the offline analytics are all working except for date fields, but I may not understand how the filters are supposed to work. I can enter a text string (as there is no calendar for selecting dates) and enter, for example 2025-05-18 to filter for Line Listing events on this day. But it seems that this filter has no effect.
Another usability issue (not a bug): the filter for numeric values works perfectly (filtering for “1” returns all numeric values with 1 such 1, 10, 111, 1001 etc. which is not useful for our use case). In our use cases we would like to filter for non-blank fields (most important, that filter is set on the web but seems not affecting offline analytics) or for value ranges such as >0 or <100.

Hi George,

I have checked that filtering by dates is not working, we will take a look at that.

Regarding the filtering of numeric values, there is a bug indeed: the operators “is empty / null” and “is not empty / null” are not implemented and they should be. I will create a ticket for that. The range filter should work though. I have created a LineList with a range a filter and the android app only displays the values in the range. This range must be defined in the LineList object (web LineList), it cannot be specified by the user in the Android app. That would be a nice feature request, feel free to open a ticket for that.

Hi Victor

Thanks for the quick feedback! Glad to hear the range filter works, so I guess >=0 will work just as well as the non-blank filter which is really helpful.