Typo in field path

Hi everyone,

We discovered a typo in a field name : /anc/vilage… This /anc/vilage is
stored in a case.

Users are already sending forms, however it is still a small scale
deployment for now, so :

  1. we still can reasonably fix each form / case by hand or by writing a
    python script and check each result
  2. it is okay if some data is lost (previous forms not compatible any
    more for example) as long as the village is right in the current cases

What could be the impact of renaming /anc/vilage to /anc/village
everywhere it is mentioned in our application ?

Many thanks,

··· -- Charles Flèche mHealth advisor Télécoms Sans Frontières http://www.tsfi.org Première Urgence - Aide Médicale Internationale http://www.pu-ami.org +95 9 431 978 25 Skype: charles.fleche

Hi Charles,

There wouldn’t be any major implications in the application as long as you
were diligent and made sure to fix every reference to the field. However,
when rolling out a new version of the app you would need to make sure that
you had cleaned all the cases or designed the app in a way to manage this.
There are two possible approaches you could take:

  1. Everywhere you need to read from the property, you could load both the
    "vilage" and “village” properties into the form and then use a logic
    expression to choose the right one. This might be tedious but should work
    and allow for a seamless migration.
  2. If you can control when the new version of the application goes out, you
    can collect all the phones, make sure they have all synced, and then use
    the case importer to populate the “village” property for all known cases.
    This will make building the application cleaner. FYI, case importer is a
    feature that requires a standard plan subscription

Whichever option you choose, one thing to also consider is that changing
the name in the forms could make data analysis from the exports more
challenging since you’ll have to combine different versions of the
application. Not sure if this is a concern or not but thought i’d mention
it.

cheers,
Cory

··· On Tue, Jul 8, 2014 at 9:31 AM, Charles Flèche wrote:

Hi everyone,

We discovered a typo in a field name : /anc/vilage… This /anc/vilage is
stored in a case.

Users are already sending forms, however it is still a small scale
deployment for now, so :

  1. we still can reasonably fix each form / case by hand or by writing a
    python script and check each result
  2. it is okay if some data is lost (previous forms not compatible any more
    for example) as long as the village is right in the current cases

What could be the impact of renaming /anc/vilage to /anc/village
everywhere it is mentioned in our application ?

Many thanks,

Charles Flèche
mHealth advisor
Télécoms Sans Frontières http://www.tsfi.org
Première Urgence - Aide Médicale Internationale http://www.pu-ami.org
+95 9 431 978 25
Skype: charles.fleche


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

Hi Cory,

··· On 08/07/2014 19:18, Cory Zue wrote: > There wouldn't be any major implications in the application as long as > you were diligent and made sure to fix every reference to the field.

Thanks the advice. I’ll just go ahead and rename the field. The few
cases we already have will be edited in our “edit” form as they come.

Thanks again,


Charles Flèche
mHealth advisor
Télécoms Sans Frontières http://www.tsfi.org
Première Urgence - Aide Médicale Internationale http://www.pu-ami.org
+95 9 431 978 25
Skype: charles.fleche