Great! Thanks Morten
On Wed, May 11, 2016 at 5:48 AM, Morten Olav Hansen
wrote:
> This is now fixed and backported down to 2.21, please give our servers
> some time to build new WAR files.
>
> --
> Morten Olav Hansen
> Senior Engineer, DHIS 2
> University of Oslo
>
This is now fixed and backported down to 2.21, please give our servers some
time to build new WAR files.
--
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo
http://www.dhis2.org
On Wed, May 11, 2016 at 10:39 AM, Morten Olav Hansen
wrote:
> Hi,
>
> I haven't done
Hi,
I haven't done this fix yet, but I think until we have a better solution I
will set it to current date, saving it as null in the database is not a
good option.
--
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo
http://www.dhis2.org
On Wed, May 11, 2016 at 10:37 AM, Jose
Hi Morten,
many thanks for your quick answer. I think it is ok to default to current
date. (or at least I can not think in why not?)
Would it be possible to have it backported to 2.22 as well? It is a bit
urgent and important for us :) (otherwise we may have some issues with our
android apps)
Hi Aamer,
okay - this seems to work well on the demo (see the Voucher program). We
will need more info or a privately shared login to assist.
It is likely some sort integrity issue with the category* structure. This
SQL script
** Changed in: dhis2
Milestone: None => 2.23
** Changed in: dhis2
Assignee: (unassigned) => Morten Olav Hansen (mortenoh)
** Changed in: dhis2
Importance: Undecided => Medium
--
You received this bug notification because you are a member of DHIS 2
developers, which is subscribed to
Hi Hari,
we have not started developing the tracker/event approvals feature as we
are a bit uncertain about the requirements here. We will make sure to reach
out to you before starting development to incorporate your needs.
regards,
Lars
On Tue, May 10, 2016 at 9:33 PM, Hari Krishna
Hi,
we have recently fixed an issue with analytics which could lead to the
analytics API returning the an unexpected organisation unit in the response.
This issue affects you if all of these conditions apply:
- there is an server-side cache
Hi Olav,
Just a note that in 2.23 Tracker Capture you are not able to complete a
program stage if required fields are missing. Each datavalue is saved once
captured though and you are still able to close a form with only some
fields captured. But at least the enforcement on completing a program
Hi Lars,
is approvals for event data available in DHIS 2.22? But in the blueprint
status is set to 'not started' and milestone is set to '2.24'. Let us know
if this feature is already rolled out in DHIS 2.22. If it is please update
this blueprint
Dear Aamer,
Data elements with domain type Tracker do not use category combos, please
use optionsets.
Look at this for more information
http://dhis2.github.io/dhis2-docs/master/en/user/html/dhis2_user_manual_en_full.html#optionSet
Thank you and Kind Regards
*Immarcqulate. A (Emma Kassy) *
Public bug reported:
Discovered in v2.22
Using the event export function, selecting 'include descendants of
organisation unit'.
We could see events in the event reports for a level 6 org unit, for
which we wanted to export the events into CSV. Using the event export
function, we selected the
Hi
We are using the latest version of 2.23 (revision #22911) When using 'Event
capture' functionality, we found the below issue.
We created a program without registration and attached category combination
of type attribute to it. In the Event Capture page, upon selecting the
program and the
Hi Olav!
Let me address your second point :)
> 10. mai 2016 kl. 15.45 skrev Olav Poppe :
>
> Hi devs,
> first, I’ve been working on a custom data entry form for tracker (2.22 and
> 2.23). I’ve customised the same form as programmes with and without
> registration, and I
Hi devs,
first, I’ve been working on a custom data entry form for tracker (2.22 and
2.23). I’ve customised the same form as programmes with and without
registration, and I notice that in Tracker Capture everything is seemingly
"magnified" by 25% or so compared to Event Capture (e.g. rows that
Public bug reported:
Applies to Tracker in 2.23. When using "First stage appears on the same
page with registration" option program rules are not applied.
** Affects: dhis2
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of DHIS 2
Public bug reported:
The program stage options for
- Auto-generate event
- Open data entry form after enrollment
are not respected in 2.23 - event must be created manually. Reproduced on
play.dhis2.org/demo (child programme).
** Affects: dhis2
Importance: Undecided
Status:
Sure, I'll take a look tonight.
On Mon, May 9, 2016 at 8:25 PM, Lars Helge Øverland wrote:
> ** Changed in: dhis2
> Assignee: (unassigned) => Ken Haase (kh)
>
> --
> You received this bug notification because you are a bug assignee.
>
Interesting, I didn't try with with tracker.
The application get meta-data just from dataSets, the main goal is to
combine properly organisationUnit Ids with dataElements Ids.
The xml with dataSets contain just that information.
Further development could include the information about the type
19 matches
Mail list logo