We are going to implement emergency project data entry and analysis through the Android Capture App. To do so we have built Dashboard/visualization and testing on the handheld devices i.e. Tablet/Phone. We have included few Program Indicators in our visualization and configured through the Android Setting Web App. Unfortunately, some of the PI having filter in the expression are not calculating/showing data correctly on the visualizations in the Android App. However ,the same indicators/visualizations are showing correct data on the Web App.
Could you guide what is issue or limitations of the android app while including Program Indicators in the Visualizations.
Thanks for your response. We are facing issue for multiple PI having filter. Here, I am sharing formula of the filter expression-
#{NB4QDIPsQhB.f4vR5NBU5jy} == ‘1’ || #{NB4QDIPsQhB.HtDAOexsHPt} == ‘1’
Hi! again,
I am putting some additional info for your better understanding.
Actually, we entered/registered 1 event on 2024-08-01. So, the indicators in row no. 2 and 3 in both the visualizations should only show value as 1 on date 2024-08-01 (see second screenshot of web app table). But in the first screenshot of Android App the same data is showing for entire dates selected in the period. That’s the data discrepancies between Android App Vis. and Web App Vis.
The visualization is configured using daily periods, isn’t it? Could you share the analytics type and period boundaries of the Program Indicator? I mean these properties:
I have been able to reproduce the issue with the information provided, thank you for the detailed report. Definitely, there is something that is not working properly with that kind of indicator.
I have created a JIRA ticket to look further into it [ANDROSDK-1907] - Jira. You can follow up the progress there.
We’ve found the issue that is causing the discrepancy and will be patched for the next release in October.
In the meantime, we’ve also found a workaround that you may use to fix it: Please wrap the Program Indicator filter with parenthesis to prevent the issue from happening. Using your filter example, just add parenthesis like such:
