We initially chose to set the* external ID to match the orignal value of
the patient ID *case property. Later we found that there are some
scenarios (more than expected) where the CHWs needs to later change/correct
the patient ID. While we can/will allow the CHW to use an 'update' form to
change the patient ID, I don't know if (or how) the external ID can be
changed to match the new patient ID case property.
So, two questions:
1 - Is it possible to change the external ID associate with a case?
2 - If "no", is it possible and reasonable to not specify any external ID?
There's currently no way to change the case name or the external id in an
app whose cases are configured in CommCare HQ. This is due to a bug in the
user interface. It will be fixed in the next revision, but will only be
available for use on CommCare 2.0 applications. I'd say your best choice
for now may be to just use patient ID instead of external ID until we
finish the 2.0 app builder and you're ready to move to 2.0.
Cheers,
Danny
···
2012/4/4 Ray Brunsting
We initially chose to set the* external ID to match the orignal value of
the patient ID *case property. Later we found that there are some
scenarios (more than expected) where the CHWs needs to later change/correct
the patient ID. While we can/will allow the CHW to use an 'update' form to
change the patient ID, I don't know if (or how) the external ID can be
changed to match the new patient ID case property.
So, two questions:
1 - Is it possible to change the external ID associate with a case?
2 - If "no", is it possible and reasonable to not specify any external ID?
To answer your second question more explicitly, there's no reason to favor
using external id over any other property, we had plans to index or
otherwise use it for common operations, but have decided to deprecate it as
an explicit field in 2.0, so using a patient-id field would work fine.
-Clayton
···
On Wed, Apr 4, 2012 at 11:55 AM, Daniel Roberts wrote:
Hi Ray,
There's currently no way to change the case name or the external id in an
app whose cases are configured in CommCare HQ. This is due to a bug in the
user interface. It will be fixed in the next revision, but will only be
available for use on CommCare 2.0 applications. I'd say your best choice
for now may be to just use patient ID instead of external ID until we
finish the 2.0 app builder and you're ready to move to 2.0.
We initially chose to set the* external ID to match the orignal value
of the patient ID *case property. Later we found that there are some
scenarios (more than expected) where the CHWs needs to later change/correct
the patient ID. While we can/will allow the CHW to use an 'update' form to
change the patient ID, I don't know if (or how) the external ID can be
changed to match the new patient ID case property.
So, two questions:
1 - Is it possible to change the external ID associate with a case?
2 - If "no", is it possible and reasonable to not specify any external ID?
Danny, Clayton, thanks for your feedback. We'll stop using the
external-id, and no longer be concerned about it being out-of-sync with the
patient id.
Two follow-up questions:
1 - Is it possible to change the case_name associate with a case?
2 - If "no", is it possible and reasonable to not specify any case_name?
(we have used the original patient name as the case_name, and have found
that it also changes quite a bit ... more than the patient id/external id)
Ray
···
On Wednesday, April 4, 2012 5:27:53 PM UTC-4, Clayton Sims wrote:
>
> To answer your second question more explicitly, there's no reason to favor
> using external id over any other property, we had plans to index or
> otherwise use it for common operations, but have decided to deprecate it as
> an explicit field in 2.0, so using a patient-id field would work fine.
>
> -Clayton
>
> On Wed, Apr 4, 2012 at 11:55 AM, Daniel Roberts wrote:
>
>> Hi Ray,
>>
>> There's currently no way to change the case name or the external id in an
>> app whose cases are configured in CommCare HQ. This is due to a bug in the
>> user interface. It will be fixed in the next revision, but will only be
>> available for use on CommCare 2.0 applications. I'd say your best choice
>> for now may be to just use patient ID instead of external ID until we
>> finish the 2.0 app builder and you're ready to move to 2.0.
>>
>> Cheers,
>> Danny
>>
>>
>> 2012/4/4 Ray Brunsting
>>
>>> We initially chose to set the* external ID t*o match the orignal value
>>> of the* patient ID *case property. Later we found that there are some
>>> scenarios (more than expected) where the CHWs needs to later change/correct
>>> the patient ID. While we can/will allow the CHW to use an 'update' form to
>>> change the patient ID, I don't know if (or how) the external ID can be
>>> changed to match the new patient ID case property.
>>>
>>> So, two questions:
>>> 1 - Is it possible to change the external ID associate with a case?
>>> 2 - If "no", is it possible and reasonable to not specify any external
>>> ID?
>>>
>>> Thanks, Ray
>>>
>>
>>
>
You should be able to update the case name by setting the "case_name"
property in 1.3 and above. It's useful to have a case name set for each
case for reporting purposes, so we have something to display for the cases.
Otherwise it is difficult to keep track of them.
-Clayton
···
On Thu, Apr 5, 2012 at 10:56 AM, Ray Brunsting wrote:
Danny, Clayton, thanks for your feedback. We'll stop using the
external-id, and no longer be concerned about it being out-of-sync with the
patient id.
Two follow-up questions:
1 - Is it possible to change the case_name associate with a case?
2 - If "no", is it possible and reasonable to not specify any case_name?
(we have used the original patient name as the case_name, and have found
that it also changes quite a bit ... more than the patient id/external id)
Ray
On Wednesday, April 4, 2012 5:27:53 PM UTC-4, Clayton Sims wrote:
To answer your second question more explicitly, there's no reason to
favor using external id over any other property, we had plans to index or
otherwise use it for common operations, but have decided to deprecate it as
an explicit field in 2.0, so using a patient-id field would work fine.
There's currently no way to change the case name or the external id in
an app whose cases are configured in CommCare HQ. This is due to a bug in
the user interface. It will be fixed in the next revision, but will only be
available for use on CommCare 2.0 applications. I'd say your best choice
for now may be to just use patient ID instead of external ID until we
finish the 2.0 app builder and you're ready to move to 2.0.
We initially chose to set the* external ID to match the orignal value
of the patient ID *case property. Later we found that there are some
scenarios (more than expected) where the CHWs needs to later change/correct
the patient ID. While we can/will allow the CHW to use an 'update' form to
change the patient ID, I don't know if (or how) the external ID can be
changed to match the new patient ID case property.
So, two questions:
1 - Is it possible to change the external ID associate with a case?
2 - If "no", is it possible and reasonable to not specify any external
ID?
I just attempted to configure the "update case" form to update the
"case_name" case property, and received the following message: Can't name
a case property "case_name"
···
*
*
Not sure if that is because I am already using the same form attribute to
update the "patient_name" case property. My intention is to update both
the case_name and patient_name case property values to match the new
patient name entered in the form.
Ray
On Thursday, April 5, 2012 4:55:13 PM UTC-4, Clayton Sims wrote:
You should be able to update the case name by setting the "case_name"
property in 1.3 and above. It's useful to have a case name set for each
case for reporting purposes, so we have something to display for the cases.
Otherwise it is difficult to keep track of them.
-Clayton
On Thu, Apr 5, 2012 at 10:56 AM, Ray Brunsting ray@tula.org wrote:
Danny, Clayton, thanks for your feedback. We'll stop using the
external-id, and no longer be concerned about it being out-of-sync with the
patient id.
Two follow-up questions:
1 - Is it possible to change the case_name associate with a case?
2 - If "no", is it possible and reasonable to not specify any case_name
?
(we have used the original patient name as the case_name, and have found
that it also changes quite a bit ... more than the patient id/external id)
Ray
On Wednesday, April 4, 2012 5:27:53 PM UTC-4, Clayton Sims wrote:
To answer your second question more explicitly, there's no reason to
favor using external id over any other property, we had plans to index or
otherwise use it for common operations, but have decided to deprecate it as
an explicit field in 2.0, so using a patient-id field would work fine.
There's currently no way to change the case name or the external id in
an app whose cases are configured in CommCare HQ. This is due to a bug in
the user interface. It will be fixed in the next revision, but will only be
available for use on CommCare 2.0 applications. I'd say your best choice
for now may be to just use patient ID instead of external ID until we
finish the 2.0 app builder and you're ready to move to 2.0.
We initially chose to set the* external ID to match the orignal
value of the patient ID *case property. Later we found that there
are some scenarios (more than expected) where the CHWs needs to later
change/correct the patient ID. While we can/will allow the CHW to use an
'update' form to change the patient ID, I don't know if (or how) the
external ID can be changed to match the new patient ID case property.
So, two questions:
1 - Is it possible to change the external ID associate with a case?
2 - If "no", is it possible and reasonable to not specify any external
ID?
What Clayton said isn't actually true. Due to a loophole in the UI (which
is a bug), the case name is actually simply not editable. We have an open
ticket for this, and I'll let you know when we have a solution. Sorry to
keep you waiting on such a seemingly simple thing.
Cheers,
Danny
···
2012/4/5 Clayton Sims
You should be able to update the case name by setting the "case_name"
property in 1.3 and above. It's useful to have a case name set for each
case for reporting purposes, so we have something to display for the cases.
Otherwise it is difficult to keep track of them.
-Clayton
On Thu, Apr 5, 2012 at 10:56 AM, Ray Brunsting ray@tula.org wrote:
Danny, Clayton, thanks for your feedback. We'll stop using the
external-id, and no longer be concerned about it being out-of-sync with the
patient id.
Two follow-up questions:
1 - Is it possible to change the case_name associate with a case?
2 - If "no", is it possible and reasonable to not specify any case_name
?
(we have used the original patient name as the case_name, and have found
that it also changes quite a bit ... more than the patient id/external id)
Ray
On Wednesday, April 4, 2012 5:27:53 PM UTC-4, Clayton Sims wrote:
To answer your second question more explicitly, there's no reason to
favor using external id over any other property, we had plans to index or
otherwise use it for common operations, but have decided to deprecate it as
an explicit field in 2.0, so using a patient-id field would work fine.
There's currently no way to change the case name or the external id in
an app whose cases are configured in CommCare HQ. This is due to a bug in
the user interface. It will be fixed in the next revision, but will only be
available for use on CommCare 2.0 applications. I'd say your best choice
for now may be to just use patient ID instead of external ID until we
finish the 2.0 app builder and you're ready to move to 2.0.
We initially chose to set the* external ID to match the orignal
value of the patient ID *case property. Later we found that there
are some scenarios (more than expected) where the CHWs needs to later
change/correct the patient ID. While we can/will allow the CHW to use an
'update' form to change the patient ID, I don't know if (or how) the
external ID can be changed to match the new patient ID case property.
So, two questions:
1 - Is it possible to change the external ID associate with a case?
2 - If "no", is it possible and reasonable to not specify any external
ID?
I just attempted to configure the "update case" form to update the
"case_name" case property, and received the following message: Can't
name a case property "case_name"
*
*
Not sure if that is because I am already using the same form attribute to
update the "patient_name" case property. My intention is to update both
the case_name and patient_name case property values to match the new
patient name entered in the form.
Ray
On Thursday, April 5, 2012 4:55:13 PM UTC-4, Clayton Sims wrote:
You should be able to update the case name by setting the "case_name"
property in 1.3 and above. It's useful to have a case name set for each
case for reporting purposes, so we have something to display for the cases.
Otherwise it is difficult to keep track of them.
-Clayton
On Thu, Apr 5, 2012 at 10:56 AM, Ray Brunsting ray@tula.org wrote:
Danny, Clayton, thanks for your feedback. We'll stop using the
external-id, and no longer be concerned about it being out-of-sync with the
patient id.
Two follow-up questions:
1 - Is it possible to change the case_name associate with a case?
2 - If "no", is it possible and reasonable to not specify any *case_name
*?
(we have used the original patient name as the case_name, and have found
that it also changes quite a bit ... more than the patient id/external id)
Ray
On Wednesday, April 4, 2012 5:27:53 PM UTC-4, Clayton Sims wrote:
To answer your second question more explicitly, there's no reason to
favor using external id over any other property, we had plans to index or
otherwise use it for common operations, but have decided to deprecate it as
an explicit field in 2.0, so using a patient-id field would work fine.
There's currently no way to change the case name or the external id in
an app whose cases are configured in CommCare HQ. This is due to a bug in
the user interface. It will be fixed in the next revision, but will only be
available for use on CommCare 2.0 applications. I'd say your best choice
for now may be to just use patient ID instead of external ID until we
finish the 2.0 app builder and you're ready to move to 2.0.
We initially chose to set the* external ID to match the orignal
value of the patient ID *case property. Later we found that there
are some scenarios (more than expected) where the CHWs needs to later
change/correct the patient ID. While we can/will allow the CHW to use an
'update' form to change the patient ID, I don't know if (or how) the
external ID can be changed to match the new patient ID case property.
So, two questions:
1 - Is it possible to change the external ID associate with a case?
2 - If "no", is it possible and reasonable to not specify any
external ID?