# TrueContext: How do you handle required Yes/No answers while still exporting to Excel?

I like that TrueContext lets you download information into Excel for use, but I have run into a limitation where Yes/No questions cannot be made mandatory to answer. For those using it in the field, how are you ensuring people don’t skip those Yes/No responses? Have you found a workaround in your form design or process that still keeps the Excel export useful?

##### Post Metadata
- Posted at: 2 months ago
- Author title: Billing Specialist
- Net upvotes: 1


## Comments
### Comment 1

Thank you for your question, Judith! After checking with one of our product experts, assuming that you are using the Single Checkbox question type for your Yes/No questions, that&#39;s the one question type that can&#39;t be made required. The reasoning is that checkboxes cannot be Required, because &quot;not checked&quot; is a valid answer, but is identical to an &quot;unanswered&quot; state.

Our guidance for this scenario is to use a Button Group instead of a Single Checkbox for Yes/No questions. A Button Group does support Required as a restriction, unlike Single Checkbox. We see this often as the standard pattern for inspection-style Yes/No/N-A questions: Button Group questions are often used in inspection forms to show a Yes/No/Not Applicable question and can collect additional comments when specified answers are selected.

We&#39;d recommend rebuilding the question as a Button Group with two (or three, if you want to allow N/A) color-coded buttons, e.g. Yes / No, or Pass / Fail / N/A. Once it&#39;s a Button Group, you can turn on the Required restriction, and the mobile app will block submission until it&#39;s answered.

This update will not change the Excel export. Button Group answers export the same way other question values do, and you control exactly what value lands in the export via the &quot;Value submitted to server,&quot; which is what&#39;s sent to any Data Destinations attached to the form. The &quot;Text displayed on device&quot; is what the mobile user sees and doesn&#39;t necessarily have to match the value that is submitted to the server. So you can keep the export clean, e.g. submit &quot;Yes&quot;/&quot;No&quot; as the server value while displaying whatever label you want on the device, and use the display value in reports if that&#39;s preferred, since documents can be configured to show either.

For more details, here are two relevant articles from our Product Documentation Portal:
Question type: Single Checkbox https://docs.truecontext.com/1374411/Content/Published/360021660752.html
Question Type: Button Group https://docs.truecontext.com/1374411/Content/Published/360020126172.html

I hope this helps!

##### Comment Metadata
- Posted at: about 2 months ago




## Related Product
[TrueContext](https://www.g2.com/products/truecontext/reviews)

## Related Category
[Connected Worker Platform](https://www.g2.com/categories/connected-worker-platform)

## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: over 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: over 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: over 13 years ago
  - Comments: 4


