The parent job contains a Unique Job # (Item ID column) and a JobLink (Tags column). When the item is created, it generates an item ID, click it (copy it) and paste it into the JobLink field.
We created a hidden status field with an “Active” and “Inactive” status.
We then created a button that would change the status to “Active.”
Then we set an action “When status changes to something (Active), create an item in another board (Child board) and link them using the link to item column in this board.”
We created an automation that would watch for the status to to “Active” and set it back to “Inactive.” …ready for another button push.
This ‘status change’ triggered item creation was important for us to include all the needed details in the parent job before creating one or more child items in the separate board. This process allows us to create child items with mirrored details, including the “JobLink” and leave others blank for individual status, deadlines, owners, etc.
Click the “JobLink” and let the search pull together the parent and child items with their unique metatag.
The mirroring, linking and metatagging itemID’s allowed us to leverage boards like relative tables in a DB.
Let me know if it’s still not making sense.