Hi DHIS2 dev team!
I'm working on a decently large tracker program, and got some questions
regarding ProgramIndicators:
- It looks like ProgramIndicator can only refer to DataElements, not other
ProgramIndicators (like "aggregate" Indicators can) - is there any specific
reason for this? Will this
Hi Martin,
On 21 February 2018 at 11:03, Martin Van Aken
wrote:
> Hi DHIS2 dev team!
>
> I'm working on a decently large tracker program, and got some questions
> regarding ProgramIndicators:
>
> - It looks like ProgramIndicator can only refer to DataElements, not other
> ProgramIndicators (like
Hi,
I'm using d2 to fetch some data inside a DHIS2 app. Everything looks to be
working well, until I have a query using event analytics.
As the d2 lib don't have models yet (I think) for this, I'm making direct
calls using get, for example:
return getInstance().then(d2 =>
d2.Api.getApi().get("eve
Hi all
Please Can I have help on this
I am trying export event data from DHIS2 instance to another Instance.
I have the same program on both instances. But got error this error
TypeNombre
Imported 0
updated 0
Ignored 1ErrorEvent.trackedEntityInstance does not point to a valid tracked
entity insta
Hey Martin!
- You can make composite indicators that consists of other program indicators,
but program indicators can not be nested within each other directly.
- Yes- program indicator values are always based on the data in the
analytics_* tables.
Markus
> 21. feb. 2018 kl. 11:03 skrev Martin
Hi Hakim,
this feedback indicates that some of your events are referring to a tracked
entity instance (e.g. person) that does not exist in your destination
system, with the identifier Ug2TixCkiAy.
regards,
Lars
On 21 February 2018 at 11:54, DJIBRIL Hakim wrote:
> Hi all
> Please Can I have h
Hi Markus & Lars,
Thanks both for your answers.
Ok so: programIndicators have a more powerful evaluation engine (with the
d2:condition for example), but indicators can use other indicators.
What I'm not 100% is the consequence of using a (aggregate) indicator to
compose program indicators - is it
On 21 February 2018 at 12:12, Martin Van Aken
wrote:
> Hi Markus & Lars,
> Thanks both for your answers.
>
> Ok so: programIndicators have a more powerful evaluation engine (with the
> d2:condition for example), but indicators can use other indicators.
> What I'm not 100% is the consequence of us
Ok - that's not what I wanted to hear but that's quite logical - so
probably better in the end.
Thanks,
Martin
On Wed, Feb 21, 2018 at 12:18 PM, Lars Helge Øverland
wrote:
>
>
> On 21 February 2018 at 12:12, Martin Van Aken
> wrote:
>
>> Hi Markus & Lars,
>> Thanks both for your answers.
>>
>
Thank you Lars.
it is like there is a issue doing synchronisation data between same DHIS2
instances both 2.28 ( Production and backup on local server).
export/import programs by *Metadata Dependency Export *works well
Not for export/import events. when doing export, we don't have enrollment
infoma
On Wed, Feb 21, 2018 at 11:31 AM, Martin Van Aken
wrote:
> Now I'm trying a event analytics query:
>
> return getInstance().then(d2 =>
> d2.Api.getApi().get("/25/analytics/events/query/jqKm7VLgdzL?stage=tbLC6IHktf0&dimension:ou:VAPI4p81HAz;LEVEL-6&displayProperty=NAME"));
>
> And this show an erro
11 matches
Mail list logo