Once the user has submitted his response, he has no more access to the submitted data.
User story
The teams in the fields are asked to fill a survey to identify the risks presented by each activity (one submit/response per activity, different risks per activity (with repeat group and different mitigation measures per risk with embedded repeat group).
Once the response submitted, the HQ has access to the data and can export it to Excel (with an API key), then to Word (via PowerQuery and Mail Merge). For the moment, the plan is to export the Word docs back to the field after validation.
Still, it would be great if the field teams could retrieve their submitted reponse. We are considering creating a fake survey linked to the first survey (with dynamic data), but this require to populate the forms with the data collected from the first survey based on some input (country, activity code and an index for example), but not sure we can generate a note field with the repeat groups , etc.).
Proposal
Once submitted, Enketo display a code to be noted and with the code, the user can reload the response previously submitted (in read only or editable depending on the setting).
@vmalep, yes maybe that’s a good idea. You could do the following to achieve this.
Use the form that you are currently using. But you will need to add a unique code (variable) to that form/project. This unique code be anything but the respondent should be knowing it (and it should not be known by other users).
Deploy the project that you currently have with the unique code.
Make a clone of that project and consider the clone project as a child project and the previously deployed project as parent project. Link the 2 projects dynamically.
So you will need to share the link of 2 projects to your enumerators now. The first is the parent project which they will have to fill. And the second is the child project where they can simply use the unique code to view their data/responses they filled up in the parent project.
But one thing, maybe you will also need to restrict is that they are not able to submit the child project. So for this, you could add a question and keep a constraint with either a text or an integer which you do not share it with anyone (as an admin). You will also need to keep this question a mandatory response. So now, even if the respondents accidentally tries to fill this and submit the child form, they would not be able to submit it to the server.
