I manage & coordinate construction tasks using Appsheet.
Anyone in my team can add “tasks” (parent rows). Anyone in my team can add a constant stream of child rows (notes, docs, URLs & images), until the task is closed.
Parent rows could be associated with other parent rows, for a variety of reasons.. some of which are -
a larger task is fleshed out into smaller tasks
there could be task interdependency (but I am not creating any sequencing conditions for this right now..), e.g. plumbing fixtures will be installed after wall tiling is done.
I have attempted to link tasks by creating one more child table having the following columns -
UniqueID
TaskID
TaskID
Column #2 is a Ref to the parent table “Tasks”.. but so is column #3.
this is not working as expected..
I hope by doing this.. I can “jump” from one task to another.
What exactly is not working? You can have as many columns as you want as REF to the same column. If you are using the “Is part of” property, there can only be one column with that set.
I would think of this as a Grandparent table. As I understand it, you are trying to list “sibling” Tasks together. In this Grandparent table, while you could add columns for each of the Tasks you want related together, you can’t easily support an unknown number of “sibling” Tasks this way.
Note that children ALWAYS point at the Parent and each child can have only a SINGLE parent. Parents should never point to the children. This would mean that the Tasks table needs to add a “Grandparent” column. Then you can easily list all related/sibling Tasks and jump from one to another.
