But what I want to achieve is something like this:
I am using here display list in workflow so it works. But what I want to happen is to save it on DB and display it through RG by fetching data on the DB
I tried doing this and it works but only for the subheading fields. The problem is that I also want to include the sublevels field which I can’t do because I can only use one data source.
I’ve been doing this for 2 days and to no avail. I appreciate all the help!
Is there a reason your DB is set up this way? The simplest way to solve this is to create a datatype called something like “sub” or whatever and then add those sub’s to your record in the report data type.
The way you currently have it is doable but it’s much trickier to implement/explain how to implement.
Can you please explain how can I add the SUB datatype into a record in the report data type?
I already created a seperate sub datatype as you said but not sure what to do next.
In your report data type, create a new field and when you choose the type from the dropdown, instead of choosing “text” or “number”, there will be an option to choose “sub”.
Then, in your workflow, where you are creating a new report or making changes to an existing report, you can add the “sub” to the report by either setting the field to the result of step x or one of the couple other ways that bubble allows you to do this. I have no idea how you have your logic set up so can’t say for sure.
I manage to figure out the database part
so the next part is displaying it:
so inside the main repeating group REPORT then inside I search for Outlines with 2 separate RG on the left for the sublevel and on the right is subheading. Is that the way to go?
You can see the screenshot below is from the left side RG to display sublevels
This one is on the right side RG to show subheadings:
In short, no, your approach is not correct. Bubble makes this much easier than what you have done. I fixed it for you. I created “RepeatingGroup Outlines copy”. Take a look at how that is set up.
I would recommend watching some youtube tutorials on how bubble data types work and working with repeating groups. Having a good understanding of this is crucial to building solid apps in bubble. What you did, while it technically works, is not only much harder to build out but is incredibly CPU intensive both server side and client side and will make the app incredibly slow if you have more than 100 items in your database.
