Hi Uwe and Lars,
Thanks for highlighting the importance. As Uwe said, if DHIS2 to continue
as a data warehouse, aggregating from tracker will be important. I'm sure
there are many who is having the same issue. And in future also there will
be many who will face this when moving into patient record
Thank you.
Sam Kasozi
+256 788-993-565
Skype: sam.kasoziug
On Tue, May 10, 2016 at 6:37 AM, Morten Olav Hansen
wrote:
> Hi Sam
>
> Just had a look, the parameter should be strategy=X not importStrategy=X,
> I will update the docs
>
> --
> Morten Olav Hansen
> Senior Engineer, DHIS 2
> Universit
Hi Sam
Just had a look, the parameter should be strategy=X not importStrategy=X, I
will update the docs
--
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo
http://www.dhis2.org
On Mon, May 9, 2016 at 12:51 PM, Sam Kasozi wrote:
> The confusion in adding the trackedEntity was whet
It might seem very superficial, but I think the ability to select colors is
actually important - just as it is for Legends in GIS (in fact, it would be
nice to be able to apply the legend colors to charts as well).
Knut
On Thu, May 5, 2016 at 6:27 PM, Knut Staring wrote:
> Yes, I have asked the
Thanks Araz for the advice, have been able to resolve now by changing some
of the user rights.
On Mon, May 9, 2016 at 2:28 PM, Araz Abishov wrote:
> Hi Shurajit,
>
> Are you sure that given user has write access rights (is able to send
> reports) to the server?
>
> You can also send me applicati
Hi Laura,
for legacy reasons it is currently "Administrate data mart". We need to
update this to reflect that analytics has replaced data mart.
regards,
Lars
On Mon, May 9, 2016 at 11:57 PM, Laura E. Lincks <
laura.lin...@icap.columbia.edu> wrote:
> A quick question, hopefully...
>
> which us
A quick question, hopefully...
which user roles or authorities allow for manual creation of Analytics
Tables from the front end via the Reports App? I can't find an authority
which maps to the process. I know our Superuser roles allow access to the
process but can't easily determine what, if any,
Hi Olav,
yes this sounds sensible.
On Mon, May 9, 2016 at 9:20 AM, Olav Poppe wrote:
> Let me chip in here:
> - finding a way around the "Indicators cannot be specified as filter."
> issue.
>
Yes, this on the plan for 2.24:
>
> Then a few things which I understand is difficult with the cu
On Mon, May 9, 2016 at 9:03 PM, Lars Helge Øverland wrote:
> Hi Olav,
>
> yes this sounds sensible.
>
>
>
> On Mon, May 9, 2016 at 9:20 AM, Olav Poppe wrote:
>
>> Let me chip in here:
>> - finding a way around the "Indicators cannot be specified as filter."
>> issue.
>>
>
>
>
On the plan for 2.2
Hi Martin,
I would recommend that you go with the analytics API instead of the report
table resource, as the former is a lot more flexible.
Your request is a good one and since it was a quick fix I have added
support for the IN_GROUP- syntax in trunk and 2.23. New download
ready in 20 minutes.
Y
This looks to be working, even if I'm not clear on the relationship between
dates & periods.
Last but not least - I had two ideas to make this work: either use the
reportTable as API source (pro: it already existed) or create the
equivalent using the analytics web API. My problem in that second ca
I'm honestly not sure, Lars would have to answer that. The date itself is a
normal date object, which means multiple date formats are supported.
@Lars ?
--
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo
http://www.dhis2.org
On Mon, May 9, 2016 at 3:37 PM, Martin Van Aken
wrote:
Hi Martin
You can use ou and date as query parameters
--
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo
http://www.dhis2.org
On Mon, May 9, 2016 at 3:18 PM, Martin Van Aken
wrote:
> Hi,
> We currently have a reportTable used to generate a PDF report. We now want
> to be able to
Hi,
We currently have a reportTable used to generate a PDF report. We now want
to be able to extract the exact same info using the API. I've seen that
there is a reportTables//data.json option, but I cannot find how to
pass it parameters (our table take two - the organisation unit and the
period).
Hi Pramil & Lars,
actually I think that Pramil is adressing a very valid problem. In my current
understanding of DHIS2 I wouldn't be able to propose any better solution than
using Lars' analysis api and an external tool (php, r, kettle etc) to read the
results and fill them into the datasets.
How
Let me chip in here:
- finding a way around the "Indicators cannot be specified as filter." issue.
Then a few things which I understand is difficult with the current chart
framework, but that would still be nice to have some day…:
- more flexibility in the "layout", e.g. two axis with different s
16 matches
Mail list logo
