Creating Views

what are views? views are a way to view data from one or many tables and modify how the tables are displayed using views, you can join multiple tables together based on related columns creating a view over a table allows you to hide columns, rename columns, and change column ordering views can be shared internally or externally ( sharing guide docid\ wxarsa1adsjtkwnbi1ztf ) to share a view, the recipient must have access to all tables used in that view to share a view, the sharer must be an owner of all assets used in that view you can use models to save time building views you can't edit table data from a view you can't use a view to build another view at this time note if you delete a source table from a view that view will break and no longer be accessible if you give a user access to a view, then remove their access to a source table, they will not be able to access the view the view builder view example imagine you need to provide someone with a list showing all employees and the addresses of the offices they work in you have an employees table and an offices table the employees table contains information about the employees , including the id of the office each employee works in the offices table contains information about each office , including office name and address you can easily combine these two tables using a view, by defining the relationship office name on the employees table = office name on the offices table in the below example, these tables will be used feel free to download them and follow along when you upload them, make sure to set the id columns as integer column types https //archbee doc uploads s3 amazonaws com/wel40prhgnhbyasjty021 ckiueutvtemcxhlwy 426 20250120 195708 xlsx https //archbee doc uploads s3 amazonaws com/wel40prhgnhbyasjty021 tckcztgtllsn2oshzuf1k 20250120 195137 xlsx create a new view 1\ go to where you want to save your view in the assets dashboard first, you'll want to navigate to where you'll want the new view to be stored in your folders in the assets dashboard you can always change an asset's location later, by selecting the asset and click the edit > location button 2\ select new >view click the " new " button in the top right of the asset nav window and select view from the dropdown view builder step 1 select assets first, you'll want to and tables or models to include in your view selecting a model will bring all tables and relationships included in that model into your view see creating models docid\ bfj ktszs6q8cfqntenhr for more information on models select the assets you want to include in your view using the folder navigation panel on the left click the add assets to selection button to add assets to your view click the step 2 define relationships button or tab to move onto the next step you can create a view that only contains 1 table this can enable the sharing table data with other users while restricting column visibility, changing column names, and column ordering view builder step 2 define relationships next, you need to define the related columns between the tables in your view this allows you to combine the data between two separate tables into one create new relationships by clicking the new button related columns must be the same column type the guide in lower left will tell you which tables you've selected have relationships all tables must be related to each other test your view by clicking the test view button at the bottom of the page you'll be able to adjust column names, visability, and ordering in the next step click the step 3 customize display button or tab to move onto the final step view builder step 3 customize display the final step in creating a view is customizing the display select the columns you want to be visible rename columns by default, columns are tablename columnname test your view by clicking the test view button at the bottom of the page name your view and give it a description access your view from the assets dashboard hidden columns will be available for column filtering when sharing your view to other users users will never be able to see hidden columns, but you can use them to dictate what rows are visible through filtering this is handy if you are using ids to connect tables, but don't want users seeing the id columns