Hi,
I might have misunderstood both the issue and your example, Jason, but my
understanding was that the problem here is that duplicate codes within an
option set is allowed, while your example refer to options having the same
codes in different option sets?
I would in any case argue for havin
I am not sure what the source of the ambiguity actually is. A given data
element is linked to a single option set (at least currently). Since every
data value is tied to a data element and the data element is in turn linked
to an option set, I am not sure what the source of the ambiguity is?
I th
Hi Jhansi,
Your second suggestion is a good one with slight modification: introduce a
setting for the option set to enforce unique option codes. This makes it
optional per option set. The reason for this is that there are use cases where
the option code is used as a value for example If the opt
Hello DHIS Devs,
In DHIS, event capture app while registering an event, we have noticed that the
event dataValues (for the dataElements with optionSet) are posted with the
selected option code. Similarly, in the event list the event data values are
mapped with the option code to show the select
4 matches
Mail list logo
