We’re working on improving the Event Reports app and would love to hear from you! If you’ve used the app and have thoughts on what works well, what could be better, or what you’d like to see in future versions, this is the moment to share.
Please take 5–10 minutes to fill out this short feedback form:
Your input will help guide the next steps in development from v43 and ensure the app better meets your needs.
PS: If you don’t use Event Reports App and want to propose other analytics apps for next phases of improvement, please respond to this message and let us know!
As a way of respect for your work I tried to fill in the form.
Unfortunately I need lots of improvement to comment on this.
Thank you for the opportunity.
Amalia
Thank you for this opportunity to provide feedback. I’ve filled in the form for Event Reports, but below I’ve also included feedback on the Line Listing App, as I know that is replacing the Event Reports Line Listing functionality.
Inability to filter by N/A for some data types For data elements with option sets, you cannot filter by N/A or No value. You can for numeric, dates, boolean, but not values with option sets.
createdAt filter Would be great to be able to use createdAt field for filtering. Sometimes people are entering data with a big delay, so filtering by event date does not give you the same thing as filtering by createdAt.
createdBy filter The addition of the createdBy field is great! But filtering should be supported.
Downloading metdata I’ve submitted this as a ticket and I think it was marked as something that wouldn’t be pursued, but the ability to download data with metadata is important. Currently in the line listing app you need to get the actual API call and remove the headers to get things like Stored by, Created By, and the event uid to come through. It used to automatically download with event uid and some additional metadata, but now you need to know how to manipulate an API call to get this information in Excel.
OR logic in filters instead of just AND would be very useful. Often we use line listing to try to understand expected values for Program Indicators, but its hard to get the correct list of events when filtering is so limited.
Are Enrollment type PIs valid for use in Line Lists? I don’t understand why they wouldn’t be able to be evaluated for Enrollment type line lists, but when I add them I always get “Something went wrong”. If Enrollment type PIs are not valid, remove them from the list of available data items. It confuses users to have data presented to them that are not valid.
In Event line lists, it would be great to have the same Repeated Events functionality as the Enrollment line lists. I realize this can be accomplished with Enrollment line lists, but you can’t filter by event date on enrollment line lists.
In Enrollment line lists, it would be really helpful to be able to add and filer by event date.
In Enrollment line lists, when using Repeated Events or data from multiple program stages, adding a column for the event date would be really useful. For example, I want to see how many people who tested positive in the HIV Testing program stage have the ART (treatment) program stage completed. And I want to know the date of both the test and the treatment.
When an Event Type PI is added to an Enrollment linelist, how is it determining the analytic period boundaries for the evaluation? Since the analytic period boundaries are defined based on the event date, and the event date is not being displayed or applied as a filter, how do we know this? For example:
Here I have two PIs, HTS_TST, which takes data from one program stage, and TX_CURR_VERIFY, which takes data from a different one. HTS_TST is returning 1 for each row, but TX_CURR_VERIFY is returning 0 (when in fact, some enrollments should be 1 for TX_CURR_VERIFY). It is challenging to troubleshoot this without knowing what analytic period boundaries are being used.
Link to client dashboard We often use line lists for data cleaning. It would be AMAZING if there was a way to add a link to the individual’s dashboard in tracker capture. We actually don’t use line lists for data cleaning for this reason. We create external dashboards.
Nice to have:
Org Units It would be nice to be able to get the org unit level that you select, as well as the org unit the data were entered at (or the entire OU path). For example, if I select level 2, but data are entered at level 4, it only returns the level the data were entered at.
