Hi, Storing age as year doesn't make sense as that number will always be relative to the date the age was entered. By storing date of birth, we are always able to calculate a correct age.
Would be nice if you could create us a jira issue requesting for age type data elements / attributes to be calculated in our output / analytics modules. -- Abyot A. Gizaw. Senior Engineer, DHIS2 University of Oslo http://www.dhis2.org On Thu, Mar 23, 2017 at 9:27 AM, Archana Chillala <archa...@thoughtworks.com > wrote: > Hi > > We are using DHIS version 2.26. We are exploring the new value type "*Age*" > that has been introduced with this release. On the UI, when we enter a > date, it calculates the age in years, months and days perfectly. But we > observe that the calculated age in years is not stored in the DB. The value > of an Age type data element is stored only as a date (YYYY-MM-DD) in the > database. We would like to use the age in years in analytics on the > visualisation apps. We have tried using program indicators for the same, > but that did not work as expected. > > Could you please suggest how we could leverage the use of age in years, > given the existing functionality. > > > > *Cheers*, > > Archana Chillala > Application Developer > Email archa...@thoughtworks.com > Telephone +91 9100960533 <+91+9100960533> > > [image: www.thoughtworks.com] <http://www.thoughtworks.com> > > _______________________________________________ > 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 > >
_______________________________________________ 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