While bubble builds AI ... we still don't have a great solution to tables

Need help
1

Trying to build a simple Table-like UI for survey responses shouldn’t be this tough in bubble.

There are so many improvements that could be made in this area. Nearly every app has tables. Repeating groups alone are not always enough.

Looking for some recommendations:

  • it’s a survey so the amount of questions is dynamic based on the survey
  • I want to see all the survey responses as you would in excel (column is question, cell is answer)
  • I want users to show and hide columns
  • I want column level sorting when it’s a text number or date (:up_arrow: or :down_arrow:)
  • I want the whole table to scroll horizontally with the headers and all the rows

What are the bubble magic tricks to building great tables? :magic_wand:

4 Likes
2

Currently checking out Datatype Agnostic Table Reusable Element - Reuse your clickable table with any datatype by @nico.dicagno – looks awesome so far

3

I think you’d really struggle to build this in bubble

you’d need these data tables
survey - each survey
survey Qs - each Q in survey (since they are dynamic and added by the user?)
survey answers - linked to survey Q and response
survey response - each survey form submit with list of answers

then the table would need to be
this surveys responses (1 per row)
sorted by - this will be tricky but could be achieved with conditionals. for simplicity I’d use a hidden repeating group and then reference it again later for the sorting.
scrolling horizontally - just set repeating group to max 100% width
columns would need min widths else they will collapse

then each row you’d need a repeating group to repeat the survey answers (per response) and the questions would need to be filtered by the users show/hide questions

you’d also need a sort function on the survey answers to ensure they are all in the same order - potentially

basically a repeating group row with a repeating group column within it

definitely needs to be paged

for the aggregates you could store those on the survey question

the difficulty in this is that you want the survey questions to be added by the user so those questions can’t simply just sit on the survey they have to exist separately.

4

I definitely understand and should have read the thread before. Just created a topic about the same thing.
I can’t display data in a table within WFs. I totally agree the table element can and should be a great element to use but seems totally forgotten

5

Last year, I built 2 apps like these.

Yep, that’s a good structure.

For filtering: daisy chain filtering is the answer. Daisy chain filtering | Loom

To expand on the structure, here’s mine. Slightly different because I needed reusable questions and different sets of questions:

  • QuestionSet has a list of QuestionsSetItems
  • QuestionSetItem: joins a
    • QuestionSet
    • Question
  • Question
    • has the question text, tags, description, etc.
    • has a link to AnswerType
  • Assessment (Survey in your case):
    • has a link to a QuestionSet
    • has a list of Answers
  • Answer
    • has a link to QuestionSetItem
  • AnswerType: defines the number of possible answers, their values, and descriptions.
2 Likes
6

This topic was automatically closed after 70 days. New replies are no longer allowed.