Hi,
In order to constrain the answers of users in my forms to under 255
characters I've been wanting to use a binding like this
However, putting in this regex constraint now seems to crash ODK Collect if
anymore than 61 characters are entered in the field on the form. I have no
idea what is magical about 61 characters but I've tested this repeatedly on
multiple forms and 61 characters seems to be the limit.
The crash message is: "Sorry! The application ODK Collect (process
org.odk.collect.android) has stopped unexpectedly. Please try again."
Any ideas what could be wrong? This seems to be the recommended regex
anywhere I've looked and I can't find any reference to anyone else having
this problem. Ironically if I leave out the constraint then 255 characters
can be entered but without the warning, my users frequently go over (they
are a wordy lot) and have their answers chopped off in ODK Aggregate.
I've also tried this:
However then it requires exactly 255 characters for an answer.
We are using a mixture of Samsung Galaxy SI and SII phones with Android
2.3.4 & 2.3.5 running ODK Collect 1.3 (1030) submitting to ODK Aggregate
1.3.1 on Google's AppEngine.
Hi,
In order to constrain the answers of users in my forms to under 255
characters I've been wanting to use a binding like this
However, putting in this regex constraint now seems to crash ODK Collect if
anymore than 61 characters are entered in the field on the form. I have no
idea what is magical about 61 characters but I've tested this repeatedly on
multiple forms and 61 characters seems to be the limit.
The crash message is: "Sorry! The application ODK Collect (process
org.odk.collect.android) has stopped unexpectedly. Please try again."
Any ideas what could be wrong? This seems to be the recommended regex
anywhere I've looked and I can't find any reference to anyone else having
this problem. Ironically if I leave out the constraint then 255 characters
can be entered but without the warning, my users frequently go over (they
are a wordy lot) and have their answers chopped off in ODK Aggregate.
I've also tried this:
However then it requires exactly 255 characters for an answer.
We are using a mixture of Samsung Galaxy SI and SII phones with Android
2.3.4 & 2.3.5 running ODK Collect 1.3 (1030) submitting to ODK Aggregate
1.3.1 on Google's AppEngine.
Hi,
In order to constrain the answers of users in my forms to under 255
characters I've been wanting to use a binding like this
However, putting in this regex constraint now seems to crash ODK Collect
if
anymore than 61 characters are entered in the field on the form. I have
no
idea what is magical about 61 characters but I've tested this repeatedly
on
multiple forms and 61 characters seems to be the limit.
The crash message is: "Sorry! The application ODK Collect (process
org.odk.collect.android) has stopped unexpectedly. Please try again."
Any ideas what could be wrong? This seems to be the recommended regex
anywhere I've looked and I can't find any reference to anyone else having
this problem. Ironically if I leave out the constraint then 255
characters
can be entered but without the warning, my users frequently go over (they
are a wordy lot) and have their answers chopped off in ODK Aggregate.
I've also tried this:
However then it requires exactly 255 characters for an answer.
We are using a mixture of Samsung Galaxy SI and SII phones with
Android
2.3.4 & 2.3.5 running ODK Collect 1.3 (1030) submitting to ODK Aggregate
1.3.1 on Google's AppEngine.
If you have a MySQL or PostgreSQL database, you should be able to ALTER
TABLE and increase the storage amount (but you won't be able to shrink it)
after-the-fact without updating your form (you just need to shut down and
restart ODK Aggregate to begin using the new string sizes).
Unfortunately, adding these storage size directives to a form is an
incompatible form change, necessitating a change in the formId, or a flush
and reload of ODK Aggregate via ODK Briefcase.
Mitch
···
On Fri, May 17, 2013 at 9:06 AM, Greg Pommen wrote:
Well at least I'm not crazy (completely). Thank you!
Hi,
In order to constrain the answers of users in my forms to under 255
characters I've been wanting to use a binding like this
However, putting in this regex constraint now seems to crash ODK
Collect if
anymore than 61 characters are entered in the field on the form. I
have no
idea what is magical about 61 characters but I've tested this
repeatedly on
multiple forms and 61 characters seems to be the limit.
The crash message is: "Sorry! The application ODK Collect (process
org.odk.collect.android) has stopped unexpectedly. Please try again."
Any ideas what could be wrong? This seems to be the recommended
regex
anywhere I've looked and I can't find any reference to anyone else
having
this problem. Ironically if I leave out the constraint then 255
characters
can be entered but without the warning, my users frequently go over
(they
are a wordy lot) and have their answers chopped off in ODK Aggregate.
I've also tried this:
However then it requires exactly 255 characters for an answer.
We are using a mixture of Samsung Galaxy SI and SII phones with
Android
2.3.4 & 2.3.5 running ODK Collect 1.3 (1030) submitting to ODK Aggregate
1.3.1 on Google's AppEngine.
Thank you for the idea, I'll see if it would help. I would still really
like to be able to set a limit within the form so I'll eagerly await the
bug fix too! BTW we have everything publishing to Google Fusion Tables or
Google Spreadsheets.
Greg
···
On Fri, May 17, 2013 at 4:04 PM, Mitch Sundt wrote:
If you have a MySQL or PostgreSQL database, you should be able to ALTER
TABLE and increase the storage amount (but you won't be able to shrink it)
after-the-fact without updating your form (you just need to shut down and
restart ODK Aggregate to begin using the new string sizes).
Unfortunately, adding these storage size directives to a form is an
incompatible form change, necessitating a change in the formId, or a flush
and reload of ODK Aggregate via ODK Briefcase.
Hi,
In order to constrain the answers of users in my forms to under 255
characters I've been wanting to use a binding like this
However, putting in this regex constraint now seems to crash ODK
Collect if
anymore than 61 characters are entered in the field on the form. I
have no
idea what is magical about 61 characters but I've tested this
repeatedly on
multiple forms and 61 characters seems to be the limit.
The crash message is: "Sorry! The application ODK Collect (process
org.odk.collect.android) has stopped unexpectedly. Please try again."
Any ideas what could be wrong? This seems to be the recommended
regex
anywhere I've looked and I can't find any reference to anyone else
having
this problem. Ironically if I leave out the constraint then 255
characters
can be entered but without the warning, my users frequently go over
(they
are a wordy lot) and have their answers chopped off in ODK Aggregate.
I've also tried this:
However then it requires exactly 255 characters for an answer.
We are using a mixture of Samsung Galaxy SI and SII phones with
Android
2.3.4 & 2.3.5 running ODK Collect 1.3 (1030) submitting to ODK
Aggregate
1.3.1 on Google's AppEngine.
···
On Tue, May 21, 2013 at 7:04 AM, Greg Pommen wrote:
Thank you for the idea, I'll see if it would help. I would still really
like to be able to set a limit within the form so I'll eagerly await the
bug fix too! BTW we have everything publishing to Google Fusion Tables or
Google Spreadsheets.
If you have a MySQL or PostgreSQL database, you should be able to ALTER
TABLE and increase the storage amount (but you won't be able to shrink it)
after-the-fact without updating your form (you just need to shut down and
restart ODK Aggregate to begin using the new string sizes).
Unfortunately, adding these storage size directives to a form is an
incompatible form change, necessitating a change in the formId, or a flush
and reload of ODK Aggregate via ODK Briefcase.
Hi,
In order to constrain the answers of users in my forms to under
255
characters I've been wanting to use a binding like this
However, putting in this regex constraint now seems to crash ODK
Collect if
anymore than 61 characters are entered in the field on the form. I
have no
idea what is magical about 61 characters but I've tested this
repeatedly on
multiple forms and 61 characters seems to be the limit.
The crash message is: "Sorry! The application ODK Collect (process
org.odk.collect.android) has stopped unexpectedly. Please try again."
Any ideas what could be wrong? This seems to be the recommended
regex
anywhere I've looked and I can't find any reference to anyone else
having
this problem. Ironically if I leave out the constraint then 255
characters
can be entered but without the warning, my users frequently go over
(they
are a wordy lot) and have their answers chopped off in ODK Aggregate.
I've also tried this:
However then it requires exactly 255 characters for an answer.
We are using a mixture of Samsung Galaxy SI and SII phones with
Android
2.3.4 & 2.3.5 running ODK Collect 1.3 (1030) submitting to ODK
Aggregate
1.3.1 on Google's AppEngine.
That seems to work, as long as I changed ' <= 255' to ' < 256 '.
FYI, the original regex I was using ' constraint="regex(., '^.{0,255}$')"
' was off the page: http://opendatakit.org/help/form-design/binding/ .
Perhaps the 61 char limitation needs to be mentioned on there in addition
to changing any of the references to the symbols <, >, or = to < >
&eq; for all the other examples too. Unless I'm missing something which
is quite likely as well.
Thanks again!
···
On Tue, May 21, 2013 at 3:29 PM, Mitch Sundt wrote:
I suspect this was failing due to a stack overflow. Larger tablets and
higher-resolution devices will have more memory and may work.
However, if all you need to do is restrict the length of the string, you
can use
Thank you for the idea, I'll see if it would help. I would still really
like to be able to set a limit within the form so I'll eagerly await the
bug fix too! BTW we have everything publishing to Google Fusion Tables or
Google Spreadsheets.
If you have a MySQL or PostgreSQL database, you should be able to ALTER
TABLE and increase the storage amount (but you won't be able to shrink it)
after-the-fact without updating your form (you just need to shut down and
restart ODK Aggregate to begin using the new string sizes).
Unfortunately, adding these storage size directives to a form is an
incompatible form change, necessitating a change in the formId, or a flush
and reload of ODK Aggregate via ODK Briefcase.
Hi,
In order to constrain the answers of users in my forms to under
255
characters I've been wanting to use a binding like this
However, putting in this regex constraint now seems to crash ODK
Collect if
anymore than 61 characters are entered in the field on the form. I
have no
idea what is magical about 61 characters but I've tested this
repeatedly on
multiple forms and 61 characters seems to be the limit.
The crash message is: "Sorry! The application ODK Collect
(process
org.odk.collect.android) has stopped unexpectedly. Please try
again."
Any ideas what could be wrong? This seems to be the recommended
regex
anywhere I've looked and I can't find any reference to anyone else
having
this problem. Ironically if I leave out the constraint then 255
characters
can be entered but without the warning, my users frequently go over
(they
are a wordy lot) and have their answers chopped off in ODK Aggregate.
I've also tried this:
However then it requires exactly 255 characters for an answer.
We are using a mixture of Samsung Galaxy SI and SII phones with
Android
2.3.4 & 2.3.5 running ODK Collect 1.3 (1030) submitting to ODK
Aggregate
1.3.1 on Google's AppEngine.
Thanks for calling this to my attention. I've updated the documentation on
that page.
You only need to replace > with > and < with < in XML files.
Equals (=) is OK as is.
and < are reserved characters in XML and cannot be used directly.
Mitch
···
On Thu, May 23, 2013 at 7:41 AM, Greg Pommen wrote:
That seems to work, as long as I changed ' <= 255' to ' < 256 '.
FYI, the original regex I was using ' constraint="regex(.,
'^.{0,255}$')" ' was off the page: http://opendatakit.org/help/form-design/binding/ . Perhaps the 61 char
limitation needs to be mentioned on there in addition to changing any of
the references to the symbols <, >, or = to < > &eq; for all the
other examples too. Unless I'm missing something which is quite likely as
well.
Thank you for the idea, I'll see if it would help. I would still really
like to be able to set a limit within the form so I'll eagerly await the
bug fix too! BTW we have everything publishing to Google Fusion Tables or
Google Spreadsheets.
If you have a MySQL or PostgreSQL database, you should be able to ALTER
TABLE and increase the storage amount (but you won't be able to shrink it)
after-the-fact without updating your form (you just need to shut down and
restart ODK Aggregate to begin using the new string sizes).
Unfortunately, adding these storage size directives to a form is an
incompatible form change, necessitating a change in the formId, or a flush
and reload of ODK Aggregate via ODK Briefcase.
Hi,
In order to constrain the answers of users in my forms to under
255
characters I've been wanting to use a binding like this
However, putting in this regex constraint now seems to crash ODK
Collect if
anymore than 61 characters are entered in the field on the form. I
have no
idea what is magical about 61 characters but I've tested this
repeatedly on
multiple forms and 61 characters seems to be the limit.
The crash message is: "Sorry! The application ODK Collect
(process
org.odk.collect.android) has stopped unexpectedly. Please try
again."
Any ideas what could be wrong? This seems to be the recommended
regex
anywhere I've looked and I can't find any reference to anyone else
having
this problem. Ironically if I leave out the constraint then 255
characters
can be entered but without the warning, my users frequently go over
(they
are a wordy lot) and have their answers chopped off in ODK
Aggregate.
I've also tried this:
However then it requires exactly 255 characters for an answer.
We are using a mixture of Samsung Galaxy SI and SII phones with
Android
2.3.4 & 2.3.5 running ODK Collect 1.3 (1030) submitting to ODK
Aggregate
1.3.1 on Google's AppEngine.
That seems to work, as long as I changed ' <= 255' to ' < 256 '.
FYI, the original regex I was using ' constraint="regex(.,
'^.{0,255}$')" ' was off the page: http://opendatakit.org/help/form-design/binding/ . Perhaps the 61 char
limitation needs to be mentioned on there in addition to changing any of
the references to the symbols <, >, or = to < > &eq; for all the
other examples too. Unless I'm missing something which is quite likely as
well.
Thank you for the idea, I'll see if it would help. I would still
really like to be able to set a limit within the form so I'll eagerly await
the bug fix too! BTW we have everything publishing to Google Fusion Tables
or Google Spreadsheets.
If you have a MySQL or PostgreSQL database, you should be able to
ALTER TABLE and increase the storage amount (but you won't be able to
shrink it) after-the-fact without updating your form (you just need to shut
down and restart ODK Aggregate to begin using the new string sizes).
Unfortunately, adding these storage size directives to a form is an
incompatible form change, necessitating a change in the formId, or a flush
and reload of ODK Aggregate via ODK Briefcase.
Hi,
In order to constrain the answers of users in my forms to
under 255
characters I've been wanting to use a binding like this
However, putting in this regex constraint now seems to crash ODK
Collect if
anymore than 61 characters are entered in the field on the form.
I have no
idea what is magical about 61 characters but I've tested this
repeatedly on
multiple forms and 61 characters seems to be the limit.
The crash message is: "Sorry! The application ODK Collect
(process
org.odk.collect.android) has stopped unexpectedly. Please try
again."
Any ideas what could be wrong? This seems to be the
recommended regex
anywhere I've looked and I can't find any reference to anyone else
having
this problem. Ironically if I leave out the constraint then 255
characters
can be entered but without the warning, my users frequently go
over (they
are a wordy lot) and have their answers chopped off in ODK
Aggregate.
I've also tried this:
However then it requires exactly 255 characters for an answer.
We are using a mixture of Samsung Galaxy SI and SII phones with
Android
2.3.4 & 2.3.5 running ODK Collect 1.3 (1030) submitting to ODK
Aggregate
1.3.1 on Google's AppEngine.