dhis2-devs team mailing list archive

[Morten Olav Hansen <mortenoh@xxxxxxxxx>]

Please also remember that data elements can be shared by multiple data
sets, so you would have to set expiry days to 0 in all data sets which
contains the data elements you want to enter data for.

--
Morten

On Fri, Sep 11, 2015 at 3:12 PM, Jason Pickering <
jason.p.pickering@xxxxxxxxx> wrote:

> Hi Gerald,
> This red data elements indicate that the data is outside of the min-max.
> It has nothing to do with data locking.
>
> Please confirm a few things.
>
> 1) In your datasets settings, be sure that "Expiry days" is set to 0.
>
> 2) Are you using data approvals? If so, this could be the reason you are
> seeing that the data set is locked.
>
> Regards,
> Jason
>
>
>
> On Fri, Sep 11, 2015 at 9:58 AM, gerald thomas <gerald17006@xxxxxxxxx>
> wrote:
>
>> Dear Knut,
>> It is not working. Don't you think it is a bug? Because it is not
>> happening for the whole form; it only occur for those data elements
>> within the forms whilst the others are submitted.
>>
>> Please find the attached view.
>>
>> On 9/11/15, Knut Staring <knutst@xxxxxxxxx> wrote:
>> > But did you try Morten's suggestion?
>> >
>> > If not, please select Data Set from the menu and again click on Data Set
>> > (in the submenu). You will see a list of your forms (HF1, HF2, HF3, HF4,
>> > HF5, HF6, HF7 and HF8)
>> >
>> > For each of them, click and select edit. In the field "Expiry days",
>> change
>> > the value to 0, and Save.
>> >
>> > I hope this will remove the problem.
>> >
>> > Knut
>> >
>> > On Fri, Sep 11, 2015 at 10:23 AM, gerald thomas <gerald17006@xxxxxxxxx>
>> > wrote:
>> >
>> >> Dear Knut,
>> >> I am so much confused that i really don't know what to do or how to
>> >> explain this issues to our Director.
>> >> I had already remove all the lock exceptions but the issue is the
>> >> same. I have another topic on the forum which is "Data Loss"; i only
>> >> found out that these data are actually not submitting these data on
>> >> the database.
>> >> I don't know if it is a bug but we need to fix this issues.
>> >>
>> >> Thanks in advance for your time and cooperation.
>> >>
>> >> On 9/11/15, Knut Staring <knutst@xxxxxxxxx> wrote:
>> >> > Dear Gerald,
>> >> >
>> >> > So you are in fact NOT looking to remove all lock exceptions
>> >> > completely?
>> >> > You want to keep them, but you have a problem with how they function?
>> >> >
>> >> >
>> >> >
>> >> > On Fri, Sep 11, 2015 at 10:04 AM, gerald thomas <
>> gerald17006@xxxxxxxxx>
>> >> > wrote:
>> >> >
>> >> >> Dear Morten,
>> >> >> Sierra Leone is experience a rear situation.
>> >> >> There is a lock exception which was activated for the various
>> >> >> forms(HF1, HF2, HF3, HF4, HF5, HF6, HF7 and HF8) per month. But when
>> >> >> the rule are remove for those particular months; on HF1(No. of fever
>> >> >> cases, total head counts, total OPD, No. of pregnant women treated,
>> >> >> No. of lactating mothers treated) and HF8(Antenatal) these data
>> >> >> elements are still showing "Data Sets is Locked" and these values
>> are
>> >> >> not being submitted into the database.
>> >> >>
>> >> >> Please find the attached view of the data elements.
>> >> >>
>> >> >>
>> >> >>
>> >> >> On 9/11/15, Morten Olav Hansen <mortenoh@xxxxxxxxx> wrote:
>> >> >> > Hi
>> >> >> >
>> >> >> > As I said, all you have to do is to edit your data set, and set
>> >> >> > expiry
>> >> >> days
>> >> >> > to 0. That will make sure that the data set never expires.
>> >> >> >
>> >> >> > I assume you mean deactivate data set locks, not exceptions.
>> >> >> >
>> >> >> > --
>> >> >> > Morten
>> >> >> >
>> >> >> > On Fri, Sep 11, 2015 at 9:21 AM, gerald thomas
>> >> >> > <gerald17006@xxxxxxxxx
>> >> >
>> >> >> > wrote:
>> >> >> >
>> >> >> >> Dear All,
>> >> >> >> I am using 2.18 and i want to know how i can deactivate lock
>> >> exception
>> >> >> >> on data elements permanently.
>> >> >> >> Please help me it is urgent.
>> >> >> >> --
>> >> >> >> Regards,
>> >> >> >>
>> >> >> >> Gerald
>> >> >> >>
>> >> >> >> _______________________________________________
>> >> >> >> Mailing list: https://launchpad.net/~dhis2-devs
>> >> >> >> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
>> >> >> >> Unsubscribe : https://launchpad.net/~dhis2-devs
>> >> >> >> More help   : https://help.launchpad.net/ListHelp
>> >> >> >>
>> >> >> >
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Regards,
>> >> >>
>> >> >> Gerald
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Knut Staring
>> >> > Dept. of Informatics, University of Oslo
>> >> > Norway: +4791880522
>> >> > Skype: knutstar
>> >> > http://dhis2.org
>> >> >
>> >>
>> >>
>> >> --
>> >> Regards,
>> >>
>> >> Gerald
>> >>
>> >
>> >
>> >
>> > --
>> > Knut Staring
>> > Dept. of Informatics, University of Oslo
>> > Norway: +4791880522
>> > Skype: knutstar
>> > http://dhis2.org
>> >
>>
>>
>> --
>> Regards,
>>
>> Gerald
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~dhis2-devs
>> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~dhis2-devs
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> --
> Jason P. Pickering
> email: jason.p.pickering@xxxxxxxxx
> tel:+46764147049
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-devs
> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-devs
> More help   : https://help.launchpad.net/ListHelp
>
>