DHIS2 Issue with closed facilities

[sybghat (SybghatAllah)]

I need to generate a dataset compliance report in DHIS2 version 2.37.6 but DHIS2 display the aggregate values of all facilities, I don’t need to show the compliance of closed facilities.
I tried a solution where I adjusted the closed date of facility. In this condition I only get the compliance of open facilities that is perfect but what’s the issue in this solution? This solution works only if the facility is closed forever, when I re-open that facility by removing the closed date, the previous reports show compliance of all facilities.

[Gassim (AL-Gassim Sharaf Addin)]

Hi @sybghat

Sorry you’ve not gotten a response. Personally, I have not tried this. I could try to figure it out if you’d like to share steps and which apps you used and I really recommend that so we get other community members involved.

For now I will also ask for support from the core team.

Thank you!
___________________________________________________________

Update:
___________________________________________________________

@sybghat I received a recommendation from @brian to suggest @Scott’s workaround using predictors. The opening and closing reporting rates for OUs doesn’t work if the reporting period isn’t continuous, but in that case the workaround is to use predictors:

@Scott

No there is no way to exclude certain days from the automatic reporting rate summary generated by DHIS2 for daily reporting rates.

There are several workarounds however, the first is that you can generate your own reporting indicator by having a data element that is the number of reporting days each month. This will allow you to do month by month reporting rate analysis. The same could be done using week by week. These can be entered nationally.

Then you will need to use a predictor to count the number of facilities that reported. You’ll have to choose one or a few data elements that would count as your proxy for reporting. The predictor generator will be something like if(DEUID > 0,1,0) or isNotNull(DEUID). You’ll then need to set the sequential sample count and annual sample count to 0. You can schedule the predictor to run nightly in the scheduler app.

This is obviously a bit more advanced, but it does work. Please let me know if you have any questions.