Updated ODK Tools Released (versions 1.3 and 2.0 alpha)

[W_Brunette]

The ODK Team is pleased to announce a new release that includes many new
exciting features such as the ability to have Collect use an external
Bluetooth printer. This release includes bug fixes and new features for
the 1.3 version of the tools as well as an introduction of some of the ODK
2.0 tool set. The goal is to include some of the functionality from 2.0
series in the 1.0 series of tools when practicable. Here is a summary of
the changes:

Collect 1.3

• Added printer support on Android 3.1 and higher systems. See
  http://opendatakit.org/help/form-design/examples/#printing_widgets and
  http://opendatakit.org/use/sensors-framework/zebra-printer-driver/
• configurable display and use of 'back' and 'next' buttons, and the
  enabling or disabling of swipe treatment within form pages (contributed
  work by Nafundi).
• configurable background transmission of submissions when network
  connections are detected (contributed work by Nafundi).
• application settings can now be saved to disk and loaded from disk
  (makes configuring device fleets easier). (contributed work by Nafundi).
• issue 401 - string prompts now can render a configurable-height text
  entry box, via the rows attribute on their tag.
• issue 751 - compact (a.k.a. grid view) select-one and select-multiple
  prompts now can render text label arrays or icon arrays.
• compact (a.k.a. grid view) select-one and select-multiple prompts, if
  given a fixed column width (e.g., compact-4), will rescale the images so
  that they exactly fit the natural width of the device. Images are not
  rescaled when the device is then rotated 90 degrees.
• if a meta/instanceName field is defined in a form, the non-empty value
  of that field will be used as the instanceName when the form is saved (and
  the user will be unable to alter it). Otherwise, the pre-1.3 instance
  naming treatment will be used. By defining this as a calculated field, the
  form designer can control the naming of the submission instances.
• if itext contains constraintMsg or requiredMsg forms, then these will
  be used for the constraint failure and required-but-missing error messages.

···

* Aggregate 1.3.1*

• Improved Fusion Tables publisher that will batch submissions to move
  the data to Fusion Tables much faster (a reduction in speed occurred when
  Aggregate 1.3 moved away from Fusion Tables deprecated API to Fusion Tables
  API v1).
• Automatically create a Fusion Tables View that includes all
  first-level repeats.
• change watchdog to run more frequently if there is an active
  publisher. Provide a 'disable' button on the Site Admin / Preferences page
  to restore older behavior (to conserve GAE quota).
• issue 794 - form upload failed for some forms on MySQL with stack
  exhaustion.
• issue 761 - Fix to simple JSON publisher. had caused instability when
  used.
• issue 697 - popups don't show centered in screen when displayed on top
  of scrolling regions.
• issue 786 - forms with repeat groups cannot be versioned.
• issue 768 - rows-per-page value keeps getting reset on refresh..

Sensors Framework 2.0 ALPHA

• Initial ALPHA release
• The Sensors framework simplifies the development of sensor-based
  mobile applications by creating a common abstraction point that enables all
  sensors to be accessed through a unified interface. To access an external
  sensor you need a driver (such as Zebra Printer Driver) for the external
  device.

Zebra Printer Driver 2.0

• Tested on Zebra MZ220 and Zebra MZ320 printers.
• For installation and configuration please see:
  http://opendatakit.org/use/sensors-framework/zebra-printer-driver/
• For usage please see:
  http://opendatakit.org/help/form-design/examples/#printing_widgets

[Martin_Friedrich1]

Hi, great work and thanks to the Team for great ODK.

A question to the new functions listed in the "official Play Store": under
the Point # Widgets there is a point: "Launch external app". What does it
mean? Is it now poosible to start a webapp via hyperlink or something like
that. I found the point in the play store but not in the release notes. For
the printing thing, I found the widget, but not for "Launch external app".

Regards

Martin

···

Am Samstag, 13. April 2013 00:57:07 UTC+2 schrieb Waylon Brunette: > > The ODK Team is pleased to announce a new release that includes many new > exciting features such as the ability to have Collect use an external > Bluetooth printer. This release includes bug fixes and new features for > the 1.3 version of the tools as well as an introduction of some of the ODK > 2.0 tool set. The goal is to include some of the functionality from 2.0 > series in the 1.0 series of tools when practicable. Here is a summary of > the changes: > > *Collect 1.3* > > > - Added printer support on Android 3.1 and higher systems. See > http://opendatakit.org/help/form-design/examples/#printing_widgets and > http://opendatakit.org/use/sensors-framework/zebra-printer-driver/ > - configurable display and use of 'back' and 'next' buttons, and the > enabling or disabling of swipe treatment within form pages (contributed > work by Nafundi). > - configurable background transmission of submissions when network > connections are detected (contributed work by Nafundi). > - application settings can now be saved to disk and loaded from disk > (makes configuring device fleets easier). (contributed work by Nafundi). > - issue 401 - string prompts now can render a configurable-height text > entry box, via the rows attribute on their tag. > - issue 751 - compact (a.k.a. grid view) select-one and > select-multiple prompts now can render text label arrays or icon arrays. > - compact (a.k.a. grid view) select-one and select-multiple prompts, > if given a fixed column width (e.g., compact-4), will rescale the images so > that they exactly fit the natural width of the device. Images are not > rescaled when the device is then rotated 90 degrees. > - if a meta/instanceName field is defined in a form, the non-empty > value of that field will be used as the instanceName when the form is saved > (and the user will be unable to alter it). Otherwise, the pre-1.3 instance > naming treatment will be used. By defining this as a calculated field, the > form designer can control the naming of the submission instances. > - if itext contains constraintMsg or requiredMsg forms, then these > will be used for the constraint failure and required-but-missing error > messages. > > * > Aggregate 1.3.1* > > > - Improved Fusion Tables publisher that will batch submissions to > move the data to Fusion Tables much faster (a reduction in speed occurred > when Aggregate 1.3 moved away from Fusion Tables deprecated API to Fusion > Tables API v1). > - Automatically create a Fusion Tables View that includes all > first-level repeats. > - change watchdog to run more frequently if there is an active > publisher. Provide a 'disable' button on the Site Admin / Preferences page > to restore older behavior (to conserve GAE quota). > - issue 794 - form upload failed for some forms on MySQL with stack > exhaustion. > - issue 761 - Fix to simple JSON publisher. had caused instability > when used. > - issue 697 - popups don't show centered in screen when displayed on > top of scrolling regions. > - issue 786 - forms with repeat groups cannot be versioned. > - issue 768 - rows-per-page value keeps getting reset on refresh.. > > > *Sensors Framework 2.0 ALPHA* > > > - Initial ALPHA release > - The Sensors framework simplifies the development of sensor-based > mobile applications by creating a common abstraction point that enables all > sensors to be accessed through a unified interface. To access an external > sensor you need a driver (such as Zebra Printer Driver) for the external > device. > > > *Zebra Printer Driver 2.0* > > > - Tested on Zebra MZ220 and Zebra MZ320 printers. > - For installation and configuration please see: > http://opendatakit.org/use/sensors-framework/zebra-printer-driver/ > - For usage please see: > http://opendatakit.org/help/form-design/examples/#printing_widgets > >

[Daniel_Bridges]

Congratulations to the team and many thanks for all your hard work.

I know it has only just been released, but are there any example forms you
can share to showcase how to use the new features in Collect?

[Nik_Go]

You'll usually find the features supported by the most current version
here: http://opendatakit.org/help/form-design/examples

···

On Monday, April 15, 2013, dj_bridges wrote:

Congratulations to the team and many thanks for all your hard work.

I know it has only just been released, but are there any example forms you
can share to showcase how to use the new features in Collect?

--

Post: opendatakit@googlegroups.com <javascript:_e({}, 'cvml',
'opendatakit@googlegroups.com');>
Unsubscribe: opendatakit+unsubscribe@googlegroups.com <javascript:_e({},
'cvml', 'opendatakit%2Bunsubscribe@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 <javascript:_e({},
'cvml', 'opendatakit%2Bunsubscribe@googlegroups.com');>.
For more options, visit https://groups.google.com/groups/opt_out.

[Mitch_S]

The list of 'new features' on Google Play is only slowly revised, so it may
refer to features from earlier releases.

In this case, the 'launch external app' functionality was available as of
1.2.

We retain earlier feature bullet points in the Google Play blurb in case
random people discover the tool through a search. And we remove earlier
features from the list only because there is a 500-character limit.

The latest changes for a specific release are always identified in the
release notes.

···

On Mon, Apr 15, 2013 at 4:35 AM, ゴー・ニコライ wrote:

You'll usually find the features supported by the most current version
here: http://opendatakit.org/help/form-design/examples

On Monday, April 15, 2013, dj_bridges wrote:

Congratulations to the team and many thanks for all your hard work.

I know it has only just been released, but are there any example forms
you can share to showcase how to use the new features in Collect?

--

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.

--

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.

--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com

[Daniel_Bridges]

I have been combing the website for a couple of days, but so far I can't
see any guides or examples on the new features. Am sure others are
interested in them all, but the killer features for me are:

• configurable display and use of 'back' and 'next' buttons, and the
  enabling or disabling of swipe treatment within form pages (contributed
  work by Nafundi).
• application settings can now be saved to disk and loaded from disk
  (makes configuring device fleets easier). (contributed work by Nafundi).
• if a meta/instanceName field is defined in a form, the non-empty value
  of that field will be used as the instanceName when the form is saved (and
  the user will be unable to alter it). Otherwise, the pre-1.3 instance
  naming treatment will be used. By defining this as a calculated field, the
  form designer can control the naming of the submission instances.
• if itext contains constraintMsg or requiredMsg forms, then these will
  be used for the constraint failure and required-but-missing error messages.

Perhaps I have missed something?

[yanokwa]

Daniel,

The core team has a ton of other stuff to do and I'm assuming they are
counting on the community to help with documentation.

I'll go first by writing up a blog post discussing some of the new
features in a day or so. I'll send out an email when that post goes
out.

Anyone else interested in helping?

Yaw

···

-- Need ODK help? Go to http://nafundi.com for custom development, form design, implementation support, and user training for ODK.

On Wed, Apr 17, 2013 at 6:37 AM, dj_bridges danieljbridges@gmail.com wrote:

I have been combing the website for a couple of days, but so far I can't see
any guides or examples on the new features. Am sure others are interested in
them all, but the killer features for me are:

configurable display and use of 'back' and 'next' buttons, and the enabling
or disabling of swipe treatment within form pages (contributed work by
Nafundi).
application settings can now be saved to disk and loaded from disk (makes
configuring device fleets easier). (contributed work by Nafundi).
if a meta/instanceName field is defined in a form, the non-empty value of
that field will be used as the instanceName when the form is saved (and the
user will be unable to alter it). Otherwise, the pre-1.3 instance naming
treatment will be used. By defining this as a calculated field, the form
designer can control the naming of the submission instances.
if itext contains constraintMsg or requiredMsg forms, then these will be
used for the constraint failure and required-but-missing error messages.

Perhaps I have missed something?

--

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.

[Mitch_S]

Whenever you see 'configurable', look in the 'Change Settings' or 'Admin
Settings' on the app.

For back/next, see 'Change Settings' / 'Navigation'.
For saving settings to disk, see 'Admin Settings' -- Menu -- 'Save to
Disk'

We'll have to wait for Yaw's blog post for info on what is saved and how to
restore/apply the saved settings.

I thought the last 2 were self-explanatory. Just like when you define a
meta/instanceID field ( http://opendatakit.org/help/form-design/ ), if you
also define a meta/instanceName field, then it will be used in the manner
described.

And for the itext, if you define an itext form of 'constraintMsg' or
'requiredMsg', then that will be used for those messages. I believe these
are now recognized by XLSForm (but haven't checked).

Attached is an example form with the last 2 features.

customErrorStrings.xml (2.57 KB)

···

On Wed, Apr 17, 2013 at 8:24 AM, Yaw Anokwa wrote:

Daniel,

The core team has a ton of other stuff to do and I'm assuming they are
counting on the community to help with documentation.

I'll go first by writing up a blog post discussing some of the new
features in a day or so. I'll send out an email when that post goes
out.

Anyone else interested in helping?

Yaw

Need ODK help? Go to http://nafundi.com for custom development, form
design, implementation support, and user training for ODK.

On Wed, Apr 17, 2013 at 6:37 AM, dj_bridges danieljbridges@gmail.com wrote:

I have been combing the website for a couple of days, but so far I can't
see
any guides or examples on the new features. Am sure others are
interested in
them all, but the killer features for me are:

configurable display and use of 'back' and 'next' buttons, and the
enabling
or disabling of swipe treatment within form pages (contributed work by
Nafundi).
application settings can now be saved to disk and loaded from disk (makes
configuring device fleets easier). (contributed work by Nafundi).
if a meta/instanceName field is defined in a form, the non-empty value of
that field will be used as the instanceName when the form is saved (and
the
user will be unable to alter it). Otherwise, the pre-1.3 instance naming
treatment will be used. By defining this as a calculated field, the form
designer can control the naming of the submission instances.
if itext contains constraintMsg or requiredMsg forms, then these will be
used for the constraint failure and required-but-missing error messages.

Perhaps I have missed something?

--

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.

--

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.

--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com

[Daniel_Bridges]

Sorry if my message didn't come across too well - I do really appreciate
all the hard work the core team has done!

Thanks for the comments everyone - I just needed a little hint in the right
direction. Everything is working really well now....

[crobert]

All,

I have written a few help topics for a few of the new features. I'll paste
them below, in case they're helpful.

I have to admit, though, that I am struggling a bit with how to test the
auto-send features (i.e., the background transmission). We may have broken
them when we merged the code, or I may just not understand how they are
meant to operate. Yaw, we might need help from you on at least how the
features should be working.

In any case, here are the help topics I promised:

How can I prevent users from changing settings or taking other actions?
Once you have configured Collect the way you want it, you may want to
restrict the actions that users can take when they use Collect to fill out
surveys. Most commonly, you may want to prevent users from changing certain
settings.

To control what users can and cannot do, press your device's Menu button
from the main Collect menu, then choose Admin Settings. From there, the
first thing you can do is set an Admin Password to restrict who can alter
the overall administrative settings.

Below the password setting, you will find a series of checkboxes with which
you can control the following:

1. Which main menu options will appear to users. You might, for example,
   disable the option to delete saved forms.

2. Which settings users can modify. You might, for example, disable all
   settings except those having to do with navigation or font size.

3. Which options are available to users when they are filling out forms.
   You might, for example, prevent users from using the "Go To Prompt" option
   to jump forward or backward in the survey.

As soon as you change the administrative settings, you can review the
changes by going back to the main menu, to the General Settings, or to fill
out a form. You can change the access settings at any time by simply going
back into Admin Settings (and supplying the password, if you set one).

How can I copy Collect's settings from one device to another?
Once you have configured Collect the way you want it on one device, you may
want to copy those settings to other devices (so that you don't have to
manually enter all of the settings on every device). You can do this by
following these steps:

1. Save your desired settings to a file. Press your device's Menu button
   from the main Collect menu, then choose *Admin Settings *and enter your
   admin password (if any). Then, click your device's Menu button again and
   select Save Settings to Disk. That will save all of your current
   settings to the /odk/settings/collect.settings file on your device's SD
   card.

2. Copy that collect.settings file off to your computer or another
   location. (How you access the SD card and copy its files will depend on the
   device.)

3. Once you have installed ODK Collect onto another device and run it at
   least once, locate the /odk directory on its SD card.

4. Copy the collect.settings file into the device's existing /odk
   directory.

5. Run ODK Collect on the device and confirm that it has loaded all of
   your settings.

You can repeat this process to copy the same configuration to all of your
devices. That way, you are sure that they are all configured in exactly the
same way.

How do I automatically generate unique names for saved forms? (presumes
using XLSForm)
By default, whenever a new form is filled out, it is named the same thing:
the title of the form. Unless users override this default and enter a
different name when they save each form, the Edit Saved Form, Send
Finalized Form, and Delete Saved Form lists in ODK Collect will show
lots of forms all with the same name; the only way to distingsuish them
will be to click on each one to see its contents.

Alternatively, you can automatically name each form in a way that utilizes
the data entered into the form. For example, you might include a unique
household ID and/or a respondent name in the name of the form. To do this,
you need to specify an instance_name setting in your form's settings
worksheet.

Start by adding a new column to your form's settings worksheet, and
entering "instance_name" into the first row of the new column.

Then, in the second row of that new column, add an expression like the
following:

concat('HH SURVEY - ', ${hhid})

Replace "HH SURVEY" with whatever prefix you want to include in form names,
and replace "hhid" with whatever field name contains a unique identifier
for the form. Alternatively, if you want to include multiple fields, you
could enter an expression like this:

concat('HH SURVEY - ID ', ${hhid}, ' - Name ', ${respondent_name})

In this example, both a household ID and a respondent name are included in
the form's name. That way, when you list filled-out forms on a device, you
will be able to more easily find specific instances.

Using variations of the concat() function, you can concatenate together an
arbitrary number of literal strings (enclosed by single-quotes) and an
arbitrary number of form fields (enclosed by ${...}).

Hope that's helpful,

Chris

···

On Thu, Apr 18, 2013 at 11:40 AM, dj_bridges wrote:

Sorry if my message didn't come across too well - I do really appreciate
all the hard work the core team has done!

Thanks for the comments everyone - I just needed a little hint in the
right direction. Everything is working really well now....

--

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.

[Daniel_Bridges]

Very helpful - thanks Chris!

[Syed_Muhammad_Qadeer]

All,

I have written a few help topics for a few of the new features. I'll paste them below, in case they're helpful.

I have to admit, though, that I am struggling a bit with how to test the auto-send features (i.e., the background transmission). We may have broken them when we merged the code, or I may just not understand how they are meant to operate. Yaw, we might need help from you on at least how the features should be working.

In any case, here are the help topics I promised:

How can I prevent users from changing settings or taking other actions?Once you have configured Collect the way you want it, you may want to restrict the actions that users can take when they use Collect to fill out surveys. Most commonly, you may want to prevent users from changing certain settings.

To control what users can and cannot do, press your device's Menu button from the main Collect menu, then choose Admin Settings. From there, the first thing you can do is set an Admin Password to restrict who can alter the overall administrative settings.

Below the password setting, you will find a series of checkboxes with which you can control the following:
Which main menu options will appear to users. You might, for example, disable the option to delete saved forms.

Which settings users can modify. You might, for example, disable all settings except those having to do with navigation or font size.
Which options are available to users when they are filling out forms. You might, for example, prevent users from using the "Go To Prompt" option to jump forward or backward in the survey.

As soon as you change the administrative settings, you can review the changes by going back to the main menu, to the General Settings, or to fill out a form. You can change the access settings at any time by simply going back into Admin Settings (and supplying the password, if you set one).

How can I copy Collect's settings from one device to another?

Once you have configured Collect the way you want it on one device, you may want to copy those settings to other devices (so that you don't have to manually enter all of the settings on every device). You can do this by following these steps:

Save your desired settings to a file. Press your device's Menu button from the main Collect menu, then choose Admin Settings and enter your admin password (if any). Then, click your device's Menu button again and select Save Settings to Disk. That will save all of your current settings to the /odk/settings/collect.settings file on your device's SD card.

Copy that collect.settings file off to your computer or another location. (How you access the SD card and copy its files will depend on the device.)
Once you have installed ODK Collect onto another device and run it at least once, locate the /odk directory on its SD card.

Copy the collect.settings file into the device's existing /odk directory.
Run ODK Collect on the device and confirm that it has loaded all of your settings.

You can repeat this process to copy the same configuration to all of your devices. That way, you are sure that they are all configured in exactly the same way.

How do I automatically generate unique names for saved forms? (presumes using XLSForm)By default, whenever a new form is filled out, it is named the same thing: the title of the form. Unless users override this default and enter a different name when they save each form, the Edit Saved Form, Send Finalized Form, and Delete Saved Form lists in ODK Collect will show lots of forms all with the same name; the only way to distingsuish them will be to click on each one to see its contents.

Alternatively, you can automatically name each form in a way that utilizes the data entered into the form. For example, you might include a unique household ID and/or a respondent name in the name of the form. To do this, you need to specify an instance_name setting in your form's settings worksheet.

Start by adding a new column to your form's settings worksheet, and entering "instance_name" into the first row of the new column.
Then, in the second row of that new column, add an expression like the following:

concat('HH SURVEY - ', ${hhid})
Replace "HH SURVEY" with whatever prefix you want to include in form names, and replace "hhid" with whatever field name contains a unique identifier for the form. Alternatively, if you want to include multiple fields, you could enter an expression like this:

concat('HH SURVEY - ID ', ${hhid}, ' - Name ', ${respondent_name})
In this example, both a household ID and a respondent name are included in the form's name. That way, when you list filled-out forms on a device, you will be able to more easily find specific instances.

Using variations of the concat() function, you can concatenate together an arbitrary number of literal strings (enclosed by single-quotes) and an arbitrary number of form fields (enclosed by ${...}).

Hope that's helpful,

Chris

Sorry if my message didn't come across too well - I do really appreciate all the hard work the core team has done!

Thanks for the comments everyone - I just needed a little hint in the right direction. Everything is working really well now....

--

--

Post: opend...@googlegroups.com

Unsubscribe: opendatakit...@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...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

Dear, It apaprears that saving settings and transfering to other devices is not working in ODK Collect V 1.4.7. I have tried on many devices but no success. Can you kindly confirm if that function is not available anymore?

Best Regards

···

On Saturday, April 20, 2013 at 2:50:58 PM UTC+5, Christopher Robert wrote: > On Thu, Apr 18, 2013 at 11:40 AM, dj_bridges wrote:

[yanokwa]

Hi there,

This works great for me on the trunk build (1.4.10), and I don't think
the code has been touched since 1.4.7.

Are you copying the collect.settings file from
/odk/settings/collect.settings to /odk/collect.settings. Note that you
have to move it from the settings folder to outside the settings
folder for it to work.

Thanks,

Yaw

···

-- Need ODK consultants? Nafundi provides form design, server setup, in-field training, and software development for ODK. Go to https://nafundi.com to get started.

On Sat, Apr 2, 2016 at 6:00 PM, plannerqadeer@gmail.com wrote:

Dear, It apaprears that saving settings and transfering to other devices is not working in ODK Collect V 1.4.7. I have tried on many devices but no success. Can you kindly confirm if that function is not available anymore?

[Syed_Muhammad_Qadeer]

Thanks a lot. I will copy the file outside the settings folder.

Best Regards

···

On Tue, May 3, 2016 at 3:53 PM, Yaw Anokwa wrote:

Hi there,

This works great for me on the trunk build (1.4.10), and I don't think
the code has been touched since 1.4.7.

Are you copying the collect.settings file from
/odk/settings/collect.settings to /odk/collect.settings. Note that you
have to move it from the settings folder to outside the settings
folder for it to work.

Thanks,

Yaw

Need ODK consultants? Nafundi provides form design, server setup,
in-field training, and software development for ODK. Go to
https://nafundi.com to get started.

On Sat, Apr 2, 2016 at 6:00 PM, plannerqadeer@gmail.com wrote:

Dear, It apaprears that saving settings and transfering to other devices
is not working in ODK Collect V 1.4.7. I have tried on many devices but no
success. Can you kindly confirm if that function is not available anymore?

--

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 a topic in the
Google Groups "ODK Community" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/opendatakit/XJu6eLvcZkw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
opendatakit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.