Hi again David,
writing rules against the option set code would be really useful, and is a
requested feature. In the source field config we could specify wether we want
to use the option code or the name. Will add a blueprint for this.
Markus
> 26. jan. 2016 kl. 18.52 skrev David Hagan :
>
> H
Hi Markus,
OK, as I suspected. I just saw another reference in the documentation for
filters supporting JEXL and was hoping that extended to this as well :-)
Any function that supports looking inside a string for comparison purposes
would be excellent! d2:left and d2:right would work (you might w
Dear David,
these operators are not supported. See chapter 31.5 for the full list that is
supported: http://dhis2.github.io/dhis2-docs/2.21/en/user/html/ch31s05.html
The android and web clients support the same operators.
In table 31.1 you see a list of supported functions, if you create a blu
Quick question to all you tacker experts out there…
For Program Rules (e.g. for event capture), is the extended JEXL syntax
(e.g. =^ for ‘starts with' … or !^ for ‘not starts with’ etc.) valid? And
if so, can we assume this extended skip logic applies to the mobile client?
David
_
4 matches
Mail list logo
