Hi Busyoe, what happened here is simply that we have removed the web user interface in "individual records" module for capturing single events with registration. You will find the same functionality with a simpler and better user interface in the new "event capture" app.
The database (or dhis service layer) does not change at all due to this, and is not related to aggregation queries. For upgrading between 2.14 and 2.15 you must run the upgrade script which you can find next to the war file on dhis2.org/downloads, direct link: http://www.dhis2.org/download/resources/sql/rename-patient-to-trackedentity.sql This will rename the tables from patient* to trackedentity* cheers Lars On Wed, May 7, 2014 at 4:25 PM, Adebusoye Anifalaje <[email protected]> wrote: > Does this change mean that data entered for single event without > registration will be stored in the trackedentitydatavalue table instead of > patientdatavalue table. I am working on a single event without registration > program. Aggregation does not work at all for all the aggregation queries. > I copied the data from the patientdatavalue table to the > trackedentitydatavalue table and this works (crooked way to go about it but > experimenting). It would be useful to know which table the event capture > app stores data and how this might help my case. > > Can anyone advise? I have already logged an entry on the user list about > the requirements. > > Thanks. > > Regards, > > Busoye > > _______________________________________________ > Mailing list: https://launchpad.net/~dhis2-devs > Post to : [email protected] > Unsubscribe : https://launchpad.net/~dhis2-devs > More help : https://help.launchpad.net/ListHelp > >
_______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : [email protected] Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
