HI Olav,
it's a good observation. It is currently a known limitation (for me at
least;) of the analytics reporting rate API. Currently it only shows
expected reports for where there are at least 1 complete registration.
I am working on it and hope to fix this for 2.25.
Lars
On Wed, Aug 31,
Hi devs, does anyone have an explanation for this?
Olav
> 23. aug. 2016 kl. 09.52 skrev Olav Poppe :
>
> Hi devs,
> I’m a bit confused about the way the completeness analytics API works - I
> suspect there might be a bug when looking at the facility level (i.e. the
> level
Hi devs,
I’m a bit confused about the way the completeness analytics API works - I
suspect there might be a bug when looking at the facility level (i.e. the level
where data is entered):
- there is no difference between "not expected to report" and "not reported" -
I would expect not reported
3 matches
Mail list logo