Best practices for handling multiple CommCare application versions and branches

Hi Ray,

As you noticed we don’t have anything like a sophisticated version-tracking
or branching mechanism, but copying applications (either to other projects
or within the same project) should work as expected. Specifically, all
unique identifiers are regenerated so that what you end up with are two
independent apps, except that corresponding forms share the same xmlns.
This should be completely transparent, however, as the reports are able to
separate submissions based not only on the form xmlns, but also the
application.

Cheers,
Danny

··· On Tue, May 28, 2013 at 1:33 AM, Ray Brunsting wrote:

We have a growing need to maintain multiple versions of CommCare
applications, and would like to know of anyone has developed tools and/or
best-practices to help with this.

In the past, we copied and renamed CommCare applications between CommCare
projects; however, this is not a very elegant solution and I’m not certain
if it works as desired.

Example sequence of steps:

  1. Copy application ‘App V1’ from project ‘ProjectX’ to ‘ProjectY’
  2. Rename application in ‘ProjectY’ to ‘App V2’
  3. Copy renamed application from ‘ProjectY’ to ‘ProjectX’

It would be great to hear from others with a better solution, or at least
others who are successfully using the same basic steps.

One specific question, for Dimagi: are the application, form and other
key/unique identifiers automatically replaced by the application copy
command? (ie. so “App V1” and “App V2” end up as completely independent
applications)

Thanks, Ray


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/groups/opt_out.

Thanks Danny. Good to know that we can safely copy an application within a
single project as well. We’ll likely end up making copies both to other
projects and within the same project.

One related request: it would be great to have API access to the
formID/xmlns pairs associated with a specific appID. As things work now,
we need to manually determine 30+ formIDs to allow our custom application
builder to update a copied application. I believe someone else recently
asked about something similar in this forum.

Cheers, Ray

··· On Tuesday, May 28, 2013 9:23:35 AM UTC-4, Daniel Roberts wrote: > > Hi Ray, > > As you noticed we don't have anything like a sophisticated > version-tracking or branching mechanism, but copying applications (either > to other projects or within the same project) should work as expected. > Specifically, all unique identifiers are regenerated so that what you end > up with are two independent apps, except that corresponding forms share the > same xmlns. This should be completely transparent, however, as the reports > are able to separate submissions based not only on the form xmlns, but also > the application. > > Cheers, > Danny > > > On Tue, May 28, 2013 at 1:33 AM, Ray Brunsting <r...@tula.org wrote: > >> We have a growing need to maintain multiple versions of CommCare >> applications, and would like to know of anyone has developed tools and/or >> best-practices to help with this. >> >> In the past, we copied and renamed CommCare applications between CommCare >> projects; however, this is not a very elegant solution and I'm not certain >> if it works as desired. >> >> Example sequence of steps: >> >> 1. Copy application 'App V1' from project 'ProjectX' to 'ProjectY' >> 2. Rename application in 'ProjectY' to 'App V2' >> 3. Copy renamed application from 'ProjectY' to 'ProjectX' >> >> It would be great to hear from others with a better solution, or at least >> others who are successfully using the same basic steps. >> >> One specific question, for Dimagi: are the application, form and other >> key/unique identifiers automatically replaced by the application copy >> command? (ie. so "App V1" and "App V2" end up as completely independent >> applications) >> >> Thanks, Ray >> >> -- >> 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-user...@googlegroups.com . >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > >

Thanks Danny. Good to know that we can safely copy an application within
a single project as well. We’ll likely end up making copies both to other
projects and within the same project.

One related request: it would be great to have API access to the
formID/xmlns pairs associated with a specific appID. As things work now,
we need to manually determine 30+ formIDs to allow our custom application
builder to update a copied application. I believe someone else recently
asked about something similar in this forum.

Thanks Ray. This is indeed on our short term roadmap and we’ll update as
soon as we have more information about timing or release.

··· On Tue, May 28, 2013 at 4:19 PM, Ray Brunsting wrote:

Cheers, Ray

On Tuesday, May 28, 2013 9:23:35 AM UTC-4, Daniel Roberts wrote:

Hi Ray,

As you noticed we don’t have anything like a sophisticated
version-tracking or branching mechanism, but copying applications (either
to other projects or within the same project) should work as expected.
Specifically, all unique identifiers are regenerated so that what you end
up with are two independent apps, except that corresponding forms share the
same xmlns. This should be completely transparent, however, as the reports
are able to separate submissions based not only on the form xmlns, but also
the application.

Cheers,
Danny

On Tue, May 28, 2013 at 1:33 AM, Ray Brunsting r...@tula.org wrote:

We have a growing need to maintain multiple versions of CommCare
applications, and would like to know of anyone has developed tools and/or
best-practices to help with this.

In the past, we copied and renamed CommCare applications between
CommCare projects; however, this is not a very elegant solution and I’m not
certain if it works as desired.

Example sequence of steps:

  1. Copy application ‘App V1’ from project ‘ProjectX’ to ‘ProjectY’
  2. Rename application in ‘ProjectY’ to ‘App V2’
  3. Copy renamed application from ‘ProjectY’ to ‘ProjectX’

It would be great to hear from others with a better solution, or at
least others who are successfully using the same basic steps.

One specific question, for Dimagi: are the application, form and other
key/unique identifiers automatically replaced by the application copy
command? (ie. so “App V1” and “App V2” end up as completely independent
applications)

Thanks, Ray


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-user…@**googlegroups.com.

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


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/groups/opt_out.