![](https://sanity-images.imgix.net/production/3bd6ad615e447b7cf414d8e4c8fb5d63f9349c64-4096x2144.png?w=1200&auto=format%2Ccompress)
7 min read
New table or new view?
How to decide when to create a view vs a new table.
What you'll learn:
- Characteristics of tables
- Characteristics of views
- When to use one vs the other
![buttons](https://sanity-images.imgix.net/production/d194cd73cdb9dce4ccca4282e60050240f81d619-128x128.png?w=100&auto=format%2Ccompress)
What you'll use:
- Tables and views
- Columns
- The Doc Map
- Cross-doc
Why is it helpful to create a view when possible?
In one phrase? Change management.These 3 charts are connected views of the same table. When one is updated, all reflect the change.
Does my view have to look exactly like the parent table?
No! Connected views share row information, but can have separate display settings. You can change the following things on a table without having any impact on the other views connected:- Title
- View type (card view, calendar view, etc)
- Filters
- Conditional formatting
- Hidden/exposed columns and column order
- Row Grouping
- Row information
- Column names
- Columns available to be exposed
When might you not want to create a view?
Connectivity, the best part of creating views, can also be a drawback in certain cases. Any change you make in information in one connected view will also be reflected in the other views. To best explain, let’s walk through what might feel like a silly example. Let’s say you're making a roster for your team, and you already have table in your doc that lists out all employees in the company. It’s a part of your specific team’s culture that you use silly nicknames for each other. You could create a connected view of the whole company roster and filter it down just to your team. However, if your team decides they want to go by their silly nickname of Bugs Bunny instead of legal name and change it on your team's roster, they are now going to be Bugs Bunny on the whole employee roster too.How do I know what tables already exist in my doc?
Use the Doc Map in your doc to quickly see what already exists. Learn how here.Can I connect to a table in another doc?
Yes! Using Coda’s Cross-doc pack, you can insert a connected view of any table you have access to into any other doc. Continuing with our roster example, many companies have an official company roster that lives in its own doc. Using Cross-doc, you can bring that roster into your doc and filter it to show just your own team. Learn more about Cross-doc here.Was this helpful?
YesNo