Thank you Jason,
I have used a custom form for the data entry screen in the online version/web
version, however the ordering in that form is not respected by the android data
capture app either.
I will try a section form to see, but if there are any other thoughts I am
interested to know.
Ma
Hi Blake
Yes, custom forms will absolutely not work with Android for sure, as you
are just using custom HTML there to provide the ordering. There is nothing
in the database to determine the order.
However, section forms should theoretically work, but the Android devs
would need to confirm this.
Morten
Sure - I just wanted to know if (1) it's a known bug; and (2) what kind of
bug it is. Somebody else must have encountered the same, and I've got a
feeling I saw some posting related to this (might even have been Elmarie,
cannot recall).
Regards
Calle
On 6 February 2017 at 09:43, Morten Ol
Hi
Just talked to Elmarie - she think the problem might be related to
passwords not being recognised because they are somehow linked to the ID in
the User table And that rings a bell - but if correct, it basically
means that users cannot be exported from one instance to another
Regards
Ca
Hi Calle
User passwords are not exported, that is correct.. but that has never
worked. What -is- supported is to import user with a -new- passowrd, so you
can do userCredentials.passowrd: "new password for me" and it will be
encrypted and stored in the instance... but password are not exported, an
Morten,
Mmm - but if that's the case, why the radically different result for:
Case 1: Selected Export Meta-date with sharing -> Users (only that ticked)
-> JSON format (2.24). When imported into a slightly different instance
where 95% of users where the same, EVERY SINGLE user were ignored.
Case
Hi Blake,
Section forms are supported and order of data elements within them is
respected on android data capture.
However, as Jason already has mentioned, custom forms are not supported in
android data capture and probably won’t be in the future.
Best regards,
—
Araz Abishov,
Android developer,
Morten
I've created a JIRA bug issue - dhis2-664
Regards
Calle
On 6 February 2017 at 11:15, Calle Hedberg wrote:
> Morten,
>
> Mmm - but if that's the case, why the radically different result for:
>
> Case 1: Selected Export Meta-date with sharing -> Users (only that ticked)
> -> JSON format (
Hi Bob,
deployments like the ones in MSF with online/offline instances will
definitely benefit from the approach that you described.
cheers
Marta
Marta
On 3 February 2017 at 12:55, Bob Jolliffe wrote:
> Lars, has there been any recent discussion over adopting an ubuntu-style
> approach of tw
Hello,
In one of our customers' DHIS2 that we are integrating through the API we
have a weird situation: we have org units we see through the API but not
using the UX.
Specifically, there seems to be a lot of org units at the level 1 (top)
while there should be only one (the country). The UI seems
Hi Martin,
the problem is usually that the user you are logged in as (the "current
user") is assigned to a single root org unit. You can check that through
the API (user -> organisationUnit) and the user app.
After this user was created, I guess someone has created additional org
units through t
Ok, thanks a lot. I understood the "multiple" root, but this explains why I
have two different situation.
Regards,
Martin
On Mon, Feb 6, 2017 at 2:28 PM, Lars Helge Øverland wrote:
> Hi Martin,
>
> the problem is usually that the user you are logged in as (the "current
> user") is assigned to
Yes sure
This problem occurred on v2.25 and last morning, I just try test with v2.26.
the same issue...
Sent from Meizu M2 Note
Original message
Sender: Jason Pickering
Time: Mon 2/6 08:18 PM
To: channara rin
Cc: DHIS 2 Developers list
Subject: Re: [Dhis2-devs] user role
Sounds like a bug in 224 yes. I will have to look into it, it might take
some time (as these issues often do...)
--
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo
http://www.dhis2.org
On Mon, Feb 6, 2017 at 5:52 PM, Calle Hedberg
wrote:
> Morten
>
> I've created a JIRA bug issue
Yes! For the implementations I've been following at country levels, a
slower release pace or at least the possibility to only upgrade once a
year would be welcome. Not every implementation has the capacity to be
agile, so there is a need for very stable releases. Even though upgrades
usually ha
Hi Vanya,
we have created filters for features and improvements per upcoming release.
For each issue we now separate between those which are "internal" to the
system (like refactors) and those of "general interest" (functional
features), and in the mentioned filters we only include "external" feat
Hi Morten,
At long last I am revisiting using the enhancement you made for including
the displayName in the Error reports documented here, with the
importReportMode import parameter:
https://dhis2.github.io/dhis2-docs/master/en/developer/html/webapi_metadata_import.html
However in our case this
Hi Devs,
If possible, I’d be very grateful for some advice around authorities in 2.25.
In order to help prepare for PSI’s upgrade to 2.25, we’ve done an analysis of
changes in Authorities between 2.22 and 2.25. I couldn’t find a database table
containing Authorities, and the list of Authoritie
Thanks for the info Lars.
Regards
Vanya
Sent from my iPhone
> On 06-Feb-2017, at 11:10 PM, Lars Helge Øverland wrote:
>
> Hi Vanya,
>
> we have created filters for features and improvements per upcoming release.
> For each issue we now separate between those which are "internal" to the
>
19 matches
Mail list logo
