Hi Lars,
Following up on this discussion - has there been any review of the current
limitation?
Thanks.
Regards,
Dapo Adejumo
> On 16 Mar 2016, at 18:04, Elmarie Claasen wrote:
>
> Hi all,
>
> We also had this issue once. Maybe one should then get a warning when you add
> >200 users to Userg
Hi Devs,
I am trying to update one attribute value for a data element via the Web API in
2.22 and there is no success - the error thrown is shown below. The syntax is
in the format curl -X PATCH -d "{\"attribute\": \"\"}" -H "Content-Type:
application/json" -u user:pass
http://localhost:808
Hi Devs,
I am trying to update one Data element attribute (name) using a patch update
command , example below
"curl -X PATCH -d "{\"name\":\"New Data Element Name\"}" -H "Content-Type:
application/json" -u xx:xx
http://localhost:8080/api/dataElements/uidxxx/name”
The command fails
+1 to this suggestion.
Regards,
Dapo Adejumo
> On Oct 27, 2016, at 2:53 PM, Olav Poppe wrote:
>
> Hi devs,
> I’d like to propose adding support for using actual and expected number of
> reports in indicator formulas. It would serve a similar purpose as the
> current "orgunit group count" fu
Hi Devs,
Looks like use of indicator group sets as data dimensions in analytics is still
not supported - How and where can the new classification tag
(Input,Activity,Output,Impact) on indicators in 2.22 be accessed in the
analysis apps?.
Thanks
Regards,
Dapo Adejumo
+2348033683677.
_
Hi Jan,
This is great news - will this also come with the ability to turn off
background completely in 2.23? , as a user setting perhaps?
Regards,
Dapo Adejumo
+2348033683677.
> On 29 Mar 2016, at 10:09, Jan Henrik Øverland
> wrote:
>
> Hi David,
>
> OpenStreetMap will be the default backgro
Hi Gerald,
Did you recently edit the affected data elements? Can you view the data in
the data entry screen?
If yes - can you also check sharing settings on these data elements?
On Sun, Aug 23, 2015 at 9:10 PM, gerald thomas
wrote:
> Dear All,
> Thanks for all your responses.
> Please find the a
Hi
Thanks Calle for bringing in the data management dimension.
Definitely a tricky issue with no easy solution.
As a start, it will be a great idea to actually get the current
functionality of tagging "compulsory data elements" for datasets and
assessing completeness based on that selection to
ing
>> Zeros for the services that are not applicable though personally I wont
>> recommend it as it tremendously increases database size. I can see 70% of
>> data is zeros in many of the state applications. The second option can
>> workout for instances where we have so
9 matches
Mail list logo