I want to allow 8 different mobile workers to access the same CommCare application on their phones and submit data to the same forms. We are not using user as a case. Is there any reason we shouldn't allow mobile workers to collect data using the same username and password? Are there any risks we should be aware of?
Are there any crucial risks to allowing mobile users sign in with the same username and password to collect data in CommCare
commcare
Related Solutions
The default settings of your project do not let you split mulitselect questions in case exports. This is because your case does not know which questions correspond with which case properties (because it could be multiple questions).
However, we do have a feature preview that you can enable on your project that will allow you to define how you would like to split your case property in a case export.
You can enable this setting by going to https://www.commcarehq.org/a/your_domain/settings/project/previews/ and checking the "Split multi-selects in case export" option. Then hit Update Previews.
When that is enabled you should see an extra column in your export that will allow you to select the Type. Here you select "multiselect." Then you can add your options. Example below:
This normally requires a Pro Plan to setup for your project. I think your project may have an older version of the Pro Plan and needs to updated to the newest one. Once that's done, Cory's solution will work.
Related Topic
- Can the CommCare Export Tool export mobile worker or location information
- How to bulk archive forms submitted with a shared login on CommCare
- Viewing supply point cases at a supervisory level
- Why are there mobile workers missing from the CommCare application status report
- The case and data behavior when I deactivate a mobile user in CommCare
- Please specify exactly which cases will sync down to a mobile device when using CommCare
- CommCare – How to Reference Mobile Worker’s Username in Case List Filter
Best Answer
There are some assumptions that get made about the locality of a user to a single device. If the same user logs into multiple devices there are some edge cases where they won't see updated data that was changed on one of the other devices. This is because the server tries to optimize what data get's synced to a user and assumes that any changes made by the user don't need to be re-synced to the device (since they're already on the device).
There may be other side effects but in general it's not something that is well tested or supported.