However, there could be a workaround. Given that you have a numerical data element which is always filled for the stage, can use the event count variable in the expression:
V{event_count}
and use that data element in the expression where you filter on a a value greater > 0, e.g.
#{A03MvHHogjR.wQLfBvPrXqq} > 0
This way, the filter will filter out event which do not have a value for that data element in that stage.
However, there could be a workaround. Given that you have a numerical data element which is always filled for the stage, can use the event count variable in the expression:
V{event_count}
and use that data element in the expression where you filter on a a value greater > 0, e.g.
#{A03MvHHogjR.wQLfBvPrXqq} > 0
This way, the filter will filter out event which do not have a value for that data element in that stage.
the reason you are not seeing the program indicator in tracker capture for the particular TEI below is the program indicators filter. There is a shortcoming when combining the filters with indicators shown in the data entry form. Working on fixing this, but in the meantime we can probably help with a workaround in the data entry form.
Did you want to show the number of events of the “Contact” program stage, assuming there is other program stages that you do not want to count events from?
However, there could be a workaround. Given that you have a numerical data element which is always filled for the stage, can use the event count variable in the expression:
V{event_count}
and use that data element in the expression where you filter on a a value greater > 0, e.g.
#{A03MvHHogjR.wQLfBvPrXqq} > 0
This way, the filter will filter out event which do not have a value for that data element in that stage.
Yes, I want to have the number of events of a specific program stage as a program indicator (hide or show in the tracker capture) because later this program indicator will be used to calculate other indicators.
I’ve try what Lars suggest me to do that’s why you see the example in the demo but it doesn’t work.
Hi there Ramaso,
the reason you are not seeing the program indicator in tracker capture for the particular TEI below is the program indicators filter. There is a shortcoming when combining the filters with indicators shown in the data entry form. Working on fixing this, but in the meantime we can probably help with a workaround in the data entry form.
Did you want to show the number of events of the “Contact” program stage, assuming there is other program stages that you do not want to count events from?
However, there could be a workaround. Given that you have a numerical data element which is always filled for the stage, can use the event count variable in the expression:
V{event_count}
and use that data element in the expression where you filter on a a value greater > 0, e.g.
#{A03MvHHogjR.wQLfBvPrXqq} > 0
This way, the filter will filter out event which do not have a value for that data element in that stage.
I want to count a distinct number of events for a given stage.
currently I have a PI of Event analytical type
–v(event_count) as an expression
–and my filter have v(program stage) =UID
This works however it is not deduplicated, the moment I change analytic type to enrolment and v(tei_count) the PI will not pull as I thought that will deduplicate the events count.
Best Regards,
how do I reference the exact program stage to count events for ?
Please note I do not have a numeric data element or any other unique data element that is overall populated completely
I think one way to approach this is by using a program rule. The program rule will count the number of events in the selected program stage in the configuration and then assign the V(event_count) to a data element or TEA:
I don’t think it should haveto be unique data element, as the filter should pull the program stage uid as well as the data element uid. I see your point about “overall populated completely” which is definitely relevant—perhaps there are a collection of data elements that would always be answered, and thus you could have a #{A03MvHHogjR.wQLfBvPrXqq} != ‘’ || #{A03MvHHogjR.wQLfBvPrXqq} != ‘’ || #{A03MvHHogjR.wQLfBvPrXqq} != ‘’