Hi,
OK, I finally figured it out: THIS IS A BUG: when you allocate
datasetelements to a data set, the categorycombo specified for the data
element is supposed to be copied into the categorycomboid field in the
datasetelement table (the last field). This is NOT happening, so all all
datasetelement
Hi,
I've encountered an issue that I find baffling - using a very recent trunk
(2.26, 30 Nov):
1.
I've got a standard category with three options, which in turn was used to
create a similarly named CategoryComto (and the three options appear in the
CategoryComboOption list). It is definition-wise
You can also use category combos on the data sets to distinguish them. This
is a bit of a "free-form" dimension, which would allow the same data
element to exist in two separate data-sets, but possibly with a different
attribute option combo.
On Fri, Dec 2, 2016 at 11:13 AM, Archana Chillala wro
Yes, this is expected. Please make sure that two data sets having same data
elements are not assigned to the same organization unit. Else, data value
gets over-ridden.
Archana Chillala
Application Developer
Email archa...@thoughtworks.com
Telephone +91 9100960533 <+91+9100960533>
[image: ThoughtWo
Hi
Another quirkie: When editing the NAME of a data set section by e.g. adding
a prefix or similar, the cursor will jump to the end of the string after
entering one character. If you then move the cursor back again, it don't
happen again. So it only happens (Chrome) the first time you put the curs
5 matches
Mail list logo