but I can see that working - I mean if a data element has form name it
displays otherwise falls back to data element full name. it could be a
cache issue - have you cleared and tried?
On Thu, Aug 21, 2014 at 1:21 PM, Abyot Gizaw wrote:
> ok it is data element form name - now I got it.
>
>
> On
ok it is data element form name - now I got it.
On Thu, Aug 21, 2014 at 12:59 PM, Rodolfo Melia wrote:
> About the form name: in the previous version, and similar to the behaviour
> of Data Sets on the aggregated side, if a Data Element has a value on the
> field 'Form Name', that's the label t
About the form name: in the previous version, and similar to the behaviour
of Data Sets on the aggregated side, if a Data Element has a value on the
field 'Form Name', that's the label that it is rendered on the data-entry
screen. At the moment the Data Element name (which I referred on my email
as
Since these are quite a number of features, hence a bit of work, fixing
them in trunk/2.17 is easier. but if you insist for 2.16 as well, I will
try to replicate.
just a question on the form name part - what do you mean "instead it uses
the full name"? I know the form name is not displayed, so you
Hi Abyot - that's great news. I guess that we are talking about 2.17? or
are they likely to make it to 2.16?
R
*Rodolfo Meliá*
*Principal | *rme...@knowming.com
Skype: rod.melia | +44 777 576 4090 | +1 708 872 7636
www.knowming.com
On Thu, Aug 21, 2014 at 7:56 AM, Abyot Gizaw wrote:
> H
Hi Rodolfo,
Thank you for the feedback. Yes those features are missing, will try to
implement them.
Abyot.
On Thu, Aug 21, 2014 at 12:35 AM, Rodolfo Melia wrote:
> Hi - we have been working with the latest 2.16 (Aug 20), and we noticed a
> couple of omissions (or bugs?) on the event capture a
6 matches
Mail list logo
