Nicely spotted. Codes is used in analytics, but names in the client side
calculation. Will fix so codes isused in TC for indicators.
Markus
> Den 28. jun. 2016 kl. 16.12 skrev Olav Poppe <olav.po...@me.com>:
>
> Hi devs, I’ve only tested this in trunk:
> when configuring program indicators the «Filter» description says: «Use
> option codes for option set references.» However, in TC data entry, looking
> in the console, it looks like name is used (‘Months’ is name, ‘MONTHS’ is
> code).
>
> Evaluation ended up as:
> ('' && d2:yearsBetween('2000-01-01','') < 5) ||
> ('Months' == 'DAYS' && 7 < 1825) ||
> ('Months' == 'WEEKS' && 7 < 520) ||
> ('Months' == 'MONTHS' && 7 < 60) ||
> (‘Months’ == 'YEARS' && 7 < 5)
>
> Assume this might be a TC-only discrepancy (e.g. that in analytics, CODE is
> actually used), though I’ve not yet been able to test that yet.
>
> Regards
> Olav
>
>
>
_______________________________________________
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp
