I’m trying to create a folder system that allows as many levels of folders as a user wants.
My table has these things:
Table: Folders
Fields:
- Folder Name
- Parent Folder (connection to Folders table)
My page has this:
- In the folder detail page, I have a table showing folders connected via the Parent Folder with add folder functionality from the options in the table
I know a folder is a subfolder if it has a parent folder assigned
What I want:
If I go to a folder’s details and add a subfolder, I want the subfolder to correctly assign itself the parent folder.
What is happening:
When I try to add a subfolder, it’s actually setting the subfolder as the parent of the primary folder
Also, when I try to add a table for subfolders, there are 2 options to select from
Here’s a Loom video with my app experience issue:
And here’s another with my builder issue:
Any chance of a screenshot or Loom video or something? This is complex to describe in words…it might be easier for other users to understand with a little more show and tell.
1 Like
Just added a couple Loom videos
Hey Josh, i dont think this is possible as far as i know
In order to have multiple levels of folders and subfolders you would first need a parent table for the root folder, then you would need to create a child table for the first level of sub folders and make a connection to the root folder. If you want to go a level deeper, you would need to add another table connected to the child table (grandchild) and so on.
You wouldn’t be able to make it limitless because there is no way to create a data table from the front end of the app
So you can’t have a table be a parent/child of itself? What I’m wanting to make almost works. It’s just that when I try to add a child folder to the parent folder, it instead makes the “child” the parent of the parent folder. This is initiated from an “add new record” action from the child table
I’m struggling with this - it seems to me there’s some kind of logic rule you’re trying to break. I want to understand this better. Why do you want this to work this way? What are you trying to achieve?
@Josh_Yellowtail
For connecting to the folder of the detail page’s record:
- Log the record ID of the current page’s record inside your detail component using the option called “save to local storage”
- Give the variable a name and copy it somewhere
- In your form to add a new folder on the detail page, add a record rule to set the parent to browser local storage variable - the one you copies earlier
For the confusing way pre-set filters are displayed when using self-connections:
Don’t choose a pre-set filter when adding your table component to your detail page, choose the option to load all folder records. Open the table component to edit it, click data source, create a filter that says “parent folder is this pages record ID”

1 Like