Re: [Dhis2-users] [Dhis2-devs] Limit on data attribute - category options

Yes, we do have fixed relationships within those categories, so this works for us! This implementation is much safer as well since it will not require a data entrant to filter through the different categories. Thank you. Sam Kasozi +256 788-993-565 Skype: sam.kasoziug On Mon, Apr 3, 2017 at 11

[Dhis2-users] CLARITY ON DEFINITIONS FOR COUNTS IN PROGRAM INDICATORS

Can someone please define for me what i expect to get when i create an indicator based on the following in the expression description: 1-Count of events,what will the indicator count 2-Count of enrollment,will this count all enrollments within the program 3-Count of tracked entity instances,what w

Re: [Dhis2-users] [Dhis2-devs] Limit on data attribute - category options

Dear all, This is also a requirement for us but we are wondering if it is possible to implement a "user" visibility of the data sets category options. For example a user from Spain only being acessible to the Spain Implementer Partners or a user only accessing to the category options where he's in

Re: [Dhis2-users] [Dhis2-devs] Limit on data attribute - category options

Yes, you can use "Sharing" controlled with user groups. However, it can get complex quickly, and usually requires very careful user management routines, coupled with automatic scripting to get it right. On Mon, Apr 3, 2017 at 9:31 AM, Marc Garnica wrote: > Dear all, > > This is also a require

Re: [Dhis2-users] [Dhis2-devs] Limit on data attribute - category options

Hi Marc, as Jason says you can use the sharing (docs ) solution for this by sharing each category option (representing e.g. partners) appropriately. This can be done in many ways depending on the level of complexity of your organization. At

Re: [Dhis2-users] [Dhis2-devs] Limit on data attribute - category options

Nice solution! We will give a try. Thank you very much! Marc 2017-04-03 10:08 GMT+02:00 Lars Helge Øverland : > Hi Marc, > > as Jason says you can use the sharing (docs > ) solution for > this by sharing each category option (representing

[Dhis2-users] PERIOD IN TRACKER CAPTURE

Am pretty sure Absolom brought a topic on this issue but am not sure how it ended.however i am experiencing the same thing. Some of the entities that were enrolled last year,i am only able to see dates for November and December 2016.This means i am failing to capture events for 2017. Secondly,som

Re: [Dhis2-users] [Dhis2-devs] PERIOD IN TRACKER CAPTURE

Hello Stanley, Are you sure that those entities which is enrolled this week has captured date/period? Where does it fail to show the dates? Do the dates appear when you search the entity on the server? Regards, Erling On Mon, Apr 3, 2017 at 12:39 PM Stanley Kalyati wrote: > Am pretty sure Abso

Re: [Dhis2-users] [Dhis2-devs] PERIOD IN TRACKER CAPTURE

Hi Stanley, We have made some improvements on this (for 2.26), mail was sent on March 2. I think you were part of the conversation. Are you sure you are running the latest 2.26? -- Abyot A. Gizaw. Senior Engineer, DHIS2 University of Oslo http://www.dhis2.org On Mon, Apr 3, 2017 at 3:28 PM, Sta

Re: [Dhis2-users] [Dhis2-devs] PERIOD IN TRACKER CAPTURE

Thanks Abyot I am running on 2.25. This means i need to upgrade to 2.26 then. Thank you My regards Stanley On Mon, Apr 3, 2017 at 3:42 PM, Abyot Asalefew Gizaw wrote: > Hi Stanley, > > We have made some improvements on this (for 2.26), mail was sent on March > 2. I think you were part of th

Re: [Dhis2-users] [Dhis2-devs] PERIOD IN TRACKER CAPTURE

Yes. The feature - still limited - is too complex to be back-ported for 2.25. We need more time and thinking to support periods in tracker/event capture. *Note: As mentioned in the earlier discussion, what is saved behind the scene is only event dates not period. The implication of this is that th