To provide context, my data structure is as follows:
Workspaces
Projects
Boards
Tasks
Each hold data of each other to one level of itself on either side of it’s structure (if that makes sense).
ie: Projects holds project workspace and project boards. Boards hold board project and board task, etc.
Below is an example of the hierarchy I’ve just described (this is not the element in question).
I’m trying to display the Workspace’s, Project’s, Board’s Tasks (and its fields corresponding to the ‘Table Column Headlines’ group) in my RG when a Board is selected (through URL path?).
Nnothing I try has worked so far…
Then you need to use expression to set your datasource to be ‘get data from URL’ (make sure you indicate the data type is Workspace) then select the Project, then the board and then you’ll have access to the tasks.
From your post it is not clear how you want to show this.
Do you want to show all tasks in a single repeating group for every board for every project within the specific workspace?
Do you want to show a repeating group with all projects of the workspace in the URL with nested repeating groups for the boards within the project and a nested repeating group for the tasks within the boards?
It looks like from screen shot of the elements tree you are using the newly released table feature, is that correct?
One thing to keep in mind, your Workspace in the URL likely has more than one project related to it, the multiple projects related to the workspace probably have multiple boards related to them and the tasks related to the multiple boards that are related to the multiple projects that are related to the single workspace will have multiples of them (tasks) and each task probably has multiple fields.
Based on screen shot from the UI, you should use a single repeating group for all the projects related to the Workspace in the URL (datasource will be get data from url workspace’s projects and type of content is project), then nested RG inside of the Project RG for the Boards (datasource would be current cells project’s boards and type of content would be boards) then have a nested repeating group in the boards RG (datasource would be current cell’s board’s tasks and type of content would be tasks) then in that task RG you can add the elements to visualize the fields of the task you want to display.
The element I’m using to achieve this is not the beta table feature of bubble’s, but a component from the Bubble Essential Kit (essentialkit.io).
To achieve something like the screenshot above, I’m wanting to show only a single Workspace’s project’s board’s tasks, at a time (per screen/view). Just as you would see on an Asana or something similar, ie: user can click into each of the boards within a project (& workspace) at a time to see the corresponding tasks.
To do this would your above answer still be applicable?
Also, this leads me to another question to make sure I set this up correctly from the beginning:
Would it be best for me to be building this task management view as a separate screen/page within bubble? I don’t think it’s explicitly required in order to ‘get data/path from URL’, but as a newbie I’m not sure what best practice would be in terms of speed of the app, structure etc.
Completely dependent on your app…some are single page apps, others are multiple page apps. Just depends on what you are building. Likely it is fine to be a page of it’s own.
So to do so would I first need to ensure that when the user clicks the board that the board, project and workspace are all included in the ‘data to send’, so then the task view in question can ‘get path from URL’?
Data fields that are related to another data type work as below:
I search for data type A and on data type A there are fields 1, 2 and 3 that are related to data type B, C and D respectively and each of those 3 data types have 22 fields on them. When I search for Data type A, I will automatically have access to the 66 data fields of the 3 related data types…so, no need to send any data to the URL except for the Workspace.
When tested I can see it sending to the URL as expected, although it’s conflicting with another current workflow I have for sending data to URL for sidebar tabs and subtabs, as outlined below:
I’m not sure what expression would be needed to keep these workflows applied to only the sidebar tabs/sub tabs, and not to interfere with sending the Workspace to the URL. Any ideas?
If you would like to have a training session to fix up all the issues you are facing, you can find me via the Bubble coaching page to book a paid training session.
Thanks @boston85719. I look to have fixed all the issues I’m facing currently now, but if any other tricky problems come up I’ll keep you in mind. Thanks again!
