Hide questions in survey, but that can be edited for internal controls

[elisantos]

Hello.

I’m trying to hide questions that are not meant to be answered by users, but rather so they can be edited by the organization team.

I have tried adding the questions as a condition, but when I try to edit the questions, they are still hidden by the logic.

Can you suggest me any solution?

[Kal_Lam]

Welcome to the community, @elisantos! You could do this by following our posts discussed previously:

Hide question option, with autofill

Hi @ryon_1, See an example below where you could hide a default question: [image]

And this one too …

I’d like to have a field (e.g. text field or integer), but don’t want to show it on the form

Maybe you could do the following workaround using the disabled feature as outlined in the steps shown below: Create a survey form with a disabled column and mark TRUE to all those questions that you do not wish to make it visible for the enumerators. [image] You could also use the following xlsform: Disabled.xlsx (9.6 KB) Now deploy the survey project. Collect data and submit them to the server. You should see the disabled column in the dataset. Sample of how it would look: [image] …

[elisantos]

Thank you for your help, @Kal_Lam

[Emeline_92]

Hi,

I wanted to do the same as elisantos, I would like to add an hidden column Reviewer comment. In the case of multiple reviewers, or if clarification is required on a record, a hidden field called “Reviewer Comment” could be added to the form. This field will not appear when completing the form but will be visible in the data table on KoboToolbox. Reviewers will therefore be able to add notes about the reasons for some of the records being held or flagged for removal.

The solution proposed in the post (hidden and disabled) does allow to add a question and the question cannot be seen in the form but I cannot edit the question afterwards to add comments on the data table in KoboToolbox. And I do not want each time to have to change the form and redeploy as we are collecting data every months and I am therefore checking monthly. Don’t want the team to have to download the new version all the time.

Thank you for your help,

Emeline

[Kal_Lam]

@Emeline_92, the best and easiest option would be to add a text question once the data collection is over and then redeploy the project. You could then add a review comment when reviewing the submissions. But please note that you add this text question only once the data collection is over; otherwise, you may have enumerators filling up the review questions, too.