We got a custom HTML in version 2.20 that populates values(in the drop down list) captured on the form but upon upgrading the db we find that the fields have changed to radio buttons and are not populating the values captured. Is there something that we’ve missed in the upgrade process or is there a setting that we can adjust for the populating of the values?
Regards
Pooben
This message and any attachments are subject to a disclaimer published at http://www.hisp.org/policies.html#comms_disclaimer. Please read the disclaimer before opening any attachment or taking any other action in terms of this electronic transmission. If you cannot access the disclaimer, kindly send an email to disclaimer@hisp.org and a copy will be provided to you. By replying to this e-mail or opening any attachment you agree to be bound by the provisions of the disclaimer.
what type of form is this, i.e. tracker or aggregate?
regards,
Lars
···
On Mon, Jun 12, 2017 at 11:27 AM, Pooben Dass pooben@hisp.org wrote:
Hi Devs
We got a custom HTML in version 2.20 that populates values(in the drop down list) captured on the form but upon upgrading the db we find that the fields have changed to radio buttons and are not populating the values captured. Is there something that we’ve missed in the upgrade process or is there a setting that we can adjust for the populating of the values?
Regards
Pooben
This message and any attachments are subject to a disclaimer published at http://www.hisp.org/policies.html#comms_disclaimer. Please read the disclaimer before opening any attachment or taking any other action in terms of this electronic transmission. If you cannot access the disclaimer, kindly send an email to disclaimer@hisp.org and a copy will be provided to you. By replying to this e-mail or opening any attachment you agree to be bound by the provisions of the disclaimer.
Its an aggregate form. I’ve changed the display of the radio buttons and now the values pull through but the changing of the field type from drop downs to radio buttons has deleted some of the custom code that was attached to the fields.
Regards
Pooben
This message and any attachments are subject to a disclaimer published at http://www.hisp.org/policies.html#comms_disclaimer. Please read the disclaimer before opening any attachment or taking any other action in terms of this electronic transmission. If you cannot access the disclaimer, kindly send an email to disclaimer@hisp.org and a copy will be provided to you. By replying to this e-mail or opening any attachment you agree to be bound by the provisions of the disclaimer.
···
On Tue, Jun 13, 2017 at 11:13 AM, Lars Helge Øverland lars@dhis2.org wrote:
Hi Pooben,
what type of form is this, i.e. tracker or aggregate?
regards,
Lars
On Mon, Jun 12, 2017 at 11:27 AM, Pooben Dass pooben@hisp.org wrote:
Hi Devs
We got a custom HTML in version 2.20 that populates values(in the drop down list) captured on the form but upon upgrading the db we find that the fields have changed to radio buttons and are not populating the values captured. Is there something that we’ve missed in the upgrade process or is there a setting that we can adjust for the populating of the values?
Regards
Pooben
This message and any attachments are subject to a disclaimer published at http://www.hisp.org/policies.html#comms_disclaimer. Please read the disclaimer before opening any attachment or taking any other action in terms of this electronic transmission. If you cannot access the disclaimer, kindly send an email to disclaimer@hisp.org and a copy will be provided to you. By replying to this e-mail or opening any attachment you agree to be bound by the provisions of the disclaimer.