Numbers in Multi-Select and occurring problems

Hi,

even though we read the documentation and knew that Multi-Select only
supports Strings, we tried to build a form with numbers ("decimal") as
values in Multi-Selection fields.

Example Code:

Defoliation

Select a value

1
1


2
2

The problems that occur are that the values are stored correctly as
numbers when we select only one field and submit the form to our ODK
Aggregate 1.0. So they are wrongly being handled as single select
fields.
But when we select more than one field the submission fails with an
"500 Internal Server Error".
A look at the PostgrSQL database and tables showed Aggregate didn't
create a table for the Multi-Select field.

Maybe it would be better to warn users when they upload a form with
"decimal" Multi-Select fields to ODK Aggregate webpage.
Because of the successful upload of the form to Aggregate and download
to Collect, we thought the values would only be converted to Strings,
but stay usable.

Has anybody else experienced this problem and could present his "work
around" to fill Multi-Selects with numbers?

Regards.

(Our setup: ODK Aggregate 1.0 (Production) on Tomcat with PostgreSQL)

You need a <bind type="select" .../> to use a multi-select field.

Mitch

··· On Thu, Nov 3, 2011 at 8:21 AM, LETSGO CeLeKT wrote:

Hi,

even though we read the documentation and knew that Multi-Select only
supports Strings, we tried to build a form with numbers ("decimal") as
values in Multi-Selection fields.

Example Code:

Defoliation

Select a value

1
1


2
2

The problems that occur are that the values are stored correctly as
numbers when we select only one field and submit the form to our ODK
Aggregate 1.0. So they are wrongly being handled as single select
fields.
But when we select more than one field the submission fails with an
"500 Internal Server Error".
A look at the PostgrSQL database and tables showed Aggregate didn't
create a table for the Multi-Select field.

Maybe it would be better to warn users when they upload a form with
"decimal" Multi-Select fields to ODK Aggregate webpage.
Because of the successful upload of the form to Aggregate and download
to Collect, we thought the values would only be converted to Strings,
but stay usable.

Has anybody else experienced this problem and could present his "work
around" to fill Multi-Selects with numbers?

Regards.

(Our setup: ODK Aggregate 1.0 (Production) on Tomcat with PostgreSQL)

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Mitch Sundt
Software Engineer


University of Washington
mitchellsundt@gmail.com

Thank you.
Now it works as expected!

Do you know whether there will be a real numeric multi-select in
future versions?

··· On Nov 3, 6:25 pm, Mitch Sundt wrote: > You need a to use a multi-select field. > > Mitch > > On Thu, Nov 3, 2011 at 8:21 AM, LETSGO CeLeKT wrote: > > > > > > > > > > > Hi, > > > even though we read the documentation and knew that Multi-Select only > > supports Strings, we tried to build a form with numbers ("decimal") as > > values in Multi-Selection fields. > > > Example Code: > > > > > Defoliation > > > > Select a value > > > > 1 > > 1 > > > > > > 2 > > 2 > > > > > > > The problems that occur are that the values are stored correctly as > > numbers when we select only one field and submit the form to our ODK > > Aggregate 1.0. So they are wrongly being handled as single select > > fields. > > But when we select more than one field the submission fails with an > > "500 Internal Server Error". > > A look at the PostgrSQL database and tables showed Aggregate didn't > > create a table for the Multi-Select field. > > > Maybe it would be better to warn users when they upload a form with > > "decimal" Multi-Select fields to ODK Aggregate webpage. > > Because of the successful upload of the form to Aggregate and download > > to Collect, we thought the values would only be converted to Strings, > > but stay usable. > > > Has anybody else experienced this problem and could present his "work > > around" to fill Multi-Selects with numbers? > > > Regards. > > > (Our setup: ODK Aggregate 1.0 (Production) on Tomcat with PostgreSQL) > > > -- > > Post: opendatakit@googlegroups.com > > Unsubscribe: opendatakit+unsubscribe@googlegroups.com > > Options:http://groups.google.com/group/opendatakit?hl=en > > -- > Mitch Sundt > Software Engineerhttp://www.OpenDataKit.org > University of Washington > mitchellsu...@gmail.com

it's unlikely there will be a typed multi-select in the future, but
feel free to file a feature request and we'll forward it on to the
javarosa community.

··· On Fri, Nov 4, 2011 at 12:13, LETSGO CeLeKT wrote: > Thank you. > Now it works as expected! > > Do you know whether there will be a real numeric multi-select in > future versions? > > > > On Nov 3, 6:25 pm, Mitch Sundt wrote: >> You need a to use a multi-select field. >> >> Mitch >> >> On Thu, Nov 3, 2011 at 8:21 AM, LETSGO CeLeKT wrote: >> >> >> >> >> >> >> >> >> >> > Hi, >> >> > even though we read the documentation and knew that Multi-Select only >> > supports Strings, we tried to build a form with numbers ("decimal") as >> > values in Multi-Selection fields. >> >> > Example Code: >> > >> >> > Defoliation >> > >> > Select a value >> > >> > 1 >> > 1 >> > >> > >> > 2 >> > 2 >> > >> > >> >> > The problems that occur are that the values are stored correctly as >> > numbers when we select only one field and submit the form to our ODK >> > Aggregate 1.0. So they are wrongly being handled as single select >> > fields. >> > But when we select more than one field the submission fails with an >> > "500 Internal Server Error". >> > A look at the PostgrSQL database and tables showed Aggregate didn't >> > create a table for the Multi-Select field. >> >> > Maybe it would be better to warn users when they upload a form with >> > "decimal" Multi-Select fields to ODK Aggregate webpage. >> > Because of the successful upload of the form to Aggregate and download >> > to Collect, we thought the values would only be converted to Strings, >> > but stay usable. >> >> > Has anybody else experienced this problem and could present his "work >> > around" to fill Multi-Selects with numbers? >> >> > Regards. >> >> > (Our setup: ODK Aggregate 1.0 (Production) on Tomcat with PostgreSQL) >> >> > -- >> > Post: opendatakit@googlegroups.com >> > Unsubscribe: opendatakit+unsubscribe@googlegroups.com >> > Options:http://groups.google.com/group/opendatakit?hl=en >> >> -- >> Mitch Sundt >> Software Engineerhttp://www.OpenDataKit.org >> University of Washington >> mitchellsu...@gmail.com > > -- > Post: opendatakit@googlegroups.com > Unsubscribe: opendatakit+unsubscribe@googlegroups.com > Options: http://groups.google.com/group/opendatakit?hl=en >

is it possible to have a multi-select option and integer field next to it???
For example:

  1. 300ml Enter Value=_____
  2. 500ml Enter Value=_____
  3. 1litre Enter Value=_____