On 6 June 2011 19:00, Jason Pickering wrote:
> Yeah, well, there is no easy way out here. One only need to review
> this
> http://www.mail-archive.com/dhis2-devs@lists.launchpad.net/msg02059.html
>
> I had a situation recently when implementing a logistics dataset,
> which would have worked great
Yeah, well, there is no easy way out here. One only need to review
this http://www.mail-archive.com/dhis2-devs@lists.launchpad.net/msg02059.html
I had a situation recently when implementing a logistics dataset,
which would have worked great with categories. The problem was that
categories are har
On 6 June 2011 17:44, jason.p.picker...@gmail.com <
jason.p.picker...@gmail.com> wrote:
> KISS. Don't use categories as the model does not fit the use case. Three
> plain old data elements will work.
>
> Just a thought.
>
Tempting thought ... with a few downsides. Its not just 3. 60 job titles
KISS. Don't use categories as the model does not fit the use case. Three plain
old data elements will work.
Just a thought.
Sent from my HTC
- Reply message -
From: "Bob Jolliffe"
Date: Mon, Jun 6, 2011 18:11
Subject: [Dhis2-devs] adding categoryoption
To: "dhis2-devs"
The folk in
Hi,
we will implement support for this in 2.4. We don't support it at the moment
but there is nothing wrong with adding a category option to an existing
category and generating additional category option combos (besides being
slightly complex to implement:)
Lars
On Mon, Jun 6, 2011 at 6:11 PM
5 matches
Mail list logo