Cases from one app showing up in export of second app

Hi all,

I have two nearly identical M+E apps within the same project space, one for
Cambodia and one for Uganda. The only difference (besides minor changes in
wording), is that Uganda has an additional form that we don’t use in
Cambodia. Cambodia was built first and then copied into a new app within
the same project space for Uganda.

I have two case exports set up, one for each app/country. When I export
Cambodia cases, I see only Cambodia cases. However, when I export Uganda
cases, I see both Cambodia and Uganda cases. Anyone have any insight into
why this is happening?

Thanks!
Jimi

Hi Jimi,

Case types are on a per project space basis, rather than per app. This
allows you to have multiple apps working with the same case data. If you
need to distinguish these two sets of cases then it might be easiest to set
a different case type in the app.

If you have already been collecting data then you would probably have to
filter the data after downloading based on something like the user that
created the case.

Hope this helps!

Jeremy

··· On Wed, Aug 31, 2016 at 5:15 PM, James Michiel wrote:

Hi all,

I have two nearly identical M+E apps within the same project space, one
for Cambodia and one for Uganda. The only difference (besides minor changes
in wording), is that Uganda has an additional form that we don’t use in
Cambodia. Cambodia was built first and then copied into a new app within
the same project space for Uganda.

I have two case exports set up, one for each app/country. When I export
Cambodia cases, I see only Cambodia cases. However, when I export Uganda
cases, I see both Cambodia and Uganda cases. Anyone have any insight into
why this is happening?

Thanks!
Jimi


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.


Jeremy Wacksman
Dimagi http://www.dimagi.com, Inc.