Two cases, one form - using data from both

Hi,

I am looking to create a ‘settings’ case for an app that has a ‘main’ case.

The ‘settings’ will be used to control the display of certain form
elements across all forms.

Can I access ‘settings’ case data whilst in the form under ‘main’?

Best

Tim

Hi Tim,

I’m sure I follow what you’re trying to do, but generally speaking forms
can only access cases in their module (i.e. cases that have the case type
of the module the form is in.

The exception is parent cases. If your form is in a module of child cases,
that form can reference data both in the child case and in the parent case
of that child case (you’ll see that case properties from the parent case
will appear in the case list configuration page for the module as well as
the case properties in the save/load section of the form’s settings page).

Let me know if this does not address your question - I’d be interested in
hearing more about what you’re trying to do!

Thanks,
Amelia

··· On Thu, Sep 11, 2014 at 11:47 AM, Tim wrote:

Hi,

I am looking to create a ‘settings’ case for an app that has a ‘main’ case.

The ‘settings’ will be used to control the display of certain form
elements across all forms.

Can I access ‘settings’ case data whilst in the form under ‘main’?

Best

Tim


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 Amelia,

I have an external app that is used for barcode scanning and is specific to
that device. I want to be able select between it and the standard zxing
scanner.

The simplest way is to have both and don’t display the one that isn’t
needed. This works, but I then need a variable that can be accessed across
the app to put into a hidden field.

Parent and child might do it. I will have a look.

Thanks

Tim

··· On Thursday, September 11, 2014 8:59:45 PM UTC+1, Amelia Sagoff wrote: > > Hi Tim, > > I'm sure I follow what you're trying to do, but generally speaking forms > can only access cases in their module (i.e. cases that have the case type > of the module the form is in. > > The exception is parent cases. If your form is in a module of child cases, > that form can reference data both in the child case and in the parent case > of that child case (you'll see that case properties from the parent case > will appear in the case list configuration page for the module as well as > the case properties in the save/load section of the form's settings page). > > Let me know if this does not address your question - I'd be interested in > hearing more about what you're trying to do! > > Thanks, > Amelia > > On Thu, Sep 11, 2014 at 11:47 AM, Tim <tim.bu...@gmail.com > wrote: > >> Hi, >> >> I am looking to create a 'settings' case for an app that has a 'main' >> case. >> >> The 'settings' will be used to control the display of certain form >> elements across all forms. >> >> Can I access 'settings' case data whilst in the form under 'main'? >> >> Best >> >> Tim >> >> -- >> 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/d/optout. >> > >

I think you’re looking for per-user data. CommCare doesn’t yet support this
functionality through our application builder but we’re tracking demand for
requested feature through uservoice.com - here’s the appropriate link for
this particular feature:
http://dimagi.uservoice.com/forums/194737-commcare-mobile/suggestions/5393295-per-user-data
Feel free to vote.

··· On Thu, Sep 11, 2014 at 9:59 PM, Amelia Sagoff wrote:

Hi Tim,

I’m sure I follow what you’re trying to do, but generally speaking forms
can only access cases in their module (i.e. cases that have the case type
of the module the form is in.

The exception is parent cases. If your form is in a module of child cases,
that form can reference data both in the child case and in the parent case
of that child case (you’ll see that case properties from the parent case
will appear in the case list configuration page for the module as well as
the case properties in the save/load section of the form’s settings page).

Let me know if this does not address your question - I’d be interested in
hearing more about what you’re trying to do!

Thanks,
Amelia

On Thu, Sep 11, 2014 at 11:47 AM, Tim tim.butler.88@gmail.com wrote:

Hi,

I am looking to create a ‘settings’ case for an app that has a 'main’
case.

The ‘settings’ will be used to control the display of certain form
elements across all forms.

Can I access ‘settings’ case data whilst in the form under ‘main’?

Best

Tim


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.


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.

Tim,

If I’m understanding correctly, you have some devices where you want to
call out to a custom bar code scanner and some where you want to use the
normal bar code scanner.

If this is the case, I think custom registration data
https://confluence.dimagi.com/display/commcarepublic/Custom+Registration+Data
is
a better option than having a separate ‘settings’ case.

To use this you’d have some field with a key like ‘custom_scanner’ that’s
mapped to ‘yes’ for all users that are using the device with the custom
call out. Then in that form you’d simply have a display condition that
checks that value and shows the app call out if its ‘yes’ and the regular
question other wise.

Please let me know if I’m misunderstanding anything about your use case.

Best,
Will

··· On Fri, Sep 12, 2014 at 10:26 AM, Tim wrote:

Hi Amelia,

I have an external app that is used for barcode scanning and is specific
to that device. I want to be able select between it and the standard zxing
scanner.

The simplest way is to have both and don’t display the one that isn’t
needed. This works, but I then need a variable that can be accessed across
the app to put into a hidden field.

Parent and child might do it. I will have a look.

Thanks

Tim

On Thursday, September 11, 2014 8:59:45 PM UTC+1, Amelia Sagoff wrote:

Hi Tim,

I’m sure I follow what you’re trying to do, but generally speaking forms
can only access cases in their module (i.e. cases that have the case type
of the module the form is in.

The exception is parent cases. If your form is in a module of child
cases, that form can reference data both in the child case and in the
parent case of that child case (you’ll see that case properties from the
parent case will appear in the case list configuration page for the module
as well as the case properties in the save/load section of the form’s
settings page).

Let me know if this does not address your question - I’d be interested in
hearing more about what you’re trying to do!

Thanks,
Amelia

On Thu, Sep 11, 2014 at 11:47 AM, Tim tim.bu...@gmail.com wrote:

Hi,

I am looking to create a ‘settings’ case for an app that has a 'main’
case.

The ‘settings’ will be used to control the display of certain form
elements across all forms.

Can I access ‘settings’ case data whilst in the form under ‘main’?

Best

Tim


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/d/optout.


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 Will,

This worked and may be very useful for case filtering, displaying the user
full name etc and other bits.

Thanks

Tim

··· On Friday, September 12, 2014 4:04:54 PM UTC+1, William Pride wrote: > > Tim, > > If I'm understanding correctly, you have some devices where you want to > call out to a custom bar code scanner and some where you want to use the > normal bar code scanner. > > If this is the case, I think custom registration data > is > a better option than having a separate 'settings' case. > > To use this you'd have some field with a key like 'custom_scanner' that's > mapped to 'yes' for all users that are using the device with the custom > call out. Then in that form you'd simply have a display condition that > checks that value and shows the app call out if its 'yes' and the regular > question other wise. > > Please let me know if I'm misunderstanding anything about your use case. > > Best, > Will > > On Fri, Sep 12, 2014 at 10:26 AM, Tim <tim.bu...@gmail.com > wrote: > >> Hi Amelia, >> >> I have an external app that is used for barcode scanning and is specific >> to that device. I want to be able select between it and the standard zxing >> scanner. >> >> The simplest way is to have both and don't display the one that isn't >> needed. This works, but I then need a variable that can be accessed across >> the app to put into a hidden field. >> >> Parent and child might do it. I will have a look. >> >> Thanks >> >> Tim >> >> >> On Thursday, September 11, 2014 8:59:45 PM UTC+1, Amelia Sagoff wrote: >>> >>> Hi Tim, >>> >>> I'm sure I follow what you're trying to do, but generally speaking forms >>> can only access cases in their module (i.e. cases that have the case type >>> of the module the form is in. >>> >>> The exception is parent cases. If your form is in a module of child >>> cases, that form can reference data both in the child case and in the >>> parent case of that child case (you'll see that case properties from the >>> parent case will appear in the case list configuration page for the module >>> as well as the case properties in the save/load section of the form's >>> settings page). >>> >>> Let me know if this does not address your question - I'd be interested >>> in hearing more about what you're trying to do! >>> >>> Thanks, >>> Amelia >>> >>> On Thu, Sep 11, 2014 at 11:47 AM, Tim wrote: >>> >>>> Hi, >>>> >>>> I am looking to create a 'settings' case for an app that has a 'main' >>>> case. >>>> >>>> The 'settings' will be used to control the display of certain form >>>> elements across all forms. >>>> >>>> Can I access 'settings' case data whilst in the form under 'main'? >>>> >>>> Best >>>> >>>> Tim >>>> >>>> -- >>>> 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/d/optout. >>>> >>> >>> -- >> 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/d/optout. >> > >