Create a view
- Last UpdatedAug 14, 2026
- 5 minute read
To create a new view:
-
Open Configure Views dialog
Do either of the following:
-
Right-click a column header in the database view and choose Configure Views from the context menu.
-
Select Configure Views from the View menu in the View group of the Home ribbon tab.
The Configure Views dialog box will open.
-
-
Create a new view
-
Click the Add View button
on the toolbar at the top of the dialog. Alternatively, you can create a copy of
the selected view by clicking the 
button.
-
Enter a view name
In the dialog box that appears, enter a name for the view and click OK.
-
Add columns to the view
Use the in-built column types provided, to configure a new column of a given type and add this to the view. A corresponding description of the column appears in the columns pane to the left hand side of the Configure Views dialog. By repeating this process as necessary, you cumulatively build up the constituent columns comprising the view. See Configure Column Details below.
Use the column management buttons located at the bottom left of the columns management pane to manage the constituent columns you add.
-
: Adds a copy of the selected column to the configured columns list, and to the Database View. The new column can be edited in the column details section.
-
: Removes the selected column from the configured columns list and from the Database View.
-
and 
: Moves the selected column up and down in the list, changing the corresponding position
of the column in the Database View.
-
-
Configure column details
The right hand side of the configure columns dialog shows the details for the column selected in the left hand side list of column headers. It allows the details for the column to be configured. The details that can be modified for every column are:
-
Field
-
Heading
-
Field
The field is the type of column which will be configured. It will usually be one from the following list of choices:
|
Field Name |
Type |
Description |
|---|---|---|
|
Assay Date |
Date |
The date the assay values of the sample were measured in the assay provider's laboratories. |
|
Creation Timestamp |
Date |
The date and time at which an assay has been created from tools such as Blend and AssayWorkup. |
|
Cut* |
Value |
The property value for a particular perfect cut. |
|
Database Name |
Textual |
The name of the Database to which the crude belongs. This field name will depend on the Database(s) you have licensed. The default options of the names of the databases standard in your edition of Assay are always available. |
|
Descriptive Name |
Textual |
The name of the crude. |
|
Flowsheet Cut* |
Value |
The property value for a chosen commercial cut. |
|
Formula* |
Value |
A calculation using one or more properties as variables. |
|
Generated with current model? |
|
Whether the assay data have been worked up and profiles generated using the current approved version of Assay. |
|
GUID |
Textual |
A unique identifier for this database entry. Can be used with the SDK to select a particular crude. |
|
Import Timestamp |
Date |
The date and time at which an assay has been imported from a .cdb (crude database) file. |
|
Issue Date |
Date |
The date the assay was issued (published) by the assay provider. |
|
Last Modified |
Textual |
The date on which the crude was last modified, if this was recorded. Assays may be modified without changing the overall crude description or any of the property profiles, by for example, changing their references. |
|
LP Tag |
Textual |
The three-letter tag used in PIMS assay files to denote this crude. This can be set in the Crude Properties dialog. See Crude summary dialog. |
|
Measured Value* |
Value |
The original measurement for a particular cut/property combination entered in the Measurement Grid during assay workup. |
|
Nearness* |
Bar |
The similarity to a given crude. |
|
Oil Type |
Textual |
The type of oil, for instance Crude or Blend. |
|
Origin |
Textual |
The place of origin of the crude. |
|
Publish Timestamp |
Date |
The date and time at which an assay has been last updated on a share. |
|
Recommended? |
|
Is this crude flagged as recommended in the distribution? |
|
Reference |
Textual |
A reference name for the crude. |
|
Sample Date |
Date |
The date the sample of crude was taken. |
|
Source Reference |
Textual |
The reference for the assay data. |
|
SRPV* |
Value |
The dollar value of the crude, under certain constraints and product prices. |
|
Traded Crude |
Textual |
A standard name for the crude, which enables easier grouping by crude. This can be set in the Crude Properties dialog. See Crude summary dialog. |
|
User Crude? |
|
Is this crude a user generated crude? |
|
User Notes |
Textual |
Your comments about the crude. |
|
Yield Bar* |
Bar |
A summarizing view of the yield distribution. |
The fields marked * need further configuration, and are explained in more detail below.
Heading
In each case the product will suggest a suitable column heading, based on the details so far entered. You can alter the heading by selecting the heading suggested and typing in an alternative.
Recommended Assays
Assays in the database may have a recommended flag set. When an assay has this flag a tick appears for the assay when a Recommended column is configured in the database. For licensed assay libraries AVEVA automatically sets a single assay of each traded crude as recommended. This is always the most up-to-date assay of the crude available. All of the assays present in the Spiral HPI assay library are also set as recommended by default.