dhis2-devs team mailing list archive
-
dhis2-devs team
-
Mailing list archive
-
Message #51153
Re: 2.29: Illegal data element identifier
Going to move this into a Jira bug:
https://jira.dhis2.org/browse/DHIS2-3612
I can oscillate having data capture and not having data capture by adding a
group with "data view" access.
*Timothy Harding*
Sr. Systems Analyst, BAO Systems
+1 202-536-1541 | tharding@xxxxxxxxxxxxxx | http://www.baosystems.com | Skype:
hardingt@xxxxxxxxx | 2900 K Street, Suite 507, Washington D.C. 20007
On Wed, May 2, 2018 at 3:57 PM, Timothy Harding <tharding@xxxxxxxxxxxxxx>
wrote:
> Hello!
>
> I'm getting the following when trying to enter data:
>
> The user has the following permissions:
>
> - Data Entry App Access
> - Data Value Create Access
> - Is in a group that is shared with this dataset "Can View [metadata]
> and "Can Capture Data"
> - Is in a group that is shared with the Attribute Option "Can View
> [metadata] and "Can Capture Data"
> - Has access to see all objects contained within the dataset.
>
> I arrived at this state by first creating a user that had one additional
> permission:
>
> - Is in a group that is shared with this dataset "Can View [metadata]
> and "Can View Data"
>
> I was able to enter the 1 and the 4 with both of those groups (can view
> data in one group, can capture data in another)
>
> When I removed the second group, the one with "Can View Data", it turns
> red (the 5) and gives me the illegal data element identifier notice, with
> all else being equal.
>
> Since a group cannot be both View and Capture, needing both seems to be a
> bit excessive, as I thought one implied the other. But that might not be
> what is going on here. Any thoughts or ideas, or should I report this as a
> 2.29 bug?
>
>
>
> *Timothy Harding*
> Sr. Systems Analyst, BAO Systems
> +1 202-536-1541 | tharding@xxxxxxxxxxxxxx | http://www.baosystems.com | Skype:
> hardingt@xxxxxxxxx | 2900 K Street, Suite 507, Washington D.C. 20007
>
References