# Q&A App's Data Configuration

**URL:** <https://community.glideapps.com/t/q-a-apps-data-configuration/75508>\
**Category:** Ask for Help\
**Created:** [August 8, 2024, 5:32am UTC](https://community.glideapps.com/t/q-a-apps-data-configuration/75508 "2024-08-08T05:32:32Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Odyssey](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/odyssey/32/36540_2.png) [@Odyssey](https://community.glideapps.com/u/Odyssey)\
**Post date:** [August 8, 2024, 5:32am UTC](https://community.glideapps.com/t/q-a-apps-data-configuration/75508/1 "2024-08-08T05:32:32Z")

</div>

Hi there, I’m building a simple Q&A app that presents choice fields to the user via a Glide table. The table is setup a question per text column and the options underneath as rows.

I want to ask what the simplest, most efficient way is to then store each user’s choice? Specifically in the choice’s “Write to” section, what table & field would be best?

I will need to read these choices individually per user to provide reporting on it. I would also like the user to be able to go back and change their choice if required.

Thank you

---

<div class="post-metadata">

**Author:** ![Odyssey](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/odyssey/32/36540_2.png) [@Odyssey](https://community.glideapps.com/u/Odyssey)\
**Post date:** [August 8, 2024, 5:45am UTC](https://community.glideapps.com/t/q-a-apps-data-configuration/75508/2 "2024-08-08T05:45:43Z")

</div>

To add to this, there will end up being approx 500-1000 questions with 5 possible answers for each

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [August 8, 2024, 8:56am UTC](https://community.glideapps.com/t/q-a-apps-data-configuration/75508/3 "2024-08-08T08:56:49Z")

</div>

I would normally suggest a separate Responses table, with one row for each users response. But 500-10000 columns would be a nightmare to maintain, and there would be no easy way to present all responses for a single user as a list.

So I think the best way to address this is to store each users responses as a JSON Object. You would need a helper table to add/edit/display, and it’s a bit of work to setup. But once it is setup it would be a lot easier to maintain and work with.

---

<div class="post-metadata">

**Author:** ![Odyssey](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/odyssey/32/36540_2.png) [@Odyssey](https://community.glideapps.com/u/Odyssey)\
**Post date:** [August 18, 2024, 3:48am UTC](https://community.glideapps.com/t/q-a-apps-data-configuration/75508/4 "2024-08-18T03:48:31Z")

</div>

Thanks for the reply. If I reduce the number of questions, what’s the best way to set up the Responses table? How would you link it back to the user & the question?