Dog Team

Dog Team Source doc

Here we see the view of the Projects table filtered to [Owning Team]=@[Dog Team].

⁠

Dog Team Sync doc

Here we have the Sync doc for the Dog Team where we synced over the view of the Projects table that is filtered to only show projects where the Owning Team is the Dog Team.

Just under the Dog Team Projects sync table, we have the Dog Team Tasks table. This Tasks table sits by itself in the Dog Team's doc and gives them the freedom to operate however works best for them. There is one ask of the overall organization, and that's for each team to show their progress on each project and report back to the main doc.

Here's where using a filtered view for the Dog Team Projects only comes into play. We can add a column to a cross-doc synced table for additional information. Since this is a view specific to the Dog Team and it's a sync table only in the Dog Team doc, we can write a formula that is also specific to the Dog Team and their Tasks.

The Progress column uses a formula to find all tasks assigned to that particular project and calculates the percent complete. We used a "Scale" column format here because it's a nice visual indicator.

[Dog Team Tasks].Filter(Project=thisRow AND [Done?]).Count()/[Dog Team Tasks].Filter(Project=thisRow).Count()*10

⁠

Now we want to report this Progress value back to the Source doc that the organization is using for their reporting. Time to use a Cross-doc Actions button.

The button column, Update Progress, is connected to the Source doc and the Dog Team Projects table view. The action of the button is going to take the Progress value from this Sync doc table and write it to the Complete column of the Source doc table.

Here is the formula used for the button action:

Crossdoc::ModifyRow([Read-write access to Dog Team Projects within Source doc (ben@coda.io)],Row.RowUrl,"Complete",Progress)

More info on setting up

Cross-doc Actions⁠

⁠

Now the Dog Team can log as many details as they need, in whatever fashion they choose, and they can still report back their progress to the organization and other teams without cluttering up the Source doc.

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.