Row limit in choice list

Hi,

I am working with a form using choice filter. My 'choice' worksheet is
having around 8000 rows which is crashing odk collect when i tried to open
from mobile whereas if i reduce the rows to few hundred everything works
perfect. Is there any limit to rows in 'choices' worksheet ?? did anybody
encountered issues like this ?.

Thanks !.
Madhav

Madhav,

You are probably running out of memory. There are two options that I know
of:

  1. The Collect v1.14 release candidate has support for an "itemsets.csv"
    feature, with which you can load and filter options from a .csv file. I'm
    not sure whether that has been documented yet, but Yaw or somebody else
    might be able to provide help on using that.

  2. If you're using SurveyCTO, there is a dynamic search-and-select feature
    that likewise allows for choices to be dynamically loaded from .csv files.
    If you run a SurveyCTO server, you can find help on that at
    https://clientname.surveycto.com/main.html#Help_Forms_dynamic-selects(where
    you replace "clientname" with your client name).

Best,

Chris

··· On Thu, Aug 15, 2013 at 8:05 AM, Madhav wrote:

Hi,

I am working with a form using choice filter. My 'choice' worksheet is
having around 8000 rows which is crashing odk collect when i tried to open
from mobile whereas if i reduce the rows to few hundred everything works
perfect. Is there any limit to rows in 'choices' worksheet ?? did anybody
encountered issues like this ?.

Thanks !.
Madhav

--

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


You received this message because you are subscribed to the Google Groups
"ODK Community" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Thanks Chris !

I have tried it with two different mobiles having good memory but failed. I
prefer using ODK with Aggregate.

Thanx..
Madhav

Madhuv,

Counterintuitively, more device memory will generally not help with ODK
out-of-memory errors -- particular before v1.4. This is because Android
devices severely limit the memory available to any one app, regardless of
the overall amount of memory available. In v1.4, Collect will request more
memory from Android, and will generally be allowed more -- though how much
more will still depend on the manufacturer/device.

In any case, if you haven't tried the v1.4 release candidate, it's worth a
try. There's a small chance that it will allow enough memory for your 8,000
rows (though then it may still be unbearably slow).

Best,

Chris

P.S. Sorry for the typo earlier: the new v1.4 release candidate has the new
itemsets.csv feature, not the older v1.14 release.

··· On Thu, Aug 15, 2013 at 8:45 AM, Madhav wrote:

Thanks Chris !

I have tried it with two different mobiles having good memory but failed.
I prefer using ODK with Aggregate.

Thanx..
Madhav

--

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


You received this message because you are subscribed to the Google Groups
"ODK Community" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Yes Chris, you are right!

have tried with Collect 1.4, it is painfully slow to load the form. it took
approx 9 min to load the form itself. Hope to see better alternative. shed
some light on using itemsets and/or odk table.

appreciate your support!.

Regards,
Madhav.

··· On Thursday, August 15, 2013 3:53:13 PM UTC+3, Christopher Robert wrote:

Madhuv,

Counterintuitively, more device memory will generally not help with ODK
out-of-memory errors -- particular before v1.4. This is because Android
devices severely limit the memory available to any one app, regardless of
the overall amount of memory available. In v1.4, Collect will request more
memory from Android, and will generally be allowed more -- though how much
more will still depend on the manufacturer/device.

In any case, if you haven't tried the v1.4 release candidate, it's worth a
try. There's a small chance that it will allow enough memory for your 8,000
rows (though then it may still be unbearably slow).

Best,

Chris

P.S. Sorry for the typo earlier: the new v1.4 release candidate has the
new itemsets.csv feature, not the older v1.14 release.

On Thu, Aug 15, 2013 at 8:45 AM, Madhav <bblsu...@gmail.com <javascript:>>wrote:

Thanks Chris !

I have tried it with two different mobiles having good memory but failed.
I prefer using ODK with Aggregate.

Thanx..
Madhav

--

Post: opend...@googlegroups.com <javascript:>
Unsubscribe: opendatakit...@googlegroups.com <javascript:>
Options: http://groups.google.com/group/opendatakit?hl=en


You received this message because you are subscribed to the Google Groups
"ODK Community" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.