verview. We are still in the planning phase for the coming year.
>
> https://www.dhis2.org/roadmap
>
>
>
> best regards,
>
> Lars
>
>
>
>> On Sat, Feb 4, 2017 at 8:32 AM, Vanya Seth wrote:
>> Hi Devs
>>
>> Thanks for the 2.26 release a
Hi Devs
Thanks for the 2.26 release and the great features. Congratulations once
again!
Can you please point to the documentation for the upcoming releases? Wanted
to get a sense of features that are lined up for the coming releases.
Thanks for the help.
--
With Regards
Vanya
ThoughtWorks Techn
HI Morten
Hope you are doing well.
Can you please have a look at these issues as well?
Regards
Vanya
On Fri, Oct 21, 2016 at 3:15 PM, Aamer Mohammed
wrote:
> Hi Lars/Morten,
>
> Recently we did a DHIS upgrade test to upgrade our instances from 2.21 to
> 2.24. We started with 2.21 instance hav
Sure. No problem.
Regards
Vanya
On Mon, May 23, 2016 at 4:16 PM, Lars Helge Øverland wrote:
>
>
> On Mon, May 23, 2016 at 12:31 PM, Vanya Seth
> wrote:
>
>> We would also look into some possibilities ourselves and get back if
>> there's something worth discuss
We would also look into some possibilities ourselves and get back if
there's something worth discussing.
Regards
Vanya
On Mon, May 23, 2016 at 3:58 PM, Vanya Seth wrote:
> Thanks a lot for the information Lars.
>
> Really appreciate it.
>
> Regards
> Vanya
>
> On
to support it - still pondering how to solve this in a way which
> offers required performance and flexibility.
>
>
> best regards,
>
> Lars
>
>
>
>
>
>
>
>
>
>
>
> On Tue, May 17, 2016 at 1:13 PM, Vanya Seth
> wrote:
>
>> Hi dhis-devs
&
Hi devs and users
Would anyone with relevant experience in this, help us understand this
better?
Regards
Vanya
On Tue, May 17, 2016 at 4:43 PM, Vanya Seth wrote:
> Hi dhis-devs
>
> We are looking at doing some analysis for the Anonymous events. For which
> we are trying to set up
Hi dhis-devs
We are looking at doing some analysis for the Anonymous events. For which
we are trying to set up some program indicators.
Currently the issue that we face is that the events that DHIS2 considers
for calculations within a specific reporting period (week, month) in event
reports/visua
Hi Morten
So, I am hoping, if its a conflict you will send the ImportSummary status
as Error or Warning.
And would you consider adding a first class status field on the
ImportSummaries object as well. I think it makes sense, as it allows the
consumer of the API to take an overall decision about t
case, maybe after resolving the conflict of the category
>> option identifier: U8vu31ybiD5 , Aamer will have to retry by setting the
>> Dry Run at "No"
>>
>> Hope this helps...if I'm not out of the lines..
>>
>> Henri
>>
>>
>
Hi Morten
As mentioned earlier. We are working on the events data sync. And this
specific issue is in the /events POST API.
The idea is to retry the event data sync if there is any conflict (where
essentially some data has not sycned ). Treating a CONFLICT as a SUCCESS
does not sound like a good
Hi Morten
In case if its not already handled. Same might be the case for DataSets.
UserRoles have dataset association as well.
Regards
Vanya
On Wed, Mar 23, 2016 at 9:39 AM, Morten Olav Hansen
wrote:
> Hi again
>
> I'm guessing this is related the circular nature of our metadata, we are
> impo
12 matches
Mail list logo
