Hi Bram,
yup I see your point and some times I am sure it's useful. Personally I
still think its a bad idea, as you easily get into trouble later. In terms
of design we are saying that groups are for output/analysis, and data set
for data input/capture. So the moment an org unit should belong to
Thanks, I actually had tried that with no effect - but by sheer
coincindence, I discovered what was the matter today:
I was going to change the icon for an OU group, and noticed that the forms
I wanted to get rid of had been assigned to several OU groups (one of which
contained most of the OUs in
Hi Lars,
I can see that this option is confusing to some, but it's very useful to
others so please reconsider removing it - let me explain: in settings with
highly dynamic org units (i.e. new org units are being added on a regular
basis), assigning a data set or a program to one or more org unit
In my 2.15 db my existing forms show up in data entry for all OUs even
though I've tried to restrict them to just level 4 (they had previously
been assigned to all OUs by mistake). The restriction/assignment works for
new datasets, but not for the existing ones.
How can make sure the exisiting
Right, but would you have any idea what causes my problem with dataset
assignment and how to fix it?
On Jul 25, 2014 2:16 AM, Lars Helge Øverland larshe...@gmail.com wrote:
On Thu, Jul 24, 2014 at 7:53 PM, Knut Staring knu...@gmail.com wrote:
One method to do this is to export the datasets
5 matches
Mail list logo
