For BriefBuilder’s tables, it is possible to (pre)define a table set-up (i.e. defining what needs to be in it) and save it for later usage. This is what we call a table definition.
Depending on your role, you can choose to create table definitions for your own usage or table definitions that are available to all project participants.
The latter is of particular relevance to requirement managers and verification managers who want to predefine overviews for the model’s other users. The verification manager may, for example, want to define tables with verifications per discipline. Likewise, the requirements manager may want to predefine commonly used overviews such as the acoustic requirements per space.
In this article, we’ll explain how to do this.
Creating and saving a new table definition
On the table’s selection page, you can create a new table definition by clicking on the New button.
When doing so, you get to see a header called Definition, under which you can use different selections for setting up your table. Note: the selections differ per type of table. The example below concerns the cross table.
Once you have made your selections, you click on the button Save table definition.
Before saving, you can obviously also first view the data in your table to make sure it is what you want. You can do so by clicking on Show and, after reviewing the table, click on Selection in the table to return to the selection page.
The saved table definitions will automatically appear in the list of selectable table definitions every time you go to this table.
For yourself or for all users?
All users can save table definitions for their own use. However, with the right permissions, it is also possible to create table definitions that are available to all the model’s users.
To do so, you have to tick the box Visible for all users with access to this model when saving your table definition.
By predefining certain tables, you can make it a lot easier for the involved disciplines (e.g. electrical, mechanical, etc.) to find the information they need. Yet, try to avoid that you’ll end up with a very long list of table definitions.
Using saved table definitions as a basis
It can be that you want to create a new table definition on the basis of an existing one. In that case, do the following:
(1) Select the table definition that you want to use as a basis.
(3) Make the modifications that are relevant (i.e. adding, deleting or changing selections).
(4) Click on Save table definition.
(5) Select Save selections as new table definition and give the table definition a name.
Copying a link to a table definition
You can copy the link/URL to a particular table definition by clicking on the link icon behind the table definitions’ name.
This can be very practical as you can paste that link into e.g. an email to another project participant who can then ‘jump’ straight to that table (assuming that this person has access to the model).
Editing a saved table definition
To edit a saved table definition, you have to click on the edit icon behind the table definition’s name. When doing so you get to see all the relevant selections which you can then modify and save.
Deleting a saved table definition
To delete a saved table definition, you have to click on the delete icon behind the table definition’s name.
Errors in table definitions
It can be that a predefined table definition no longer works because its selections included objects or values that are no longer present. In that case, you will see a notification that says ‘Table definition may no longer be valid’.
