Share
Explore

Object connected tables

TableA
1
ProjectObject
tasks
1
New Project: 11/29/2022 1:06:08 AM
task 1
task 2
task 3
2
New Project: 11/29/2022 1:09:53 AM
task 1
task 2
task 3
3
New Project: 11/29/2022 1:43:03 AM
task 1
task 2
task 3
There are no rows in this table
View of TableA
1
ProjectObject
tasks
1
New Project: 11/29/2022 1:06:08 AM
task 1
task 2
task 3
2
New Project: 11/29/2022 1:09:53 AM
task 1
task 2
task 3
3
New Project: 11/29/2022 1:43:03 AM
task 1
task 2
task 3
There are no rows in this table
TableB
TaskObject
project
1
task 1
New Project: 11/29/2022 1:06:08 AM
2
task 2
New Project: 11/29/2022 1:06:08 AM
3
task 3
New Project: 11/29/2022 1:06:08 AM
4
task 1
New Project: 11/29/2022 1:09:53 AM
5
task 2
New Project: 11/29/2022 1:09:53 AM
6
task 3
New Project: 11/29/2022 1:09:53 AM
7
task 1
New Project: 11/29/2022 1:43:03 AM
8
task 2
New Project: 11/29/2022 1:43:03 AM
9
task 3
New Project: 11/29/2022 1:43:03 AM
There are no rows in this table
new project
delete all rows
Note: if this would be my document I would give projects a unique number and instead of using last() in the new project button I would filter on the active project number. That is easy to implement and reliable. When using last() you can add a filter where you filter on rows generated by the active user. It is not recommended to filter on rowID’s, because they might not yet be generated when needed.

Share
 
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.