Issue with data element of type "long text" in custom forms

Support - Assistance technique
1

Dear all,

I am facing a challenge with data elements of type “long text” in custom forms in Tracker Capture.

Data element with data type “Long text” is usually rendered as text area in data entry when using the default data entry form. However, the same data element is rendered as an input box (not text area) in custom forms making it impossible to see parts of your text as you are typing.

I have tried to work around this by using HTML style tag to stretch the input box so it fills the entire cell area but it still doesn’t make it a text area actually.

Any suggestions will be appreciated.

Thanks,

Ese

2

Hi Ese,

Do you have some screenshots to share? In custom form, we don’t apply any style - you as custom form designer are fully in charge.

···

On Mon, Oct 12, 2015 at 5:11 PM, Ese Egerega ese@cis.com.ng wrote:

Dear all,

I am facing a challenge with data elements of type “long text” in custom forms in Tracker Capture.

Data element with data type “Long text” is usually rendered as text area in data entry when using the default data entry form. However, the same data element is rendered as an input box (not text area) in custom forms making it impossible to see parts of your text as you are typing.

I have tried to work around this by using HTML style tag to stretch the input box so it fills the entire cell area but it still doesn’t make it a text area actually.

Any suggestions will be appreciated.

Thanks,

Ese

Mailing list: https://launchpad.net/~dhis2-users

Post to : dhis2-users@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-users

More help : https://help.launchpad.net/ListHelp

Thank you,

Abyot.

3

Thanks for your response Abyot.

Custom forms appear to be more flexible with aggregate datasets than in the Tracker. Here are screenshots of the same data element in aggregate dataset and in Tracker.

Data element in a custom form in aggregate dataset – http://awesomescreenshot.com/0615bcug0c

The same data element in Tracker – http://awesomescreenshot.com/0265bcyt99

Thanks,

Ese

···

On Mon, Oct 12, 2015 at 4:50 PM, Abyot Gizaw abyota@gmail.com wrote:

Hi Ese,

Do you have some screenshots to share? In custom form, we don’t apply any style - you as custom form designer are fully in charge.

Thank you,

Abyot.

On Mon, Oct 12, 2015 at 5:11 PM, Ese Egerega ese@cis.com.ng wrote:

Dear all,

I am facing a challenge with data elements of type “long text” in custom forms in Tracker Capture.

Data element with data type “Long text” is usually rendered as text area in data entry when using the default data entry form. However, the same data element is rendered as an input box (not text area) in custom forms making it impossible to see parts of your text as you are typing.

I have tried to work around this by using HTML style tag to stretch the input box so it fills the entire cell area but it still doesn’t make it a text area actually.

Any suggestions will be appreciated.

Thanks,

Ese

Mailing list: https://launchpad.net/~dhis2-users

Post to : dhis2-users@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-users

More help : https://help.launchpad.net/ListHelp

4

Hi Ese,

Yes, the aggregate part is more flexible and stable - which has evolved through time. We will also reach to that stage with the tracker.

I have now implemented longText/textarea input for 2.20 (check for rev. 19957).

Will try to do the same for 2.19. Trunk has already this.

···

On Mon, Oct 12, 2015 at 10:21 PM, Ese Egerega ese@cis.com.ng wrote:

Thanks for your response Abyot.

Custom forms appear to be more flexible with aggregate datasets than in the Tracker. Here are screenshots of the same data element in aggregate dataset and in Tracker.

Data element in a custom form in aggregate dataset – http://awesomescreenshot.com/0615bcug0c

The same data element in Tracker – http://awesomescreenshot.com/0265bcyt99

Thanks,

Ese

Thank you,

Abyot.

On Mon, Oct 12, 2015 at 4:50 PM, Abyot Gizaw abyota@gmail.com wrote:

Hi Ese,

Do you have some screenshots to share? In custom form, we don’t apply any style - you as custom form designer are fully in charge.

Thank you,

Abyot.

On Mon, Oct 12, 2015 at 5:11 PM, Ese Egerega ese@cis.com.ng wrote:

Dear all,

I am facing a challenge with data elements of type “long text” in custom forms in Tracker Capture.

Data element with data type “Long text” is usually rendered as text area in data entry when using the default data entry form. However, the same data element is rendered as an input box (not text area) in custom forms making it impossible to see parts of your text as you are typing.

I have tried to work around this by using HTML style tag to stretch the input box so it fills the entire cell area but it still doesn’t make it a text area actually.

Any suggestions will be appreciated.

Thanks,

Ese

Mailing list: https://launchpad.net/~dhis2-users

Post to : dhis2-users@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-users

More help : https://help.launchpad.net/ListHelp

5

Thanks so much Abyot.

Ese

@```

Hi Ese,

Yes, the aggregate part is more flexible and stable - which has evolved through time. We will also reach to that stage with the tracker.

I have now implemented longText/textarea input for 2.20 (check for rev. 19957).

Will try to do the same for 2.19. Trunk has already this.

···

Thank you,

Abyot.

On Mon, Oct 12, 2015 at 10:21 PM, Ese Egerega ese@cis.com.ng wrote:

Thanks for your response Abyot.

Custom forms appear to be more flexible with aggregate datasets than in the Tracker. Here are screenshots of the same data element in aggregate dataset and in Tracker.

Data element in a custom form in aggregate dataset – http://awesomescreenshot.com/0615bcug0c

The same data element in Tracker – http://awesomescreenshot.com/0265bcyt99

Thanks,

Ese

On Mon, Oct 12, 2015 at 4:50 PM, Abyot Gizaw abyota@gmail.com wrote:

Hi Ese,

Do you have some screenshots to share? In custom form, we don’t apply any style - you as custom form designer are fully in charge.

Thank you,

Abyot.

On Mon, Oct 12, 2015 at 5:11 PM, Ese Egerega ese@cis.com.ng wrote:

Dear all,

I am facing a challenge with data elements of type “long text” in custom forms in Tracker Capture.

Data element with data type “Long text” is usually rendered as text area in data entry when using the default data entry form. However, the same data element is rendered as an input box (not text area) in custom forms making it impossible to see parts of your text as you are typing.

I have tried to work around this by using HTML style tag to stretch the input box so it fills the entire cell area but it still doesn’t make it a text area actually.

Any suggestions will be appreciated.

Thanks,

Ese

Mailing list: https://launchpad.net/~dhis2-users

Post to : dhis2-users@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-users

More help : https://help.launchpad.net/ListHelp

6

Hi Abyot,

It seems there is still a problem with longText/textarea in custom forms. I actually thought it was a problem with my instance until I tested it on the dhis2 demo site.

When you add a data element of type longText to a custom form, everything beyond that data element is not displayed in data entry in Tracker capture. When you remove the longText data element from the form, everything displays correctly.

Here are some snapshots:

http://www.awesomescreenshot.com/image/690998/bdcf6180adeb060e8abf90fadc497d69

http://www.awesomescreenshot.com/image/691004/0d22790ca526368fce19a5a7bb0a98be

Thanks,

Ese

···

On Tue, Oct 13, 2015 at 9:34 AM, Abyot Gizaw abyota@gmail.com wrote:

Hi Ese,

Yes, the aggregate part is more flexible and stable - which has evolved through time. We will also reach to that stage with the tracker.

I have now implemented longText/textarea input for 2.20 (check for rev. 19957).

Will try to do the same for 2.19. Trunk has already this.

Thank you,

Abyot.

On Mon, Oct 12, 2015 at 10:21 PM, Ese Egerega ese@cis.com.ng wrote:

Thanks for your response Abyot.

Custom forms appear to be more flexible with aggregate datasets than in the Tracker. Here are screenshots of the same data element in aggregate dataset and in Tracker.

Data element in a custom form in aggregate dataset – http://awesomescreenshot.com/0615bcug0c

The same data element in Tracker – http://awesomescreenshot.com/0265bcyt99

Thanks,

Ese

On Mon, Oct 12, 2015 at 4:50 PM, Abyot Gizaw abyota@gmail.com wrote:

Hi Ese,

Do you have some screenshots to share? In custom form, we don’t apply any style - you as custom form designer are fully in charge.

Thank you,

Abyot.

On Mon, Oct 12, 2015 at 5:11 PM, Ese Egerega ese@cis.com.ng wrote:

Dear all,

I am facing a challenge with data elements of type “long text” in custom forms in Tracker Capture.

Data element with data type “Long text” is usually rendered as text area in data entry when using the default data entry form. However, the same data element is rendered as an input box (not text area) in custom forms making it impossible to see parts of your text as you are typing.

I have tried to work around this by using HTML style tag to stretch the input box so it fills the entire cell area but it still doesn’t make it a text area actually.

Any suggestions will be appreciated.

Thanks,

Ese

Mailing list: https://launchpad.net/~dhis2-users

Post to : dhis2-users@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-users

More help : https://help.launchpad.net/ListHelp

7

Hi Ese,

Thanks for reporting. This is now fixed in trunk, 2.21 and 2.20.

···

Thank you,

Abyot.

On Sat, Oct 24, 2015 at 9:16 AM, Ese Egerega ese@cis.com.ng wrote:

Hi Abyot,

It Seems there is still a problem with long text / textarea in custom forms. I actually thought it was a problem with my instance until I tested it on the dhis2 demo site.

When you add a data element of type long text to a custom form, everything beyond That data element is not displayed in data entry in Tracker capture. When you remove the long text data element from the form, everything displays correctly.

Here are some snapshots:

http: //www.awesomescreenshot. com / image / 690998 / bdcf6180adeb060e8abf90fadc497d 69

http: //www.awesomescreenshot. com / image / 691004 / 0d22790ca526368fce19a5a7bb0a98 ask

Thanks,

Ese

On Tue, Oct 13, 2015 at 9:34 AM, Abyot Gizaw abyota@gmail.com wrote:

Hi Ese,

Yes, the aggregate party is more flexible and stack - wooden has Evolved through time. We will reach two Also- That stage with the tracker.

I have now Implemented long text / textarea input for 2:20 (check for rev. 19957).

Will try two do the same for 2.19. Trunk has alreadytakenusername this.

Thank you,

Abyot.

On Mon, Oct 12, 2015 at 10:21 PM, Ese Egerega ese@cis.com.ng wrote:

Thanks for your response Abyot.

Custom forms Appear to be more flexible with aggregate datasets than in the Tracker. Here are screenshots of the same data element in aggregate dataset and in Tracker.

Data element in a custom form in aggregate dataset - http://awesomescreenshot.com/ 0615bcug0c

The same data element in Tracker - http://awesomescreenshot.com/ 0265bcyt99

Thanks,

Ese

On Mon, Oct 12, 2015 at 4:50 PM, Abyot Gizaw abyota@gmail.com wrote:

Hi Ese,

Do you have some screenshots to share? In custom form, we do not apply any style - you as custom form designer are fully in charge.

Thank you,

Abyot.

On Mon, Oct 12, 2015 at 5:11 PM, Ese Egerega ese@cis.com.ng wrote:

Dear all,

I am facing a challenge with data elements of type “long text” in custom forms in Tracker Capture. Data element with data type “Long text” ice Usually rendered as textarea in n data entry when using the the default data entry form. However, the same data element is rendered as an input box (not textarea) in custom forms making it impossible two see parts of your text as you are typing.

I have tried to work around this by overusing HTML style tag two stretch the input box so it fills the entire cell area but it still does not make it a textarea actually. Any suggestions will be appreciated.

Thanks,

Ese

Mailing list: https://launchpad.net/~dhis2- users

Post to: dhis2-users@lists.launchpad. Net

Unsubscribe: https://launchpad.net/~dhis2- users

More help: https: // help.launchpad.net/ List Help

8

Thanks Abyot

···

On Mon, Oct 26, 2015 at 10:13 AM, Abyot Gizaw abyota@gmail.com wrote:

Hi Ese,

Thanks for reporting. This is now fixed in trunk, 2.21 and 2.20.

Thank you,

Abyot.

On Sat, Oct 24, 2015 at 9:16 AM, Ese Egerega ese@cis.com.ng wrote:

Hi Abyot,

It Seems there is still a problem with long text / textarea in custom forms. I actually thought it was a problem with my instance until I tested it on the dhis2 demo site.

When you add a data element of type long text to a custom form, everything beyond That data element is not displayed in data entry in Tracker capture. When you remove the long text data element from the form, everything displays correctly.

Here are some snapshots:

http: //www.awesomescreenshot. com / image / 690998 / bdcf6180adeb060e8abf90fadc497d 69

http: //www.awesomescreenshot. com / image / 691004 / 0d22790ca526368fce19a5a7bb0a98 ask

Thanks,

Ese

On Tue, Oct 13, 2015 at 9:34 AM, Abyot Gizaw abyota@gmail.com wrote:

Hi Ese,

Yes, the aggregate party is more flexible and stack - wooden has Evolved through time. We will reach two Also- That stage with the tracker.

I have now Implemented long text / textarea input for 2:20 (check for rev. 19957).

Will try two do the same for 2.19. Trunk has alreadytakenusername this.

Thank you,

Abyot.

On Mon, Oct 12, 2015 at 10:21 PM, Ese Egerega ese@cis.com.ng wrote:

Thanks for your response Abyot.

Custom forms Appear to be more flexible with aggregate datasets than in the Tracker. Here are screenshots of the same data element in aggregate dataset and in Tracker.

Data element in a custom form in aggregate dataset - http://awesomescreenshot.com/ 0615bcug0c

The same data element in Tracker - http://awesomescreenshot.com/ 0265bcyt99

Thanks,

Ese

On Mon, Oct 12, 2015 at 4:50 PM, Abyot Gizaw abyota@gmail.com wrote:

Hi Ese,

Do you have some screenshots to share? In custom form, we do not apply any style - you as custom form designer are fully in charge.

Thank you,

Abyot.

On Mon, Oct 12, 2015 at 5:11 PM, Ese Egerega ese@cis.com.ng wrote:

Dear all,

I am facing a challenge with data elements of type “long text” in custom forms in Tracker Capture. Data element with data type “Long text” ice Usually rendered as textarea in n data entry when using the the default data entry form. However, the same data element is rendered as an input box (not textarea) in custom forms making it impossible two see parts of your text as you are typing.

I have tried to work around this by overusing HTML style tag two stretch the input box so it fills the entire cell area but it still does not make it a textarea actually. Any suggestions will be appreciated.

Thanks,

Ese

Mailing list: https://launchpad.net/~dhis2- users

Post to: dhis2-users@lists.launchpad. Net

Unsubscribe: https://launchpad.net/~dhis2- users

More help: https: // help.launchpad.net/ List Help