dhis2-users team mailing list archive
-
dhis2-users team
-
Mailing list archive
-
Message #12538
Re: Error message : Form is invalid. Please checkforrequired fields.
Hi Timothy,
Are you sure all the required data elements are part of the custom form?
That was not the case with the db you sent to me.
Can you check this without the custom form?
--
Abyot A. Gizaw.
Senior Engineer, DHIS2
University of Oslo
http://www.dhis2.org
On Fri, Feb 10, 2017 at 6:46 AM, Timothy Kiyemba <tkiyemba@xxxxxxxxx> wrote:
> Dear Abyot,
>
> Just to replicate the steps a bit, I have removed my declarations for
> required fields from program rules then I have maintained it only under the
> set up of the program stage for Form 1 - training and sensitisation. I have
> declared the 9 fields as compulsory under the set up of the variables for
> the stage. When I get back to data entry and click save, it highlights all
> required fields, I fill each of them up (all 9) but the red error message "Form
> is invalid. Please check for required fields" still remains at the bottom
> of the form. I really can't figure out what I am missing.
>
> Timothy
>
> On Thu, Feb 9, 2017 at 8:09 PM, Timothy Kiyemba <tkiyemba@xxxxxxxxx>
> wrote:
>
>> Could it be because I declared them both as program rules and also as
>> required fields under the program?. Is it enough for me to declare them as
>> required fields under the program stage? Just thinking
>>
>> On Thu, Feb 9, 2017 at 7:44 PM, timothy kiyemba <tkiyemba@xxxxxxxxx>
>> wrote:
>>
>>> Dear Abyot,
>>>
>>> The custom form has distributed IECs variable as well. However its a
>>> yes/no field. Could it be that its not recognising it?
>>>
>>> Timothy
>>> ------------------------------
>>> From: Abyot Asalefew Gizaw <abyot@xxxxxxxxx>
>>> Sent: 09/02/2017 18:13
>>> To: timothy kiyemba <tkiyemba@xxxxxxxxx>
>>> Cc: dhis2-devs <dhis2-devs@xxxxxxxxxxxxxxxxxxx>; DHIS 2 Users list
>>> <dhis2-users@xxxxxxxxxxxxxxxxxxx>
>>> Subject: Re: [Dhis2-users] Error message : Form is invalid. Please
>>> checkforrequired fields.
>>>
>>> Hi Timothy,
>>>
>>> I just checked your system - specifically program "Form 01 - Training
>>> and Sensitisation".
>>>
>>> You have *NINE* compulsory data elements, however your custom form
>>> contains only *EIGHT* of them. I think the missing data element is
>>> "Distributed IECs". Please check your custom form.
>>>
>>>
>>> --
>>> Abyot A. Gizaw.
>>> Senior Engineer, DHIS2
>>> University of Oslo
>>> http://www.dhis2.org
>>>
>>> On Wed, Feb 8, 2017 at 7:03 PM, timothy kiyemba <tkiyemba@xxxxxxxxx>
>>> wrote:
>>>
>>>> Dear Abyot,
>>>>
>>>> I have cross checked. I do not have any hidden fields on the form.
>>>> Tried filling up all of them but this message continues to persist at the
>>>> bottom of the entry form.
>>>>
>>>> Timothy
>>>> ------------------------------
>>>> From: Abyot Gizaw <abyota@xxxxxxxxx>
>>>> Sent: 08/02/2017 20:33
>>>> To: Timothy Kiyemba <tkiyemba@xxxxxxxxx>
>>>> Cc: dhis2-devs <dhis2-devs@xxxxxxxxxxxxxxxxxxx>; DHIS 2 Users list
>>>> <dhis2-users@xxxxxxxxxxxxxxxxxxx>
>>>> Subject: Re: [Dhis2-users] Error message : Form is invalid. Please
>>>> check forrequired fields.
>>>>
>>>> See if a required field is hidden by a program rule.
>>>>
>>>> ---
>>>>
>>>> Thank you,
>>>> Abyot.
>>>> (sent from mobile)
>>>>
>>>> On Feb 8, 2017 18:25, "Timothy Kiyemba" <tkiyemba@xxxxxxxxx> wrote:
>>>>
>>>> Dear all,
>>>>
>>>> I am trying to create program rules but on trying to perform trial
>>>> entries I get the error message ;
>>>>
>>>> "Form is invalid. Please check for required fields."
>>>>
>>>> Is this a bug? or is there something I am missing.
>>>>
>>>> I have gone through all the fields and I have performed entry for all
>>>> the required fields.
>>>>
>>>> Please help. I am working with DHIS2 2.25.
>>>>
>>>> Kind regards
>>>>
>>>> Timothy
>>>>
>>>> _______________________________________________
>>>> Mailing list: https://launchpad.net/~dhis2-users
>>>> Post to : dhis2-users@xxxxxxxxxxxxxxxxxxx
>>>> Unsubscribe : https://launchpad.net/~dhis2-users
>>>> More help : https://help.launchpad.net/ListHelp
>>>>
>>>>
>>>>
>>>
>>
>
Follow ups
References