Dear Viet,We have encountered this issue and I had reported this and got no
response.
The thing is that for us, the default category option is not used on any of
these data sets that are encountering this issue. Also, we did not have this
issue until we upgraded to the latest build of 2.29 on Friday and right now,
none of our teams can enter any data.
So, what changed between the updates from the previous version to the latest?
Secondly, why is a category option that is not used in any dataset affecting
data entry on that dataset?
Thanks
Warm Regards,
Ifeanyi
Read DrMaestro's Blog
www.ifeanyiokoye.com
On Thursday, September 27, 2018, 8:48:23 AM GMT+1, Viet Nguyen
<[email protected]> wrote:
Hi Alejandro,
That's a bug, the default category option should be shared by default. I have
just added a fix for that issue. It will be included in the latest build by
tomorrow.
Regards,
On Thu, Sep 27, 2018 at 12:32 AM Alejandro <[email protected]> wrote:
Hi,
We have had the same issue when upgrading from 2.28 to 2.30. When trying to
enter data in a Tracker Program with all the capture sharings configured for
the user (Tracked Entity Type, Program, Stages) we got the following message:
{httpStatus: "Conflict", httpStatusCode: 409, status: "ERROR",…}httpStatus:
"Conflict"httpStatusCode: 409message: "An error occurred, please check import
summary."response: {responseType: "ImportSummary", status:
"ERROR",…}description: "[User has no write access to category option:
rHGSHuG4Ts5]"importCount: {imported: 0, updated: 0, ignored: 1, deleted:
0}responseType: "ImportSummary"status: "ERROR"status: "ERROR"
The category option rHGSHuG4Ts5 in our system is the system default one (i.e.
when category option = none):
<categoryOption
id="rHGSHuG4Ts5"><displayName>default</displayName></categoryOption>
And this category option is not displayed in the UI (we cannot give it the
Data->Can view or Data->Can capture options). How can we set those permissions
for the system default category option? Should not this be granted by default?
Thank you in advance!Alejandro
On Tue, Jul 24, 2018 at 8:00 PM Eudson Bambo
<[email protected]> wrote:
Dear Blake,
It worked. Many thanks.
Adolphe and Viet, I saw your emails also - thank you.
Eudson
On 23 Jul 2018, at 8:54 PM, Eudson Bambo <[email protected]>
wrote:
Dear Blake,
Thanks for your response, I will have a look at the documentation and give the
permissions to the users.
Many thanks.Eudson Bambo
On 23 Jul 2018, at 12:15 PM, Blake Hansen <[email protected]> wrote:
Dear Eudson,
What was your DHIS2 version prior to upgrade? It seems like you are
encountering the change in data entry sharing that occurred from 2.29. Whereas
previously the ability for data entry was conferred specifically through the
‘data sets’ and ‘programs’ user roles, this is now done through ‘data’ sharing
levels. Additionally, the sharing also impacts category options. You can see
the DHIS2 documentation on this here:
https://www.dhis2.org/spotlight#datalevelsharing2 - scroll down to the Data
Level Sharing: Category Options and Data Sets video.
The route for fixing would seem to be giving your users who enter data the
sharing level ‘can capture data’. This would mean either conferring this
ability publicly on your category options, or adding these users to a specific
user group and giving the capture permission to that user group.
Trust this is a helpful start (and hopefully finish),Blake
--
<BAO_Logo_bright_padded.png>
Blake Hansen
Projects Implementation Manager, BAO Systems+1 202-536-1541 |
[email protected] | http://www.baosystems.com |Skype: blake.a.hansen |
2900 K Street, Suite 507, Washington D.C. 20007
On 23 Jul 2018, at 11:08, Eudson Bambo <[email protected]>
wrote:
Thanks Lars and Team.
This really great, DHIS2 is getting better and better.
So sorry for sending this on this thread but the problem is related to this
version.
Last week my team (infrastructure) decided to update our DHIS2 instance to this
version (2.30) and since then all non-superuser users are having problems
entering data, everyone is getting the follow error message: User has no data
write access for CategoryOption
I tried to check on the user roles and category options to see if I could
give/enable that permission to the non-superuser users but no luck so far.
Your help will be most appreciated.
Kind Regards,Eudson bambo
On 12 Jul 2018, at 1:43 PM, Lars Helge Øverland <[email protected]> wrote:
Hi all,
DHIS version 2.30 is out with many new features, apps and improvements.
Login with admin/district on the demo system.
ANALYTICS FEATURES---
Linkable dashboards: Individual dashboards can now be linked to through the
URL. This makes it easier to share dashboards through email and chats.
Screenshot | Demo
Mentions in interpretations and comments: You can now mention users in
interpretations and comments by using @. Users who are mentioned will receive a
notification in the messaging app. Notifications over email and SMS can also be
enabled through user settings. Interpretations can be written from the
right-side panel.
Screenshot | Demo
Subscribe to analytics items: You can now subscribe to analytics items.
Subscribing means that you will receive a notification whenever a new
interpretation or comment is made for the analytical object you subscribed to.
Look out for the bell icon.
Screenshot | Demo
Interpretations panel in maps: The maps app now has an interpretations panel to
the right which lets you write new interpretations and view existing ones for a
map.
Screenshot | Demo
File menu in maps: The maps app now supports the file menu you are used to from
pivot table and chart apps.
Screenshot | Demo
Buffers in event map layers: You can now render buffers for events in the maps
app. This is useful e.g. for visualizing coverage of health services. Zoom in
to see buffers on the demo.
Screenshot | Demo
Tracked entity thematic layer: The maps app now provides a thematic layer for
viewing tracked entities. Users can choose the the tracked entity type,
program, active or complete, period of last updated, organizational unit, and
style including an optional buffer.
Screenshot 1 | 2 | 3 | Demo
Style by data items in event maps: In the maps app you can now style each event
layer independently, i.e. chose the color and size of event points and clusters.
Screenshot 1 | 2 | Demo
APPS---
We have completely rewritten 5 web apps to provide a consistent and better user
interface and improve the software architecture:
User app: The user app has been redesigned with Material UI to provide a more
elegant and user-friendly interface. User roles and authorities management have
been reworked to make it a lot clearer and easier to get the overview of the
available authorities. Tracker authorities have been replaced to a large extent
by the new data level sharing model, simplifying the setup of tracker user
roles.
Screenshot 1 | 2 | Demo
Import-export app: The import-export app also has a new, fresh look. The new
app also exposes a lot more of the features and options available through the
API in a rich and intuitive interface.
Screenshot 1 | 2 | Demo
Messaging app: The messaging app is also refreshed, and styled in the manner of
modern email and messaging clients. Messages are categorised on the left to
allow clear distinction of different types of message for different uses. The
ticket message type allows the messaging platform to be used as a simple and
effective ticketing system. The new messaging app allows for adding people to
an existing conversation, and to search message conversations based on the
message content.
Screenshot 1 | 2 | 3 | Demo
Data quality app: The data quality app has been rewritten and features a
Material UI based design which is simpler and more intuitive to use.
Screenshot 1 | 2 | Demo
Data administration app: The data administration app has been rewritten and has
a nicer-looking UI. The analytics table generation UI has been moved here from
the reports app.
Screenshot 1 | 2 | Demo
TRACKER FEATURES---
MODEL UPDATES
Ownership concept: A tracked entity instance (TEI) can now be owned by one org
unit per program. The owner will be the latest organization unit that enrolled
the TEI into each program. A TEI is searchable in the context of every
organization unit that owns any programs for that tracked entity instance, as
well as the original registering organization unit. When performing a permanent
referral, ownership of the program in the tracked entity instance will be
transferred to the receiving organization unit, while the registration org unit
remains the same for the purposes of analytics.
Docs | Jira
Enhanced relationships: The relationship model is updated to be more expressive
and expandable. All relationships are now modelled as one-way relationships. In
version 2.30 relationships between tracked entity instances are supported. Each
side of the relationship now is constrained to a tracked entity type and the
types on the two sides might be different.
Screenshot | Jira
SECURITY
Improved UI for sharing programs and stages: Building on the new granular
sharing model there is now an improved UI for sharing programs and program
stages available. The add and edit program wizard now includes a step
calledAccess where the configurator will be presented with tools to share the
program and program stages.
Screenshot | Demo | Jira
Breaking the glass: If the program access level is set to protected the user is
now required to provide a reason for reading a tracked entity instance
belonging to an organisation unit where the user does not have data capture
access. The reason given will be stored and linked to the tracked entity
instance and program.
Screenshot | Docs| Jira
Improved audit logs: Audit logs will now retain information on users that read
enrollments, whether or not they change or enter data. This will enable
improved audit reporting tools and UI in future releases.
Docs| Jira
Capture polygons for events: It is now possible to to capture map polygons
instead of coordinates (points) for events.
Screenshot | Jira
PROGRAM RULES
Organisation unit groups in program rules: New function that allows program
rules to check whether the user is part of an organisation unit group.
Docs | Jira
Hide options and option group with program rules: Use program rules to
selectively hide options in an option set. Option groups can be used to hide or
show options effectively for large option sets. This feature can be used when
some data entered into an event can help qualify or disqualify options in an
option set. An example is showing relevant malaria vectors based on the
location of the infection.
Screenshot 1 | 2 | Docs | Jira
Variable for program rule runtime environment: Program rules now have a new
variable that can be used to see which runtime environment is triggering the
rule: Web client, Android client or server. This can be useful when making a
rule that for example only should run on the web client and not on Android.
Docs | Jira
UI RENDERING OPTIONS
Icon library for metadata: You now have the ability to associate icons to
programs, stages, data elements and the options of an option set. There are
currently 134 icons available through the maintenance app. In the Android app,
program icons render in the home screen, and stage icons render when adding a
new stage. For data elements and options, the icons render for single event
programs when a section contains a single data element.
Screenshot 1 | 2 | 3 | Demo | Docs | Jira
Color palette for metadata: The new Android app can now assign background
colours for programs, stages, data elements and options in option sets. A color
in the maintenance app allows selection from a optimized color palette.
Screenshot 1 | 2 | Demo | Docs | Jira
Rendering types for program sections: For the new Android app, a program
section with a single data element and associated option set can render the
options in sequential or matrix layout based on the the associated icon of the
option.
Screenshot 1 | 2 | 3 | Docs | Jira
GENERAL FEATURES---
Horizontal scalability: DHIS 2 can now be scaled horizontally at the
application layer by hosting multiple DHIS 2 application instances in a
cluster. Several technical challenges have beens solved, such as shared
sessions, shared application cache and cluster leader election through the use
of the Redis data store, and Hibernate cluster cache invalidation. The Redis
data store is a requirement for horizontal scalability.
Docs
Two-factor authentication: You can now enable two-factor authentication for
your DHIS 2 user. This lets you to enable a secondary authentication step for
improved performance, using aTOTP based authentication app such as Google
Authenticator. You can enable 2FA from Profile menu > Account settings. Admins
can disable 2FA for other users from the list of users in the user app.
Docs
API FEATURES---
_______________________________________________
Mailing list: https://launchpad.net/~dhis2-users
Post to : [email protected]
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp
--
Viet NguyenSoftware Developer, DHIS 2University of Oslohttp://www.dhis2.org
_______________________________________________
Mailing list: https://launchpad.net/~dhis2-users
Post to : [email protected]
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~dhis2-devs
Post to : [email protected]
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp
