Why is Incident Date shown in Period dimension if it’s not used for filtering in Line Listing App?

Hello DHIS2 community,

We are trying to understand the behavior of the Period dimension in the Line Listing App.
When we build a line list that pulls data across program stages, the app only allows filtering based on the Enrollment Date as the input time dimension.

However, in the Period selector, we see both Enrollment Date and Incident Date listed.
Our question is:

  • Why is the Incident Date included in the Period dimension if the Line Listing App does not use it for filtering?
  • Is this a known limitation, an expected design choice, or is something misconfigured in our setup?

We would appreciate any clarification from the community or DHIS2 team.

Thank you

1 Like

Hi @dmbantu

Thank you for your question!

I think you can filter incident dates. If you double click the dimension, you will see a dialog with all the filtering options as you can see in the screenshot below:

Did I understand your question or were you referring to something else? If so, a screenshot would be quite helpful, thanks!

Hi @Gassim,

Thank you for your reply!

I think I may not have explained the situation clearly. Yes—when you open the Incident Date dimension directly, you can configure filters.

But what I was referring to is this specific behavior:

  • When the line list pulls data across multiple program stages, the Line Listing App seems to use only the Enrollment Date as the actual time boundary for retrieving records.
  • Even though Incident Date appears in the Period selector, changing it does not affect the returned data when multiple stages are involved. Only Enrollment Date does.

Hi @dmbantu,

  1. Yes, this is intentional, because many programs do not use incident dates, but all have enrollment dates, so it makes sense to use that as the standard filtering.
  2. Can you give steps to reproduce this? Incident date appears in the Period selector as a selection yes, but it should also be filtering returned data if you have applied a filter. If you just add it as a column, it will not change the returned data.

Best,
Karoline

1 Like

Hi @dmbantu

Think of the report as a table where each row is an enrollment before the system adds any stage data, it first decides which enrollments to include and that decision is made using Enrollment Date only

Incident Date belongs to the enrollment, but it cannot be used to limit which enrollments are fetched when multiple stages are involved

I’m sure you can do it :clap:

1 Like

You CAN use Incident date to limit which enrollments are fetched with multiple stages.

See this video where I am filtering on enrollment date, as well as incident date to further narrow down the list of enrollment, and I have data elements from two different stages in my line list too.

Let me know if you need any further info or if there is a different requirement that is not being met :blush:

2 Likes

Hi @dmbantu

I’m just wondering if the posts above solves the issue, if so please mark the post with the solution.

Thanks!