User Community Service Desk Downloads
If you can't find the product or version you're looking for, visit support.ataccama.com/downloads

Views

Views provide users of the RDM web application with a logical subset of chosen tables. Views are composed of two or more tables joined into one record grouping. Views are defined in the RDM Logical Model > Views node.

Create a view

  1. Right-click Views > New view.

  2. Fill in General view attributes.

  3. Add and configure parent tables under the Parent tables section: see Parent table attributes.

  4. Select OK to save changes.

General view attributes

Views are configured via the following attributes:

Field Required Description

Name

Y

Technical name of the view used in model configuration, for example, construction of hierarchies.

Some names are reserved and cannot be used. See Reserved Words and Keywords
The name must be unique across tables, views, and data sets.

Label

Y

Name of the view as shown in the web application.

View description

N

Description of the view to be displayed in the web application by selecting Description.

Show in all tables

N

If selected, the view is shown in the table summary accessible by double-clicking the Tables node in the web application.

Base entity

Y

The child table from which to start building the view (children of this table will not be available, only parents).

Filter

N

Set conditions that restrict the count of rows from the child table to a subset of the table.

Both basic and advanced methods are available. For basic conditions use the forms available in the RDM web app to set entities and operators.

You can use the advanced filter for situations where the basic filter is not enough. It functions similarly to the WHERE SQL clause and uses SQL-like syntax.

To get started:

  1. Press Ctrl+Space or +Space to get a list of all columns. Column names are case sensitive and must be in double quotes if they contain more than one word.

  2. Next, set the filtering rules using operators and/or functions. Operators are not case sensitive, but functions are. Operators appear in purple in the advanced condition box. The following are supported:

    • Operators: LIKE, ESCAPE, FALSE, TRUE, NULL, CASE, IS, IN,=, <>, >, >=, <, , IS NOT NULL, ISNULL, NOTLIKE, LIKEESCAPE, NOTLIKEESCAPE, LIST, FUNC.

    • Logical operators: AND, OR, NOT.

    • Functions: upper, lower, length, concat, now, to_date,substring.

  3. To define the criteria, state what value you are filtering by. Values must be in single quotes and are case sensitive. They appear in red in the advanced condition box.

Native SQL is now supported in row permissions and nativeSql in filter configuration of views and relations.

Columns

Y

Allows selecting columns from the base entity, which is used to construct the view:

  • Name - Column name from the logical model used in the view.

  • Label - (Optional) Name of the column as shown in the web application.

  • Alias - Technical name of the column written to the database; has to be unique across the whole view.

Parent tables

N

Allows selecting parent tables for constructing the view. See Parent table attributes.

Column order

N

Allows ordering columns in the view. Alias names must be used.

Come back to this section after you have fully constructed the view: columns from joined parent tables will become available too.

Parent table attributes

Field Required Description

Name

Y

Technical name of a parent table used in model configuration.

Label

Y

Name of the parent table as shown in the web application by selecting Description.

Relationship

Y

Name of the relationship between the parent table and the base entity.

Columns

Y

Allows selecting columns from the parent table, which is used to construct the view:

  • Name - Technical name of the column.

  • Label - (Optional) Name of the column as shown in the web application.

  • Alias - Alias of the column as shown in the web application; has to be unique across the whole view.

Parent tables

N

Allows selecting parent tables of the next level.

View example

RDM View definition
When referencing foreign key columns in views, you must add the parent table and select the column from there, otherwise validation errors occur.

Was this page useful?