← Back to team overview

dhis2-devs team mailing list archive

Re: Bug in 2.18 data entry?

 

Hi, 
thanks for the suggestion. I did that now (and cleared both nginx and browser caches), but I still have the same problem.

Olav



> 28. apr. 2015 kl. 16.52 skrev Dan Cocos <dcocos@xxxxxxxxx>:
> 
> Hi Olav,
> 
> I saw something like this happen recently as well, updating to the latest 2.18 resolved the problem. 
> 
> Thanks,
> Dan
> 
> 
> Dan Cocos
> BAO Systems
> www.baosystems.com <http://www.baosystems.com/>
> T: +1 202-352-2671 | skype: dancocos
> 
>> On Apr 28, 2015, at 10:50 AM, Olav Poppe <olav.poppe@xxxxxx <mailto:olav.poppe@xxxxxx>> wrote:
>> 
>> Hi, I’m experiencing a strange problem after upgrading from 2.16 to 2.18 (through 2.17): for certain datasets, regular users do not see existing data in the data entry screen (and in some cases no form either, but not sure if the two issues are related). For superusers, there is no problem.
>> 
>> I’ve tried to open the getDataValues URL with a "data entry user" account to see if I could see the raw values, but it is emtpy (like this: ../dhis/dhis-web-dataentry/getDataValues.action?periodId=201503&dataSetId=SVxIdNuoFxg&organisationUnitId=vrV9Pt3ByZQ&multiOrganisationUnit=false <http://burkina.dhis2.org/dhis/dhis-web-dataentry/getDataValues.action?periodId=201503&dataSetId=SVxIdNuoFxg&organisationUnitId=vrV9Pt3ByZQ&multiOrganisationUnit=false&_=1430230594612>). However, when I do this I see this following in the tomcat log, where the key part seems to be "data set: null":
>> * WARN  2015-04-28 14:42:21,638 Illegal input, org unit: [IdentifiableObject: id='11363', uid='vrV9Pt3ByZQ', code='null', name='CSPS Boundoré', created='2012-07-11 17:27:02.358', lastUpdated='2014-02-19 10:50:26.545', class='class org.hisp.dhis.organisationunit.OrganisationUnit"'], period: [Monthly: Sun Mar 01 00:00:00 UTC 2015 - Tue Mar 31 00:00:00 UTC 2015], data set: null (GetDataValuesForDataSetAction.java [tomcat-http-54])
>> 
>> Opening the exact same URL with a superuser account gives the existing values as expected, and no error in the tomcat log.
>> 
>> Some additional info on the datasets causing problems:
>> - sharing is not used, i.e. public: read and write
>> - approval is not enabled
>> - expiry/locking is not enabled
>> - the users roles all have see data entry module, add data value, delete data value and have the dataset assigned.
>> 
>> Any ideas? The issue was not picked up when testing 2.18, so it is happening on a production database - a quick response would be appreciated!
>> 
>> Thanks
>> Olav
>> _______________________________________________
>> Mailing list: https://launchpad.net/~dhis2-devs <https://launchpad.net/~dhis2-devs>
>> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx <mailto:dhis2-devs@xxxxxxxxxxxxxxxxxxx>
>> Unsubscribe : https://launchpad.net/~dhis2-devs <https://launchpad.net/~dhis2-devs>
>> More help   : https://help.launchpad.net/ListHelp <https://help.launchpad.net/ListHelp>
> 


Follow ups

References