Re: [Dhis2-devs] [Dhis2-users] Feature roadmap for the next releases

[Vanya Seth]

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 
> system (like refactors) and those of "general interest" (functional 
> features), and in the mentioned filters we only include "external" features.
> 
> You can find links to those filters here, which should give you a decent 
> overview. 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 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 Technologies
>> Hyderabad
>> 
>> --Stay Hungry Stay Foolish!!
>> 
>> ___
>> Mailing list: https://launchpad.net/~dhis2-users
>> Post to : dhis2-us...@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~dhis2-users
>> More help   : https://help.launchpad.net/ListHelp
>> 
> 
> 
> 
> -- 
> Lars Helge Øverland
> Lead developer, DHIS 2
> University of Oslo
> Skype: larshelgeoverland
> l...@dhis2.org
> http://www.dhis2.org
> 
___
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help   : https://help.launchpad.net/ListHelp

[Dhis2-devs] FW: Authorities in 2.25 (vs 2.22)

[Sam Johnson]

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 Authorities in the DHIS2 documentation 
doesn’t appear to have been updated since version 2.22, so I’ve scraped the 
‘Authorities’ drop-down in the ‘Create Role’ screen to obtain lists of 
Authorities in 2.22 and 2.25 for comparison.

The following Authority changes seem fairly straightforward, and were 
documented as part of DHIS2 releases:

RETIRED (functionality no longer exists)

· View data browser

· See Data Set Maintenance module

· See Organisation Unit Maintenance module

· Scheduling case aggregate query builder
INTRODUCED (new functionality)

· Delete External Map Layer

· Add/Update Private External Map Layer

· Add/Update Public External Map Layer

· Add/Update Legend

· Delete Legend

· Delete Legend Set

· Add/Update Private Legend Set

· Add/Update Public Legend Set

· Metadata sync

· Add/Update Predictor

· Delete Predictor

· Delete Program Indicator Group

· Add/Update Private Program Indicator Group

· Add/Update Public Program Indicator Group

· Add/Update Push Analysis

· Delete Push Analysis

· See Usage Analytics module

I’m guessing the following Authorities have been retired because they duplicate 
existing (more refined) Authorities?   Could you confirm whether this guess is 
correct?
RETIRED AS REDUNDANT?:

· Option Set Management

· Constant Management
DO THESE EXISTING AUTHORITIES MAINTAINED IN 2.25 PROVIDE THE SAME PERMISSIONS?

· Delete Option Set

· Add/Update Private Option Set

· Add/Update Public Option Set


· Add Constant

· Delete Constant

I’m not sure what the following new set of Authorities govern – I’ve looked at 
Option Sets (as distinct from Category Option Group Sets), but can’t find any 
concept of ‘Groups’ in Options/Option Sets…  What do these new authorities 
control?
INTRODUCED

· Delete Option Group

· Add/Update Private Option Group

· Add/Update Public Option Group

· Delete Option Group Set

· Add/Update Private Option Group Set

· Add/Update Public Option Group Set

The following appear to have been RETIRED prior to the 2.25 release – could you 
confirm that these Authorities have indeed been retired (rather than just 
missed off the drop-down of Authorities in the ‘Create Role’ screen)?  If they 
have been retired, which Authority now manages these permissions?
RETIRED?  (AND REPLACED BY?)

· Add Relationship Type – now covered by ???

· Delete Relationship Type – now covered by ???


· Scheduling send messages – now covered by ???


· Add/Update Section – now covered by ???

· Delete Section – now covered by ???


· Add/Update Tracked Entity – now covered by ???

· Delete Tracked Entity – now covered by ???


· Manage Tracked Entities – now covered by ???

· Update Tracked Entities – now covered by ???


· Delete Tracked Entity Attribute – now covered by ???

· Add/Update Private Tracked Entity Attribute – now covered by ???

· Add/Update Public Tracked Entity Attribute – now covered by ???


· Manage Tracked Entity Instance Reminders


· M_dhis-web-menu-management


We’d be very grateful for any advice or feedback you can provide on the 
questions above, as it would be a huge help in adjusting our own Roles to 
ensure permissions work smoothly during our 2.25 upgrade.

(Once the dust has settled on our 2.25 upgrade, I’d also be very happy to re-do 
this exercise for 2.26, and share it with this Dev list.)

Many thanks,

Sam.


Samuel Johnson - Consultant
—
Qebo Ltd
288a Gloucester Rd, Bristol BS7 8RP
Phone: +44 7734 960 923
___
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-devs] Response differences between /api/metadata and /api/23/metadata

[Lorill Crees]

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 doesn't end up reducing the amount of data that we
need to pass around. Basically, the only time we need to have the
displayName included in the response is if it is associated with an Error
that we need to pass back to the user. With the three options "ERRORS",
"FULL", and "DEBUG", we can only get the displayName with the option
"DEBUG", which also returns a separate object report for every object we
posted, regardless of whether or not it was an error.

Is it possible to augment this functionality with a fourth option, which is
"ERRORS" only, but with the displayName included? We don't want to have the
"FULL" functionality that is included in "DEBUG" as the point of us using
this functionality was to reduce the amount of data being passed around in
order to get at the displayName property of an error. In versions prior to
2.23, we got this information returned by default.

Please let me know what you think, and if a fourth option could be added.
It would be basically "ERRORS_DEBUG".

Thanks,

Lorill


On Sun, Oct 23, 2016 at 7:40 PM, Morten Olav Hansen 
wrote:

>
> On Tue, Oct 18, 2016 at 11:51 PM, Lorill Crees  wrote:
>

>1. The /api/23/metadata response with "errorReports" within
>"objectReports" appears to have replaced the /api/metadata
>"importConflicts". In /api/metadata, the "importConflicts" "object" 
> field
>contains the actual name of the object that has the error (eg: the 
> Program
>short name in our case). However, in /api/23/metadata there is only the
>index which makes it more work to debug. Is it possible to also 
> include the
>name of the object in the error report like the prior API version does?
>
> Hm, right. I understand that it's useful, but that can easily add up
 to a lot of data returned. Maybe we should add some kind of "debug" mode
 where more output is provided.

>>>
>>> Although I understand that this might add more data to the payload, it
>>> would decrease the amount of data that we need to pass around in our app,
>>> and also potentially decrease the number of API calls we need to do. Not
>>> having this information in the response now means we need to pass around
>>> our original post data (which can be quite large, and which we aren't
>>> currently doing) and do a lookup by ID to send any kind of useful
>>> information back to the user. Additionally, we may have even posted these
>>> objects by ID only, which means we will now need to do another API call to
>>> look up the object to get useful information to send back to the user. Keep
>>> in mind that in our app, the user doesn't actually even have a knowledge of
>>> IDs - we are doing those lookups for them by name or code.
>>> Would it be possible to add a flag to the api call where we can request
>>> the name or shortname or code to be returned in addition to just the ID?
>>> Perhaps similar to the metadata field filter?  Where we could say supply
>>> importConflictsFields=:identifiable?
>>>
>>
>> Yes, let me see what I can do for 225 at least (I might be able to
>> backport to 224 if it doesn't disrupt things too much)
>>
>> https://blueprints.launchpad.net/dhis2/+spec/importer-parame
>> ter-to-adjust-importreport-output
>>
>
> Thanks Morten, that's great!
>

>> I see this blueprint was completed in 2.25 - great! Was this backported
>> to 2.24? Is there documentation for this?
>>
>
> Yes, this is also in 224, docs are here:
>
> https://dhis2.github.io/dhis2-docs/master/en/developer/html/
> webapi_metadata_import.html
>
> --
> Morten Olav Hansen
> Senior Engineer, DHIS 2
> University of Oslo
> http://www.dhis2.org
>



-- 
Lorill Crees
Project Leader / Senior Developer
2Paths Solutions Ltd. 

lcr...@2paths.com
skype: lorill2paths
(604) 689-4123 x 15
___
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-devs] [Dhis2-users] Feature roadmap for the next releases

[Lars Helge Øverland]

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" features.

You can find links to those filters here, which should give you a decent
overview. 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 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 Technologies
> Hyderabad
>
> --Stay Hungry Stay Foolish!!
>
> ___
> Mailing list: https://launchpad.net/~dhis2-users
> Post to : dhis2-us...@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
l...@dhis2.org
http://www.dhis2.org 
___
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help   : https://help.launchpad.net/ListHelp

[Dhis2-devs] Betr: Re: [Dhis2-users] release cycle: from 4 to 3 releases per year

[Gijsbert OOMS]

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 have little impact on the user-side, each upgrade needs to be 
followed by a training - at least for administrators. Sometimes that's a 
big investment for little functionality.


GIJSBERT OOMS
EXPERT D4D - Digitalisation for Development
BELGIAN DEVELOPMENT AGENCY
RUE HAUTE 147
1000 BRUSSELS
T +32 (0)2 505 18 44
F +32 (0)2 502 98 62
M +32 (0)477 300 770
WWW.BTCCTB.ORG
Save paper! Think before you print



Van:Bob Jolliffe 
Aan:Lars Helge Øverland 
Cc: DHIS 2 Users list , DHIS 2 
Developers list 
Datum:  03/02/2017 12:56
Onderwerp:  Re: [Dhis2-users] [Dhis2-devs] release cycle: from 4 to 3 
releases per year
Verzonden door: "Dhis2-users" 




Lars, has there been any recent discussion over adopting an ubuntu-style 
approach of two types of release?

I think a lot of people running large national setups with 1000's of users 
would be happy to see a long-term-service release maybe once a year with 
at least guaranteed security related backports for maybe two years.  Then 
maybe two more bleeding edge releases in the year for those who really 
need the latest functionality and have the agility to upgrade frequently.

The numbers above can be different, but I think the idea of two types of 
release might have some merit.   I wonder what would be the main arguments 
for and against.  We want to continue to release-often-release-early to 
maintain momentum.  But also provide some stability.  These aims tend to 
work against each other :-)  Anyway I'd be interested to hear what people 
think.

On 3 February 2017 at 09:40, Lars Helge Øverland  wrote:
Hi all,

we would like to let you know that the release cycle for DHIS 2 will be be 
shifting from 4 to 3 yearly releases. The upcoming releases look like 
this:

2.27: June 1, 2017
2.28: October 1, 2017
2.29: February 1, 2018


A few observations led to this change:

- The machinery around DHIS 2 of documentation, academy materials, release 
notes, web pages and so on is getting larger and the overhead of updating 
it for each release is becoming significant.

- Implementing organizations seem to be lagging a few releases behind the 
latest on average in terms of testing and roll-out. This leads to a large 
demand for back-porting of fixes and even features, consuming a lot of 
developer time.


So by reducing the number of releases by one we hope to reduce the 
overhead and free more time for new development. We promise to remain 
agile and user-driven in spite of this change.


best regards,

Lars






-- 
Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
l...@dhis2.org
http://www.dhis2.org


___
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-us...@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-devs] Exporting/importing User meta-data

[Morten Olav Hansen]

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 - 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 (2.24). When imported into a slightly different
>> instance where 95% of users where the same, EVERY SINGLE user were ignored.
>>
>> Case 2: Selected Export Meta-date with sharing -> Users (only that
>> ticked) -> JSON format (2.25). When imported into the same instance, all
>> where flagged as "updated" and none ignored.
>>
>> So there might be a bug in 2.24, then...
>>
>> Regards
>> Calle
>>
>> On 6 February 2017 at 11:01, Morten Olav Hansen  wrote:
>>
>>> 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, and
>>> not importable as hashes
>>>
>>> --
>>> Morten Olav Hansen
>>> Senior Engineer, DHIS 2
>>> University of Oslo
>>> http://www.dhis2.org
>>>
>>> On Mon, Feb 6, 2017 at 3:58 PM, Calle Hedberg 
>>> wrote:
>>>
 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
 Calle

 On 6 February 2017 at 10:42, Calle Hedberg 
 wrote:

> 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 Olav Hansen 
> wrote:
>
>> Hi Calle
>>
>> Would you mind filing a bug in Jira? easier to track it that way
>>
>> --
>> Morten Olav Hansen
>> Senior Engineer, DHIS 2
>> University of Oslo
>> http://www.dhis2.org
>>
>> On Mon, Feb 6, 2017 at 6:53 AM, Calle Hedberg <
>> calle.hedb...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> I tried to export "Users" meta-data in 2.24 earlier this evening,
>>> and then import it into another slightly different version of the same
>>> instance (when logged in as superuser).
>>>
>>> Every single user was ignored during import, and every single one
>>> had an import summary error message like the one below.
>>>
>>> Anybody able to figure out what's blocking the import in this case?
>>> I do see the ""teiSearchOrganisationUnits":"[]" } is not allowed to
>>> grant users access to user role" sections which looks like some kind of
>>> error, but I don't know what that section actually means.
>>>
>>> (I later tried to export and import "Users" meta-data in the same
>>> 2.25 instance - that worked without a hitch).
>>>
>>> Regards
>>> Calle
>>>
>>> Validation Violations: [ErrorReport{message=User {"id":"0",
>>> "uid":"V0643n3eCBk", "code":"null", "created":"Tue May 03 15:44:05 CAT
>>> 2016", "lastUpdated":"Tue May 03 15:44:05 CAT 2016", "surname":"User",
>>> "firstName":"Demo", "email":"null", "phoneNumber":"null",
>>> "jobTitle":"null", "introduction":"null", "gender":"null",
>>> "birthday":"null", "nationality":"null", "employer":"null",
>>> "education":"null", "interests":"null", "languages":"null",
>>> "lastCheckedInterpretations":"null", 
>>> "userCredentials":"{"username":"Demo_User",
>>> "openId":"null", "password":"$2a$10$CNhU7EJFD5X
>>> 53qDd/F6DyuyVH99JUoWEX6vLFUWC7k4rL7SUzb.kG",
>>> "passwordLastUpdated":"Tue May 03 15:44:04 CAT 2016",
>>> "userAuthorityGroups":"[{"class":"class
>>> org.hisp.dhis.user.UserAuthorityGroup", "id":"0",
>>> "uid":"aWAMSmyKe4b", "code":"null", "name":"Data capturer - Event",
>>> "created":"Thu Jun 25 09:06:05 CAT 2015", "lastUpdated":"Wed Dec 21
>>> 09:20:24 CAT 2016" }, {"class":"class 
>>> org.hisp.dhis.user.UserAuthorityGroup",
>>> "id":"0", "uid":"tnNVBu5cxxZ", "code":"null", "name":"Dashboard",
>>> "created":"Thu Jul 23 17:18:16 CAT 2015", "lastUpdated":"Mon Jun 20
>>> 08:59:15 CAT 2016" }]", 

Re: [Dhis2-devs] user role problem

[rin.channara]

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 problem

>Hi Channara,
>
>Maybe have been hit by the bug described here it seems, but this should not be 
>happening on V2.26
>
>
>https://lists.launchpad.net/dhis2-users/msg12117.html
>
>
>You are certain you are on Version 2.26?
>
>
>Regards,
>
>Jason
>
>
>
>
>
>
>On Mon, Feb 6, 2017 at 4:50 PM, channara rin  wrote:
>
>Dear all,
>
>when i create new user role, i didn't see any program to select. and i saw the 
>error. if i view user role "Supper user", i can see program to select.
>
>
>
>
>DHIS2 V2.26
>
>
>thank you
>
>channara
>
>
>___
>Mailing list: https://launchpad.net/~dhis2-devs
>Post to     : dhis2-devs@lists.launchpad.net
>Unsubscribe : https://launchpad.net/~dhis2-devs
>More help   : https://help.launchpad.net/ListHelp
>
>
>
>
>-- 
>
>Jason P. Pickering
>email: jason.p.picker...@gmail.com
>tel:+46764147049
>
___
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-devs] Org Units visible in API but not in UX

[Martin Van Aken]

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 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 the API but got the "parent" org unit element wrong or simply
> omitted it. When an org unit has a null/missing parent, it effectively
> becomes a root org unit. Now since your user is assigned the original root,
> you cannot see those other root org units.
>
> The solution is to move the "fake" root org units to their appropriate
> place in the hierarchy by modifying the org unit parent element.
>
> Also, if you log in with a user with the ALL authority and go to the user
> app -> create new user, you should be able to see those extra root org
> units.
>
> regards,
>
> Lars
>
>
>
>
>
>
>
> On Mon, Feb 6, 2017 at 2:21 PM, Martin Van Aken 
> wrote:
>
>> 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 good, so I'm
>> wondering if there is any sort of filtering by default on the UI and if so
>> which one?
>>
>> At this time, this means we can't locate the "main/country" org unit
>> through the API (we expect to find only one at the root level, which is not
>> the case).
>>
>> Any leads?
>>
>> Thanks,
>>
>> Martin
>>
>> --
>> *Martin Van Aken - **Freelance Enthusiast Developer*
>>
>> Mobile : +32 486 899 652
>>
>> Follow me on Twitter : @martinvanaken 
>> Call me on Skype : vanakenm
>> Hang out with me : mar...@joyouscoding.com
>> Contact me on LinkedIn : http://www.linkedin.com/in/martinvanaken
>> Company website : www.joyouscoding.com
>>
>> ___
>> Mailing list: https://launchpad.net/~dhis2-devs
>> Post to : dhis2-devs@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~dhis2-devs
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> --
> Lars Helge Øverland
> Lead developer, DHIS 2
> University of Oslo
> Skype: larshelgeoverland
> l...@dhis2.org
> http://www.dhis2.org 
>
>


-- 
*Martin Van Aken - **Freelance Enthusiast Developer*

Mobile : +32 486 899 652

Follow me on Twitter : @martinvanaken 
Call me on Skype : vanakenm
Hang out with me : mar...@joyouscoding.com
Contact me on LinkedIn : http://www.linkedin.com/in/martinvanaken
Company website : www.joyouscoding.com
___
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-devs] Org Units visible in API but not in UX

[Lars Helge Øverland]

 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 the API but got the "parent" org unit element wrong or simply
omitted it. When an org unit has a null/missing parent, it effectively
becomes a root org unit. Now since your user is assigned the original root,
you cannot see those other root org units.

The solution is to move the "fake" root org units to their appropriate
place in the hierarchy by modifying the org unit parent element.

Also, if you log in with a user with the ALL authority and go to the user
app -> create new user, you should be able to see those extra root org
units.

regards,

Lars







On Mon, Feb 6, 2017 at 2:21 PM, Martin Van Aken 
wrote:

> 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 good, so I'm
> wondering if there is any sort of filtering by default on the UI and if so
> which one?
>
> At this time, this means we can't locate the "main/country" org unit
> through the API (we expect to find only one at the root level, which is not
> the case).
>
> Any leads?
>
> Thanks,
>
> Martin
>
> --
> *Martin Van Aken - **Freelance Enthusiast Developer*
>
> Mobile : +32 486 899 652
>
> Follow me on Twitter : @martinvanaken 
> Call me on Skype : vanakenm
> Hang out with me : mar...@joyouscoding.com
> Contact me on LinkedIn : http://www.linkedin.com/in/martinvanaken
> Company website : www.joyouscoding.com
>
> ___
> Mailing list: https://launchpad.net/~dhis2-devs
> Post to : dhis2-devs@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-devs
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
l...@dhis2.org
http://www.dhis2.org 
___
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help   : https://help.launchpad.net/ListHelp

[Dhis2-devs] Org Units visible in API but not in UX

[Martin Van Aken]

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 good, so I'm
wondering if there is any sort of filtering by default on the UI and if so
which one?

At this time, this means we can't locate the "main/country" org unit
through the API (we expect to find only one at the root level, which is not
the case).

Any leads?

Thanks,

Martin

-- 
*Martin Van Aken - **Freelance Enthusiast Developer*

Mobile : +32 486 899 652

Follow me on Twitter : @martinvanaken 
Call me on Skype : vanakenm
Hang out with me : mar...@joyouscoding.com
Contact me on LinkedIn : http://www.linkedin.com/in/martinvanaken
Company website : www.joyouscoding.com
___
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-devs] [Dhis2-users] release cycle: from 4 to 3 releases per year

[Marta Vila]

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 two types of release?
>
> I think a lot of people running large national setups with 1000's of users
> would be happy to see a long-term-service release maybe once a year with at
> least guaranteed security related backports for maybe two years.  Then
> maybe two more bleeding edge releases in the year for those who really need
> the latest functionality and have the agility to upgrade frequently.
>
> The numbers above can be different, but I think the idea of two types of
> release might have some merit.   I wonder what would be the main arguments
> for and against.  We want to continue to release-often-release-early to
> maintain momentum.  But also provide some stability.  These aims tend to
> work against each other :-)  Anyway I'd be interested to hear what people
> think.
>
> On 3 February 2017 at 09:40, Lars Helge Øverland  wrote:
>
>> Hi all,
>>
>> we would like to let you know that the release cycle for DHIS 2 will be
>> be shifting from 4 to 3 yearly releases. The upcoming releases look like
>> this:
>>
>> 2.27: June 1, 2017
>> 2.28: October 1, 2017
>> 2.29: February 1, 2018
>>
>>
>> A few observations led to this change:
>>
>> - The machinery around DHIS 2 of documentation, academy materials,
>> release notes, web pages and so on is getting larger and the overhead of
>> updating it for each release is becoming significant.
>>
>> - Implementing organizations seem to be lagging a few releases behind the
>> latest on average in terms of testing and roll-out. This leads to a large
>> demand for back-porting of fixes and even features, consuming a lot of
>> developer time.
>>
>>
>> So by reducing the number of releases by one we hope to reduce the
>> overhead and free more time for new development. We promise to remain agile
>> and user-driven in spite of this change.
>>
>>
>> best regards,
>>
>> Lars
>>
>>
>>
>>
>>
>>
>> --
>> Lars Helge Øverland
>> Lead developer, DHIS 2
>> University of Oslo
>> Skype: larshelgeoverland
>> l...@dhis2.org
>> http://www.dhis2.org 
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~dhis2-devs
>> Post to : dhis2-devs@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~dhis2-devs
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
> ___
> Mailing list: https://launchpad.net/~dhis2-users
> Post to : dhis2-us...@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-devs] Exporting/importing User meta-data

[Calle Hedberg]

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 (2.24). When imported into a slightly different instance
> where 95% of users where the same, EVERY SINGLE user were ignored.
>
> Case 2: Selected Export Meta-date with sharing -> Users (only that ticked)
> -> JSON format (2.25). When imported into the same instance, all where
> flagged as "updated" and none ignored.
>
> So there might be a bug in 2.24, then...
>
> Regards
> Calle
>
> On 6 February 2017 at 11:01, Morten Olav Hansen  wrote:
>
>> 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, and
>> not importable as hashes
>>
>> --
>> Morten Olav Hansen
>> Senior Engineer, DHIS 2
>> University of Oslo
>> http://www.dhis2.org
>>
>> On Mon, Feb 6, 2017 at 3:58 PM, Calle Hedberg 
>> wrote:
>>
>>> 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
>>> Calle
>>>
>>> On 6 February 2017 at 10:42, Calle Hedberg 
>>> wrote:
>>>
 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 Olav Hansen 
 wrote:

> Hi Calle
>
> Would you mind filing a bug in Jira? easier to track it that way
>
> --
> Morten Olav Hansen
> Senior Engineer, DHIS 2
> University of Oslo
> http://www.dhis2.org
>
> On Mon, Feb 6, 2017 at 6:53 AM, Calle Hedberg  > wrote:
>
>> Hi,
>>
>> I tried to export "Users" meta-data in 2.24 earlier this evening, and
>> then import it into another slightly different version of the same 
>> instance
>> (when logged in as superuser).
>>
>> Every single user was ignored during import, and every single one had
>> an import summary error message like the one below.
>>
>> Anybody able to figure out what's blocking the import in this case? I
>> do see the ""teiSearchOrganisationUnits":"[]" } is not allowed to
>> grant users access to user role" sections which looks like some kind of
>> error, but I don't know what that section actually means.
>>
>> (I later tried to export and import "Users" meta-data in the same
>> 2.25 instance - that worked without a hitch).
>>
>> Regards
>> Calle
>>
>> Validation Violations: [ErrorReport{message=User {"id":"0",
>> "uid":"V0643n3eCBk", "code":"null", "created":"Tue May 03 15:44:05 CAT
>> 2016", "lastUpdated":"Tue May 03 15:44:05 CAT 2016", "surname":"User",
>> "firstName":"Demo", "email":"null", "phoneNumber":"null",
>> "jobTitle":"null", "introduction":"null", "gender":"null",
>> "birthday":"null", "nationality":"null", "employer":"null",
>> "education":"null", "interests":"null", "languages":"null",
>> "lastCheckedInterpretations":"null", 
>> "userCredentials":"{"username":"Demo_User",
>> "openId":"null", "password":"$2a$10$CNhU7EJFD5X
>> 53qDd/F6DyuyVH99JUoWEX6vLFUWC7k4rL7SUzb.kG",
>> "passwordLastUpdated":"Tue May 03 15:44:04 CAT 2016",
>> "userAuthorityGroups":"[{"class":"class
>> org.hisp.dhis.user.UserAuthorityGroup", "id":"0",
>> "uid":"aWAMSmyKe4b", "code":"null", "name":"Data capturer - Event",
>> "created":"Thu Jun 25 09:06:05 CAT 2015", "lastUpdated":"Wed Dec 21
>> 09:20:24 CAT 2016" }, {"class":"class 
>> org.hisp.dhis.user.UserAuthorityGroup",
>> "id":"0", "uid":"tnNVBu5cxxZ", "code":"null", "name":"Dashboard",
>> "created":"Thu Jul 23 17:18:16 CAT 2015", "lastUpdated":"Mon Jun 20
>> 08:59:15 CAT 2016" }]", "lastLogin":"Tue May 03 15:44:04 CAT 2016",
>> "restoreToken":"null", "restoreCode":"null", "restoreExpiry":"null",
>> "selfRegistered":"false", "disabled":"false" }", "groups":"[]",
>> "organisationUnits":"[{"class":"class 
>> org.hisp.dhis.organisationunit.OrganisationUnit",
>> "id":"0", "uid":"kWi0HuwZ68H", "code":"null", "name":"Ministry of Health
>> and Social Services", 

Re: [Dhis2-devs] Arranging data entry in data capture app

[Araz Abishov]

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, DHIS 2
University of Oslo
https://www.dhis2.org/

On February 6, 2017 at 9:05:37 AM, Jason Pickering (
jason.p.picker...@gmail.com) wrote:

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.

Regards,
Jason


On Mon, Feb 6, 2017 at 2:30 PM, Blake Hansen  wrote:

> 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.
> Many thanks,
> Blake
>
>
> --
>
>
>
>
> *Blake Hansen*
> Projects Implementation Manager, BAO Systems
> +1 202-536-1541 | bhan...@baosystems.com | http://www.baosystems.com |
> Skype: blake.a.hansen |  2900 K Street, Suite 406, Washington D.C. 20007
>
> On 6 Feb 2017, at 14:51, Jason Pickering 
> wrote:
>
> Hi Blake,
>
> Just use a section form and order them as you like. This of course will
> require that you can  use a section form.
>
> Otherwise, you would need to implement a custom form and order then there.
>
> Regards,
> Jason
>
>
> On Mon, Feb 6, 2017 at 1:24 PM, Blake Hansen 
> wrote:
>
>> Dear Devs,
>>
>> I am trying to rearrange the order of data elements and category options
>> as they appear in the tabularised form of the data capture app - aggregate
>> form.
>> I expected them to load based on alphabetical order of the data element
>> name, and as such gave them numbering at the beginning of the name ‘005,
>> 010, etc…’ However the order the data elements in the app adopt in the
>> aggregate form seems not to respect this. How do I arrange the order of the
>> data elements in the form, please?
>>
>> With thanks,
>> Blake
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~dhis2-devs
>> Post to : dhis2-devs@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~dhis2-devs
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> --
> Jason P. Pickering
> email: jason.p.picker...@gmail.com
> tel:+46764147049 <+46764147049>
>
>
>


--
Jason P. Pickering
email: jason.p.picker...@gmail.com
tel:+46764147049
___
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp


0468193D-F2F1-4D86-A884-BB427B14A393
Description: Binary data
___
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-devs] Exporting/importing User meta-data

[Calle Hedberg]

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 2: Selected Export Meta-date with sharing -> Users (only that ticked)
-> JSON format (2.25). When imported into the same instance, all where
flagged as "updated" and none ignored.

So there might be a bug in 2.24, then...

Regards
Calle

On 6 February 2017 at 11:01, Morten Olav Hansen  wrote:

> 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, and
> not importable as hashes
>
> --
> Morten Olav Hansen
> Senior Engineer, DHIS 2
> University of Oslo
> http://www.dhis2.org
>
> On Mon, Feb 6, 2017 at 3:58 PM, Calle Hedberg 
> wrote:
>
>> 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
>> Calle
>>
>> On 6 February 2017 at 10:42, Calle Hedberg 
>> wrote:
>>
>>> 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 Olav Hansen 
>>> wrote:
>>>
 Hi Calle

 Would you mind filing a bug in Jira? easier to track it that way

 --
 Morten Olav Hansen
 Senior Engineer, DHIS 2
 University of Oslo
 http://www.dhis2.org

 On Mon, Feb 6, 2017 at 6:53 AM, Calle Hedberg 
 wrote:

> Hi,
>
> I tried to export "Users" meta-data in 2.24 earlier this evening, and
> then import it into another slightly different version of the same 
> instance
> (when logged in as superuser).
>
> Every single user was ignored during import, and every single one had
> an import summary error message like the one below.
>
> Anybody able to figure out what's blocking the import in this case? I
> do see the ""teiSearchOrganisationUnits":"[]" } is not allowed to
> grant users access to user role" sections which looks like some kind of
> error, but I don't know what that section actually means.
>
> (I later tried to export and import "Users" meta-data in the same 2.25
> instance - that worked without a hitch).
>
> Regards
> Calle
>
> Validation Violations: [ErrorReport{message=User {"id":"0",
> "uid":"V0643n3eCBk", "code":"null", "created":"Tue May 03 15:44:05 CAT
> 2016", "lastUpdated":"Tue May 03 15:44:05 CAT 2016", "surname":"User",
> "firstName":"Demo", "email":"null", "phoneNumber":"null",
> "jobTitle":"null", "introduction":"null", "gender":"null",
> "birthday":"null", "nationality":"null", "employer":"null",
> "education":"null", "interests":"null", "languages":"null",
> "lastCheckedInterpretations":"null", 
> "userCredentials":"{"username":"Demo_User",
> "openId":"null", "password":"$2a$10$CNhU7EJFD5X
> 53qDd/F6DyuyVH99JUoWEX6vLFUWC7k4rL7SUzb.kG",
> "passwordLastUpdated":"Tue May 03 15:44:04 CAT 2016",
> "userAuthorityGroups":"[{"class":"class 
> org.hisp.dhis.user.UserAuthorityGroup",
> "id":"0", "uid":"aWAMSmyKe4b", "code":"null", "name":"Data capturer -
> Event", "created":"Thu Jun 25 09:06:05 CAT 2015", "lastUpdated":"Wed Dec 
> 21
> 09:20:24 CAT 2016" }, {"class":"class 
> org.hisp.dhis.user.UserAuthorityGroup",
> "id":"0", "uid":"tnNVBu5cxxZ", "code":"null", "name":"Dashboard",
> "created":"Thu Jul 23 17:18:16 CAT 2015", "lastUpdated":"Mon Jun 20
> 08:59:15 CAT 2016" }]", "lastLogin":"Tue May 03 15:44:04 CAT 2016",
> "restoreToken":"null", "restoreCode":"null", "restoreExpiry":"null",
> "selfRegistered":"false", "disabled":"false" }", "groups":"[]",
> "organisationUnits":"[{"class":"class 
> org.hisp.dhis.organisationunit.OrganisationUnit",
> "id":"0", "uid":"kWi0HuwZ68H", "code":"null", "name":"Ministry of Health
> and Social Services", "created":"Mon Aug 10 08:57:03 CAT 2015",
> "lastUpdated":"Thu Jun 16 11:53:40 CAT 2016" }]",
> "dataViewOrganisationUnits":"[{"class":"class
> org.hisp.dhis.organisationunit.OrganisationUnit", "id":"0",
> "uid":"kWi0HuwZ68H", "code":"null", 

Re: [Dhis2-devs] Exporting/importing User meta-data

[Morten Olav Hansen]

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, and
not importable as hashes

-- 
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo
http://www.dhis2.org

On Mon, Feb 6, 2017 at 3:58 PM, Calle Hedberg 
wrote:

> 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
> Calle
>
> On 6 February 2017 at 10:42, Calle Hedberg 
> wrote:
>
>> 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 Olav Hansen  wrote:
>>
>>> Hi Calle
>>>
>>> Would you mind filing a bug in Jira? easier to track it that way
>>>
>>> --
>>> Morten Olav Hansen
>>> Senior Engineer, DHIS 2
>>> University of Oslo
>>> http://www.dhis2.org
>>>
>>> On Mon, Feb 6, 2017 at 6:53 AM, Calle Hedberg 
>>> wrote:
>>>
 Hi,

 I tried to export "Users" meta-data in 2.24 earlier this evening, and
 then import it into another slightly different version of the same instance
 (when logged in as superuser).

 Every single user was ignored during import, and every single one had
 an import summary error message like the one below.

 Anybody able to figure out what's blocking the import in this case? I
 do see the ""teiSearchOrganisationUnits":"[]" } is not allowed to
 grant users access to user role" sections which looks like some kind of
 error, but I don't know what that section actually means.

 (I later tried to export and import "Users" meta-data in the same 2.25
 instance - that worked without a hitch).

 Regards
 Calle

 Validation Violations: [ErrorReport{message=User {"id":"0",
 "uid":"V0643n3eCBk", "code":"null", "created":"Tue May 03 15:44:05 CAT
 2016", "lastUpdated":"Tue May 03 15:44:05 CAT 2016", "surname":"User",
 "firstName":"Demo", "email":"null", "phoneNumber":"null",
 "jobTitle":"null", "introduction":"null", "gender":"null",
 "birthday":"null", "nationality":"null", "employer":"null",
 "education":"null", "interests":"null", "languages":"null",
 "lastCheckedInterpretations":"null", 
 "userCredentials":"{"username":"Demo_User",
 "openId":"null", "password":"$2a$10$CNhU7EJFD5X
 53qDd/F6DyuyVH99JUoWEX6vLFUWC7k4rL7SUzb.kG",
 "passwordLastUpdated":"Tue May 03 15:44:04 CAT 2016",
 "userAuthorityGroups":"[{"class":"class 
 org.hisp.dhis.user.UserAuthorityGroup",
 "id":"0", "uid":"aWAMSmyKe4b", "code":"null", "name":"Data capturer -
 Event", "created":"Thu Jun 25 09:06:05 CAT 2015", "lastUpdated":"Wed Dec 21
 09:20:24 CAT 2016" }, {"class":"class 
 org.hisp.dhis.user.UserAuthorityGroup",
 "id":"0", "uid":"tnNVBu5cxxZ", "code":"null", "name":"Dashboard",
 "created":"Thu Jul 23 17:18:16 CAT 2015", "lastUpdated":"Mon Jun 20
 08:59:15 CAT 2016" }]", "lastLogin":"Tue May 03 15:44:04 CAT 2016",
 "restoreToken":"null", "restoreCode":"null", "restoreExpiry":"null",
 "selfRegistered":"false", "disabled":"false" }", "groups":"[]",
 "organisationUnits":"[{"class":"class 
 org.hisp.dhis.organisationunit.OrganisationUnit",
 "id":"0", "uid":"kWi0HuwZ68H", "code":"null", "name":"Ministry of Health
 and Social Services", "created":"Mon Aug 10 08:57:03 CAT 2015",
 "lastUpdated":"Thu Jun 16 11:53:40 CAT 2016" }]",
 "dataViewOrganisationUnits":"[{"class":"class
 org.hisp.dhis.organisationunit.OrganisationUnit", "id":"0",
 "uid":"kWi0HuwZ68H", "code":"null", "name":"Ministry of Health and Social
 Services", "created":"Mon Aug 10 08:57:03 CAT 2015", "lastUpdated":"Thu Jun
 16 11:53:40 CAT 2016" }]" "teiSearchOrganisationUnits":"[]" } is not
 allowed to grant users access to user role {"class":"class
 org.hisp.dhis.user.UserAuthorityGroup", "id":"60273",
 "uid":"ckj7ljweNzk", "code":"null", "name":"User Managed Groups",
 "created":"2015-06-24 17:05:03.418", "lastUpdated":"2016-06-15
 15:45:57.802" }., errorCode=E3003, mainKlass=class
 org.hisp.dhis.user.UserAuthorityGroup, errorKlass=null, value=null},
 ErrorReport{message=User {"id":"0", "uid":"V0643n3eCBk", "code":"null",
 "created":"Tue May 03 15:44:05 CAT 2016", "lastUpdated":"Tue May 03
 15:44:05 CAT 2016", 

Re: [Dhis2-devs] Exporting/importing User meta-data

[Calle Hedberg]

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
Calle

On 6 February 2017 at 10:42, Calle Hedberg  wrote:

> 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 Olav Hansen  wrote:
>
>> Hi Calle
>>
>> Would you mind filing a bug in Jira? easier to track it that way
>>
>> --
>> Morten Olav Hansen
>> Senior Engineer, DHIS 2
>> University of Oslo
>> http://www.dhis2.org
>>
>> On Mon, Feb 6, 2017 at 6:53 AM, Calle Hedberg 
>> wrote:
>>
>>> Hi,
>>>
>>> I tried to export "Users" meta-data in 2.24 earlier this evening, and
>>> then import it into another slightly different version of the same instance
>>> (when logged in as superuser).
>>>
>>> Every single user was ignored during import, and every single one had an
>>> import summary error message like the one below.
>>>
>>> Anybody able to figure out what's blocking the import in this case? I do
>>> see the ""teiSearchOrganisationUnits":"[]" } is not allowed to grant
>>> users access to user role" sections which looks like some kind of error,
>>> but I don't know what that section actually means.
>>>
>>> (I later tried to export and import "Users" meta-data in the same 2.25
>>> instance - that worked without a hitch).
>>>
>>> Regards
>>> Calle
>>>
>>> Validation Violations: [ErrorReport{message=User {"id":"0",
>>> "uid":"V0643n3eCBk", "code":"null", "created":"Tue May 03 15:44:05 CAT
>>> 2016", "lastUpdated":"Tue May 03 15:44:05 CAT 2016", "surname":"User",
>>> "firstName":"Demo", "email":"null", "phoneNumber":"null",
>>> "jobTitle":"null", "introduction":"null", "gender":"null",
>>> "birthday":"null", "nationality":"null", "employer":"null",
>>> "education":"null", "interests":"null", "languages":"null",
>>> "lastCheckedInterpretations":"null", 
>>> "userCredentials":"{"username":"Demo_User",
>>> "openId":"null", "password":"$2a$10$CNhU7EJFD5X
>>> 53qDd/F6DyuyVH99JUoWEX6vLFUWC7k4rL7SUzb.kG", "passwordLastUpdated":"Tue
>>> May 03 15:44:04 CAT 2016", "userAuthorityGroups":"[{"class":"class
>>> org.hisp.dhis.user.UserAuthorityGroup", "id":"0", "uid":"aWAMSmyKe4b",
>>> "code":"null", "name":"Data capturer - Event", "created":"Thu Jun 25
>>> 09:06:05 CAT 2015", "lastUpdated":"Wed Dec 21 09:20:24 CAT 2016" },
>>> {"class":"class org.hisp.dhis.user.UserAuthorityGroup", "id":"0",
>>> "uid":"tnNVBu5cxxZ", "code":"null", "name":"Dashboard", "created":"Thu Jul
>>> 23 17:18:16 CAT 2015", "lastUpdated":"Mon Jun 20 08:59:15 CAT 2016" }]",
>>> "lastLogin":"Tue May 03 15:44:04 CAT 2016", "restoreToken":"null",
>>> "restoreCode":"null", "restoreExpiry":"null", "selfRegistered":"false",
>>> "disabled":"false" }", "groups":"[]", "organisationUnits":"[{"class":"class
>>> org.hisp.dhis.organisationunit.OrganisationUnit", "id":"0",
>>> "uid":"kWi0HuwZ68H", "code":"null", "name":"Ministry of Health and Social
>>> Services", "created":"Mon Aug 10 08:57:03 CAT 2015", "lastUpdated":"Thu Jun
>>> 16 11:53:40 CAT 2016" }]", "dataViewOrganisationUnits":"[{"class":"class
>>> org.hisp.dhis.organisationunit.OrganisationUnit", "id":"0",
>>> "uid":"kWi0HuwZ68H", "code":"null", "name":"Ministry of Health and Social
>>> Services", "created":"Mon Aug 10 08:57:03 CAT 2015", "lastUpdated":"Thu Jun
>>> 16 11:53:40 CAT 2016" }]" "teiSearchOrganisationUnits":"[]" } is not
>>> allowed to grant users access to user role {"class":"class
>>> org.hisp.dhis.user.UserAuthorityGroup", "id":"60273",
>>> "uid":"ckj7ljweNzk", "code":"null", "name":"User Managed Groups",
>>> "created":"2015-06-24 17:05:03.418", "lastUpdated":"2016-06-15
>>> 15:45:57.802" }., errorCode=E3003, mainKlass=class
>>> org.hisp.dhis.user.UserAuthorityGroup, errorKlass=null, value=null},
>>> ErrorReport{message=User {"id":"0", "uid":"V0643n3eCBk", "code":"null",
>>> "created":"Tue May 03 15:44:05 CAT 2016", "lastUpdated":"Tue May 03
>>> 15:44:05 CAT 2016", "surname":"User", "firstName":"Demo", "email":"null",
>>> "phoneNumber":"null", "jobTitle":"null", "introduction":"null",
>>> "gender":"null", "birthday":"null", "nationality":"null",
>>> "employer":"null", "education":"null", "interests":"null",
>>> "languages":"null", "lastCheckedInterpretations":"null",
>>> "userCredentials":"{"username":"Demo_User", "openId":"null",
>>> "password":"$2a$10$CNhU7EJFD5X53qDd/F6DyuyVH99JUoWEX6vLFUWC7k4rL7SUzb.kG",
>>> "passwordLastUpdated":"Tue May 03 15:44:04 CAT 2016",
>>> "userAuthorityGroups":"[{"class":"class 
>>> org.hisp.dhis.user.UserAuthorityGroup",
>>> "id":"0", 

Re: [Dhis2-devs] Exporting/importing User meta-data

[Calle Hedberg]

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 Olav Hansen  wrote:

> Hi Calle
>
> Would you mind filing a bug in Jira? easier to track it that way
>
> --
> Morten Olav Hansen
> Senior Engineer, DHIS 2
> University of Oslo
> http://www.dhis2.org
>
> On Mon, Feb 6, 2017 at 6:53 AM, Calle Hedberg 
> wrote:
>
>> Hi,
>>
>> I tried to export "Users" meta-data in 2.24 earlier this evening, and
>> then import it into another slightly different version of the same instance
>> (when logged in as superuser).
>>
>> Every single user was ignored during import, and every single one had an
>> import summary error message like the one below.
>>
>> Anybody able to figure out what's blocking the import in this case? I do
>> see the ""teiSearchOrganisationUnits":"[]" } is not allowed to grant
>> users access to user role" sections which looks like some kind of error,
>> but I don't know what that section actually means.
>>
>> (I later tried to export and import "Users" meta-data in the same 2.25
>> instance - that worked without a hitch).
>>
>> Regards
>> Calle
>>
>> Validation Violations: [ErrorReport{message=User {"id":"0",
>> "uid":"V0643n3eCBk", "code":"null", "created":"Tue May 03 15:44:05 CAT
>> 2016", "lastUpdated":"Tue May 03 15:44:05 CAT 2016", "surname":"User",
>> "firstName":"Demo", "email":"null", "phoneNumber":"null",
>> "jobTitle":"null", "introduction":"null", "gender":"null",
>> "birthday":"null", "nationality":"null", "employer":"null",
>> "education":"null", "interests":"null", "languages":"null",
>> "lastCheckedInterpretations":"null", 
>> "userCredentials":"{"username":"Demo_User",
>> "openId":"null", "password":"$2a$10$CNhU7EJFD5X
>> 53qDd/F6DyuyVH99JUoWEX6vLFUWC7k4rL7SUzb.kG", "passwordLastUpdated":"Tue
>> May 03 15:44:04 CAT 2016", "userAuthorityGroups":"[{"class":"class
>> org.hisp.dhis.user.UserAuthorityGroup", "id":"0", "uid":"aWAMSmyKe4b",
>> "code":"null", "name":"Data capturer - Event", "created":"Thu Jun 25
>> 09:06:05 CAT 2015", "lastUpdated":"Wed Dec 21 09:20:24 CAT 2016" },
>> {"class":"class org.hisp.dhis.user.UserAuthorityGroup", "id":"0",
>> "uid":"tnNVBu5cxxZ", "code":"null", "name":"Dashboard", "created":"Thu Jul
>> 23 17:18:16 CAT 2015", "lastUpdated":"Mon Jun 20 08:59:15 CAT 2016" }]",
>> "lastLogin":"Tue May 03 15:44:04 CAT 2016", "restoreToken":"null",
>> "restoreCode":"null", "restoreExpiry":"null", "selfRegistered":"false",
>> "disabled":"false" }", "groups":"[]", "organisationUnits":"[{"class":"class
>> org.hisp.dhis.organisationunit.OrganisationUnit", "id":"0",
>> "uid":"kWi0HuwZ68H", "code":"null", "name":"Ministry of Health and Social
>> Services", "created":"Mon Aug 10 08:57:03 CAT 2015", "lastUpdated":"Thu Jun
>> 16 11:53:40 CAT 2016" }]", "dataViewOrganisationUnits":"[{"class":"class
>> org.hisp.dhis.organisationunit.OrganisationUnit", "id":"0",
>> "uid":"kWi0HuwZ68H", "code":"null", "name":"Ministry of Health and Social
>> Services", "created":"Mon Aug 10 08:57:03 CAT 2015", "lastUpdated":"Thu Jun
>> 16 11:53:40 CAT 2016" }]" "teiSearchOrganisationUnits":"[]" } is not
>> allowed to grant users access to user role {"class":"class
>> org.hisp.dhis.user.UserAuthorityGroup", "id":"60273",
>> "uid":"ckj7ljweNzk", "code":"null", "name":"User Managed Groups",
>> "created":"2015-06-24 17:05:03.418", "lastUpdated":"2016-06-15
>> 15:45:57.802" }., errorCode=E3003, mainKlass=class
>> org.hisp.dhis.user.UserAuthorityGroup, errorKlass=null, value=null},
>> ErrorReport{message=User {"id":"0", "uid":"V0643n3eCBk", "code":"null",
>> "created":"Tue May 03 15:44:05 CAT 2016", "lastUpdated":"Tue May 03
>> 15:44:05 CAT 2016", "surname":"User", "firstName":"Demo", "email":"null",
>> "phoneNumber":"null", "jobTitle":"null", "introduction":"null",
>> "gender":"null", "birthday":"null", "nationality":"null",
>> "employer":"null", "education":"null", "interests":"null",
>> "languages":"null", "lastCheckedInterpretations":"null",
>> "userCredentials":"{"username":"Demo_User", "openId":"null",
>> "password":"$2a$10$CNhU7EJFD5X53qDd/F6DyuyVH99JUoWEX6vLFUWC7k4rL7SUzb.kG",
>> "passwordLastUpdated":"Tue May 03 15:44:04 CAT 2016",
>> "userAuthorityGroups":"[{"class":"class 
>> org.hisp.dhis.user.UserAuthorityGroup",
>> "id":"0", "uid":"aWAMSmyKe4b", "code":"null", "name":"Data capturer -
>> Event", "created":"Thu Jun 25 09:06:05 CAT 2015", "lastUpdated":"Wed Dec 21
>> 09:20:24 CAT 2016" }, {"class":"class org.hisp.dhis.user.UserAuthorityGroup",
>> "id":"0", "uid":"tnNVBu5cxxZ", "code":"null", "name":"Dashboard",
>> "created":"Thu Jul 23 17:18:16 CAT 2015", "lastUpdated":"Mon Jun 20
>> 08:59:15 CAT 2016" }]", "lastLogin":"Tue May 03 15:44:04 CAT 2016",
>> "restoreToken":"null", "restoreCode":"null", 

Re: [Dhis2-devs] Arranging data entry in data capture app

[Jason Pickering]

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.

Regards,
Jason


On Mon, Feb 6, 2017 at 2:30 PM, Blake Hansen  wrote:

> 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.
> Many thanks,
> Blake
>
>
> --
>
>
>
>
> *Blake Hansen*
> Projects Implementation Manager, BAO Systems
> +1 202-536-1541 | bhan...@baosystems.com | http://www.baosystems.com |
> Skype: blake.a.hansen |  2900 K Street, Suite 406, Washington D.C. 20007
>
> On 6 Feb 2017, at 14:51, Jason Pickering 
> wrote:
>
> Hi Blake,
>
> Just use a section form and order them as you like. This of course will
> require that you can  use a section form.
>
> Otherwise, you would need to implement a custom form and order then there.
>
> Regards,
> Jason
>
>
> On Mon, Feb 6, 2017 at 1:24 PM, Blake Hansen 
> wrote:
>
>> Dear Devs,
>>
>> I am trying to rearrange the order of data elements and category options
>> as they appear in the tabularised form of the data capture app - aggregate
>> form.
>> I expected them to load based on alphabetical order of the data element
>> name, and as such gave them numbering at the beginning of the name ‘005,
>> 010, etc…’ However the order the data elements in the app adopt in the
>> aggregate form seems not to respect this. How do I arrange the order of the
>> data elements in the form, please?
>>
>> With thanks,
>> Blake
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~dhis2-devs
>> Post to : dhis2-devs@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~dhis2-devs
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> --
> Jason P. Pickering
> email: jason.p.picker...@gmail.com
> tel:+46764147049 <+46764147049>
>
>
>


-- 
Jason P. Pickering
email: jason.p.picker...@gmail.com
tel:+46764147049
___
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-devs] Arranging data entry in data capture app

[Blake Hansen]

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. 
Many thanks,
Blake


-- 




Blake Hansen
Projects Implementation Manager, BAO Systems
+1 202-536-1541 | bhan...@baosystems.com  | 
http://www.baosystems.com  |
Skype: blake.a.hansen |  2900 K Street, Suite 406, Washington D.C. 20007

> On 6 Feb 2017, at 14:51, Jason Pickering  wrote:
> 
> Hi Blake,
> 
> Just use a section form and order them as you like. This of course will 
> require that you can  use a section form. 
> 
> Otherwise, you would need to implement a custom form and order then there. 
> 
> Regards,
> Jason
> 
> 
> On Mon, Feb 6, 2017 at 1:24 PM, Blake Hansen  > wrote:
> Dear Devs,
> 
> I am trying to rearrange the order of data elements and category options as 
> they appear in the tabularised form of the data capture app - aggregate form.
> I expected them to load based on alphabetical order of the data element name, 
> and as such gave them numbering at the beginning of the name ‘005, 010, etc…’ 
> However the order the data elements in the app adopt in the aggregate form 
> seems not to respect this. How do I arrange the order of the data elements in 
> the form, please?
> 
> With thanks,
> Blake
> 
> 
> ___
> Mailing list: https://launchpad.net/~dhis2-devs 
> 
> Post to : dhis2-devs@lists.launchpad.net 
> 
> Unsubscribe : https://launchpad.net/~dhis2-devs 
> 
> More help   : https://help.launchpad.net/ListHelp 
> 
> 
> 
> 
> 
> -- 
> Jason P. Pickering
> email: jason.p.picker...@gmail.com 
> tel:+46764147049

___
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help   : https://help.launchpad.net/ListHelp