Tools → Table Editor

About the Table Editor

The Table Editor allows you to define the properties of physical schema entity objects. The physical schema entity objects include the following:

• Physical schema table
• Materialized view (MV)
• Alias
• Incorta Analyzer table
• Incorta SQL table

You must have the suitable permissions and access rights to access the Table Editor and edit the physical schema entity objects. You can also access the Table Editor to view the entity object details.

Table Editor permissions and access rights

A user that belongs to a group with the Schema Manager or the SuperRole role can access the Table Editor for a given object in a physical schema that this user owns or has at least View access rights to.

If the Enable Super User Mode option is enabled in the Cluster Management Console (CMC) → Tenant Configurations → Security, the Super User that is a Tenant Administrator and any user with the SuperRole can access the Table Editor for a given object and edit it regardless of the access rights.

A user with only the Schema Manager role must own or have Edit access rights to the physical schema to be able to use the Table Editor to edit its objects.

You can access the Table Editor for an entity object in a physical schema using the:

• Schema Designer
• Schema Diagram Viewer
• Load Job Viewer for the physical schema (not applicable for an alias)

Access the Table Editor using the Schema Designer

There are multiple options or paths that you have to access the Table Editor for a given object using the Schema Designer for a physical schema that you own or have access rights to:

• If there are no existing entity objects in the physical schema in the Schema Designer, in the Start adding tables to your schema section, select the type of either the entity object or the data source for the new object, except for the Schema Wizard. Use the Data Source dialog to define the data source properties, and then select Add.
• In the Action bar, select + New → Table, and then select the type of the data source you want for the new physical schema table.
• In the Action bar, select + New → Alias.
• In the Action bar, select + New → Derived Table → Incorta Analyzer.
• In the Action bar, select + New → Derived Table → Incorta SQL.
• In the Action bar, select + New → Derived Table → Materialized View.
• For a given entity object in the Tables section, in the Action menu (v arrow), select Table Details.
• In the Tables section, select a given entity object.

Access the Table Editor using the Schema Diagram Viewer

You can access the Table Editor for a given entity object in a physical schema that you own or have access rights to by using the Schema Diagram Viewer of:

• the same physical schema
• another physical schema that this object has a join relationship with one of its entity objects

To access the Table Editor using the Schema Diagram Viewer, select an entity object in the diagram. In the entity object details drawer, select the square with arrow icon next to the object name.

Access the Table Editor using the Load Job Viewer

You can access the Table Editor for a given entity object in a physical schema that you own or have access rights to by using the Load Job Viewer of the physical schema.

Here are the steps to access the Table Editor using the Load Job Viewer:

• In the Jobs list view, if required, select a load job.
• In the Load Job Details list view, in the Name column, select the name link of an entity object.

Table Editor anatomy

The Table Editor consists of the following:

• Action bar
• Table Summary section
• Columns section
• Formula Columns section
• Runtime Security Filters section
• Parent Joins section
• Child Joins section
• Load Filter section

Action bar

The Action bar shows the following, as applicable:

• +New: select to open the Add New menu. The Add New menu options are:
  • Formula Column: select to create a new formula column, available only for physical schema tables and materialized views.
  • Security Filter: select to add a new runtime security filter
  • Join (as parent): select to add a new join relationship for the entity object as a parent
  • Join (as child): select to add a new join relationship for the entity object as a child
• Done: available when you make changes to the physical schema object, whether to add, edit, or remove an item. Select to save the changes you made and exit the Table Editor.
• Cancel: select to cancel the changes you made and exit the Table Editor.

Table Summary section

The Table Summary section contains the following:

• Name: The name of the entity object. You cannot change this name once saved.
• Manage Output: This option is available only for a physical schema table with multiple sources. Select to manage mapping between the columns in the different datasets and to select the data type for each output column in the multi-source table.
• Performance Optimized: This option is enabled by default. The Analytics Service will load performance-optimized objects into the Analytics Service in-memory Direct Data Mapping engine. Toggle this option off to load the object data into Shared Storage only. You must enable performance optimization for Incorta SQL tables and Incorta Analyzer tables to avoid load failure.
• Enforce Primary Key Constraint: This option is available starting with release 5.1.2. It is available in the case of a physical schema table or materialized view with a key column. It is enabled by default. You can enable it to enforce the calculation of the primary key index or disable it to skip this calculation to optimize data load time and performance.
  • When enabled, during a full load job, the Loader Service calculates the Primary key index to enforce record uniqueness.
  • When disabled, the Loader Service skips this calculation. Disable it only if you are sure your dataset has unique records.
  • This scenario applies to full load jobs only. In incremental load jobs, the Loader Service must compare existing and new data to avoid data duplication when key columns are defined.
• Disable Full Load: This option is available only for physical schema tables and MVs enabled for incremental load. Enabling this toggle will prevent the accidental deletion of data from a snapshot table, where the data in Incorta is more granular than the source data. In the case of physical schema tables and MVs that have incremental load enabled and full load disabled, the Loader Service may throw errors in the case of the first full load job or skips them during next full load jobs. Typically, a schema developer performs a full load of an object at least once before enabling this property.
• Data Source(s): This section shows the data source(s) of the physical schema entity object, if any, and in the case of an alias, this section shows the source physical schema and object.
  • There can be one or more data sources depending upon the physical schema entity type.
  • Only a physical schema table can be single-source or multi-source depending upon the connector you use for the data source. The name of the external data file or source appears under the data source icon.
  • Besides physical schema tables, all physical schema entity objects cannot be multi-source. An alias, Incorta Analyzer table, Incorta SQL table, and materialized view must have one and only one data source; they are single-source objects.
  • An alias does not actually have an external data source. It rather references another entity object in the same physical schema or another physical schema.
  • In the case of a physical schema table, the Data Source(s) section shows the add data source option (addition icon in a dashed square) to define a multi-source table.
  • If there are no data sources or you delete the data source, the Data Source(s) section shows the add data source option (addition icon in a dashed square).
  • As applicable, select a data source to access the Data Source dialog to view or edit the data source properties, or to delete the data source.
  • In the case of an Incorta Analyzer table, you can view a sample of the object data in the Data Source dialog.
  • The icon of the data source properties varies according to the physical schema entity objects.
    • In the case of a physical schema table, the data source properties icon represents the type of the dataset whether Files, SQL, XML, Salesforce, ...etc.
    • In the case of other physical schema entity objects, the data source icon represents the type of the physical schema entity:
      • Incorta for an Incorta Analyzer table or Incorta SQL table
      • Materialized for a materialized view
      • Alias for an alias
  • When you save the data source properties of a physical schema table without discovery or when you select to save only the script of the MV in the data source properties, a note under the data source icon confirms that the object is not validated, and the note continues to appear till you validate your updates.

Columns section

The Columns section shows the following:

• The number of data-backed columns in the physical schema entity object
• Preview data: select to preview sample data of the entity object. Available only in the case of a loaded physical schema table or materialized view.
• Search box: use to search for object columns.
• Columns in the physical schema entity object. For a loaded object, you can preview samples of the column data.
• Column properties: determine how the Loader Service extracts and stores data as well as how the Analytics Service loads data. Some properties determine how Incorta stores the column data; other properties influence the column’s representation and default behavior in tools such as the Analyzer and Formula Builder.

The Table Editor shows the properties of a column as follows:

To learn about a column in a physical schema table, review Concepts → Physical Schema Table Column

To learn about a column in a materialized view, review Concepts → Materialized View Column

To learn about a column in an Incorta Analyzer Table materialized view, review Concepts → Incorta Analyzer Table Column

Formula Columns section

The Formula Columns section is available only in the case of a saved physical schema table and a materialized view to create and manage formula columns for the physical schema object. An alias inherits formula columns from the original physical schema table or materialized view; you cannot manage them for the alias itself.

This Formula Columns section shows the following:

• The number of formula columns in the physical schema entity object, if any
• + Add Formula Column: available in the case of a saved object when there are no existing formula columns in this object
• The formula columns in the physical schema entity object, if any. For each formula column, the Formula Columns section shows the following:

To learn more about formula columns in a physical schema table, review Concepts → Physical Schema Table Formula Column

To learn more about formula columns in a materialized view, review Concepts → Materialized View Formula Column

Formula column type inference

Based on the output of the formula expression, the Table Editor will automatically infer the data type of a formula column. You can modify the formula expression to explicitly cast the data type of the return value. For example, you can use a built-in function, such as int(), to specify that the formula expression returns an integer value.

Runtime Security Filters section

A runtime security filter is a filter expression that the Analytics Service applies when a user accesses an in-memory physical schema table, materialized view, Incorta Analyzer Table, or Incorta SQL Table. As an alias only references another physical schema object, you cannot create security filters for it. There are two types of runtime security filter: Regular and Formula.

The Runtime Security Filters section shows the following:

• The number of runtime security filters specified for the physical schema entity object, if any
• If there are no security filters, the + Add Security Filter option is available to add the first security filter.
• All the runtime security filters specified for the physical schema entity object, whether regular filter or formula filter.
• For a formula security filter, the Runtime Security Filters section shows the filter expression for the security filter, if any. Select the text box to invoke the Formula Builder to create or edit the filter expression
• For a regular security filter, the Runtime Security Filters section shows the following:
  • Table: the physical schema entity object to use one of its data-backed or formula columns. This can be the entity object itself or another object in the same physical schema that has a join relationship as a Parent table with the current entity object as the Child table.
  • Column: the filterable column in the entity object you select for the Table. This can be a data-backed column or a formula column.
  • Operator: the operator in the filter expression. This can be one of the following:
    • <: less than
    • ≤: less than or equal to
    • =: equal to
    • ≠ or <>: not equal to
    • >: greater than
    • ≥: greater than or equal to
    • IN
  • Value: the value in the filter expression. This can be a filter expression session variable, internal session variable, external session variable, or a global variable.
• X Remove Filter: select to remove the runtime security filter

To learn more about runtime security filters, review Concepts → Runtime Security Filter.

Parent Joins section

The Parent Joins section shows all the join relationships, if any, where the current physical schema entity object is the Parent table; that is, the object on the right side of the join. With the suitable access rights and permissions, you can add, edit, and delete join relationships in the Parent Joins section if both the Parent and Child objects exist in the same physical schema. However, you cannot edit or remove parent joins with objects in another physical schema. You can access and manage them from the Table Editor of the Child object.

To learn more about joins, review Concepts → Join and Tools → Join Editor.

The Parent Joins section shows the following:

• The number of join relationships, if any, where this object is the Parent table in the join
• + Add Parent Join: available only if there are no existing parent joins for the entity object. Select to add a new join relationship.
• The conditions of each existing join relationship; join filters do not show in the Table Editor. Each join condition defines the following:
  • The physical schema, entity object, and column of the Child side in the join (the object on the left side)
  • Join operator
  • The physical schema, entity object, and column of the Parent side in the join (the object on the right side). Typically, this is the current physical schema object.
• Action menu: available only in the case that both the Parent and Child objects in the join relationship exist in the same physical schema. Options in the Action menu are the following:
  • Join Details: select to access the Join Editor to manage the join conditions and filters
  • Remove Join: select to delete the join relationship

Child Joins section

The Child Joins section shows all the join relationships, if any, where the current physical schema entity object is the Child table; that is, the object on the left side of the join. With the suitable access rights and permissions, you can add, edit, and delete join relationships in the Child Joins section whether both the Parent and Child objects exist in the same physical schema or in different physical schemas.

The Child Joins section shows the following:

• The number of join relationships, if any, where this object is the Child table in the join
• + Add Child Join: available only if there are no existing child joins for the entity object. Select to add a new join relationship.
• The conditions of each existing join relationship; join filters do not show in the Table Editor. Each join condition defines the following:
  • The physical schema, entity object, and column of the Child side in the join (the object on the left side). Typically, this is the current physical schema object.
  • Join operator
  • The physical schema, entity object, and column of the Parent side in the join (the object on the right side)
• Action menu: contains the following options:
  • Join Details: select to access the Join Editor to manage the join conditions and filters
  • Remove Join: select to delete the join relationship

Load Filter section

The Load Filter section is available only for a physical schema table or materialized view. This section shows the filter expression, if any, that the Loader Service applies when loading the object data to restrict the rows to retrieve from the object data source(s).

Select the Load Filter text box to invoke the Formula Builder to create, edit, or clear the load filter expression. To learn more about load filters, review Concepts → Load Filter.

Table Editor actions for a physical schema object

With the Table Editor, you can perform the following actions for a physical schema entity object, as applicable:

• Define a physical schema entity object
  • Define a physical schema table
  • Define an alias
  • Define an Incorta Analyzer table
  • Define an Incorta SQL table
  • Define a materialized view
• Update a physical schema entity object
• Enable or disable performance optimization
• Enable or disable enforcing primary key index calculation
• Enable or disable full load
• Manage data sources
  • Add a data source
  • Create a multi-source physical schema table
  • View data source details
  • Edit a data source
  • Manage output columns for a multi-source physical schema table
  • Remove a data source
  • Preview object sample data
• Manage columns
  • Search for columns
  • Select columns to show in Analyzer
  • Preview column sample data
  • Specify column properties
• Manage formula columns
  • Create a formula column
  • Edit a formula column
  • Select formula columns to show in Analyzer
  • Delete a formula column
• Manage runtime security filters
  • Add a regular runtime security filter
  • Add a formula runtime security filter
  • Edit a runtime security filter
  • Remove a runtime security filter
• Manage joins
  • Create a join as parent
  • Create a join as child
  • Edit a join relationship
  • Remove a join relationship
• Manage the load filter
  • Add a load filter
  • Edit the load filter
  • Remove the load filter

Updates that require data load

Some updates you make to the physical schema objects require loading data, either load from source (full load) or load from staging.

The following are the updates that require load from staging:

• Adding or updating the load filter
• Enabling performance optimization for non-optimized objects

The following are the updates that require full load:

• Adding a new physical schema table or materialized view
• Changing the data type of a physical schema table column or MV column
• Changing the source of a materialized view or physical schema table, whether by selecting another source file in the Data Source properties dialog or editing the query
• Adding or changing a key column (changing the column function from key to dimension or measure and vice versa) in a physical schema table or MV
• Adding a new physical schema table column
• Adding a new MV column
• Changing the object type, for example, changing a physical schema table to an Incorta Analyzer table or MV
• Removing a physical schema table column or a materialized view column that functions as a key

In this case, when you select Done in the Table Editor, and then select Save Changes in the Schema Designer, a warning dialog appears denoting that you have to perform data load. The dialog lists the objects and the required load type for each, and the message banner in the Schema Designer will keep showing the objects that require data load till you or another user performs the required load or a scheduled load job runs the required load for the related object(s). In addition, the Model Status for this object in the Schema Manager and the object icon in the Schema Designer will show a triangle with an exclamation mark.

Table Editor access rights matrix

The availability of sections and options in the Table Editor is subject to both the user access rights to the physical schema and the type of the physical schema entity object.

The following table shows the options and sections available for each entity type and the least access rights required to the related physical schema to perform the action:

Define a physical schema entity object

To create a physical scheme object, you need to use the + New menu in the Schema Designer, and then use the Table Editor to define its properties.

Define a physical schema table

• In the Schema Designer, in the Action bar, select + New → Table → the data source type.
• In the Table Editor, in the Data Source dialog, specify the properties of the new physical schema table.
• Select Add.
• In the Table Editor, for Table Name, enter the name of the new physical schema table.
• In the Action bar, select Done.

To discover more about the properties of different data sources, see Connectors → All, and refer to the suitable connector.

Define an alias

• In the Schema Designer, in the Action bar, select + New → Alias.
• In the Table Editor, for Table Name, enter the name of the new alias.
• In the Table Editor, in the Data Source(s) section, for Schema Name, select the physical schema of the original entity object that this alias references. This can be the current physical schema or another physical schema. The default is the current physical schema.
• For Select Table, select the original entity object that this alias references.
• In the Action bar, select Done.

Define an Incorta Analyzer table

• In the Schema Designer, in the Action bar, select + New → Derived Table → Incorta Analyzer Table.
• In the Table Editor, in the Data Source dialog, select the pen icon.
• In the Analyzer, select the columns in the new Incorta Analyzer table and specify their properties.
• In the Analyzer, select Save.
• In the Data Source dialog, review the sample data, and then select Add.
• In the Table Editor, for Table Name, enter the name of the new Incorta Analyzer table.
• In the Action bar, select Done.

To learn more about the Analyzer, review Tools → Analyzer.

Define an Incorta SQL table

• In the Schema Designer, in the Action bar, select + New → Derived Table → Incorta SQL Table.
• In the Table Editor, in the Data Source dialog, in the Query section, select the pen icon.
• In the Query Editor, enter the SQL code for the new table, and then select Done.
• In the Data Source dialog, select Add.
• In the Table Editor, for Table Name, enter the name of the new Incorta SQL table.
• In the Action bar, select Done.

Define a materialized view

• In the Schema Designer, in the Action bar, select + New → Derived Table → Materialized View.
• In the Table Editor, in the Data Source dialog, specify the properties of the new object.
• Select Add.
• In the Table Editor, for Table Name, enter the name of the new materialized view.
• In the Action bar, select Done.

To discover more about the properties of a materialized view, see Concepts → Materialized View.

Update a physical schema entity object

• Access the Table Editor for a given physical schema entity object.
• In the Table Editor, make the necessary updates.
• To save your changes, in the Action bar, select Done.

Enable or disable performance optimization

The performance optimization is enabled by default for all the physical schema objects. Here are the steps to disable or enable it:

• Access the Table Editor for a given physical schema entity object.
• In the Table Editor, in the Table Summary section, disable the Performance Optimized toggle to disable the Performance optimization, or enable the toggle to enable performance optimization.
• In the Action bar, select Done.

Enable or disable enforcing primary key index calculation

The primary key (PK) index calculation is enabled by default for all the physical schema tables and materialized views with key columns. Here are the steps to disable or enable it:

• Access the Table Editor for a given physical schema entity object.
• In the Table Editor, in the Table Summary section, disable the Enforce Primary Key Constraint toggle to disable the PK index calculation, or enable the toggle to enable the PK index calculation.
• In the Action bar, select Done.

Enable or disable full load

Here are the steps to disable full load for an entity object with incremental load enabled:

• Access the Table Editor for a given physical schema entity object with incremental load enabled.
• In the Table Editor, in the Table Summary section, enable the Disable Full Load toggle to disable full load, or disable the toggle to enable full load for the physical schema object.
• In the Action bar, select Done.

Manage data sources

Add a data source

In the case you delete the object data source or you exit the Data Source dialog without saving the properties of a new object, you can use the Table Editor to add the data source.

• In the Table Editor, in the Data Source(s) section, select + (addition icon in a dashed square).
• In the Data Source dialog, specify the data source configuration as applicable.
• Select Add to check the data source properties and save the new data source.
• In the Action bar, select Done.

Create a multi-source physical schema table

• Access the Table Editor for a given physical schema table.
• In the Table Editor, in the Data Source(s) section, select + (addition icon in a dashed square).
• In the Data Source dialog, specify the data source configuration as applicable.
• Select Add to check the data source properties and save the new data source.
• In the Action bar, select Done.

View data source details

• Access the Table Editor for a given physical schema entity object.
• In the Table Editor, in the Data Source(s) section, select a data source.
• In the Data Source dialog, review the data source properties.
• Select x in the upper-right corner of the dialog to exit it.

Edit a data source

• Access the Table Editor for a given physical schema entity object.
• In the Table Editor, in the Data Source(s) section, select a data source.
• In the Data Source dialog, make the necessary configuration updates as applicable.
• Select Validate to check the data source properties and save the updates.
• In the Action bar, select Done.

Manage output columns for a multi-source physical schema table

• Access the Table Editor for a given physical schema table with multiple data sources.
• In the Table Editor, in the Table Summary section, select Manage Output.
• In the Manage Output dialog, define the data type for the output columns.
• Select Ok.
• In the Action bar, select Done.

Remove a data source

• Access the Table Editor for a given physical schema entity object.
• In the Table Editor, in the Data Source(s) section, select a data source.
• In the Data Source dialog, select Delete.
• In the dialog, select Yes.
• In the Action bar, select Done.

Preview object sample data

You can preview sample data for loaded objects only.

• Access the Table Editor for a given physical schema entity object.
• In the Table Editor, in the Columns section, select Preview Data.
• In the Preview dialog, review the sample data. Select x in the upper-right corner of the dialog or select any other place in the Table Editor to exit the dialog.

Manage columns

Search for columns

• Access the Table Editor for a given physical schema entity object.
• In the Table Editor, in the Columns section, in the Search box, enter a search term.
• Review the list of columns.

Select columns to show in Analyzer

By default, all columns in a physical schema entity object show in the Data panel in the Analyzer. However, you can specify which columns to show.

Here are the steps to specify which columns to show or hide in the Analyzer:

• Access the Table Editor for a given physical schema entity object.
• In the Table Editor, in the Columns section, clear the checkbox for each column you want to hide in the Data panel; select the checkbox for the columns you want to show.
• In the Action bar, select Done.

Preview column sample data

you can preview sample data for a column that is loaded.

• Access the Table Editor for a given physical schema entity object.
• In the Table Editor, in the Columns section, hover over the column you want.
• Select the eye icon.
• Review the column fully qualified name and sample data.
• Select any other place in the Table Editor to exit the column data preview.

Specify column properties

• Access the Table Editor for a given physical schema entity object.
• In the Table Editor, in the Columns section, edit the properties of the column you want as applicable depending upon the entity object type.
  • You cannot change the column name in the Table Editor.
  • For Label, enter a user-friendly name for the column. This is not available for an Incorta Analyzer table nor an Incorta SQL table. However, you can use the Analyzer to specify the column label for an Incorta Analyzer table column, and use the Query Editor to specify another name and label for an Incorta SQL table column.
  • For Type, select the data type of the column.
  • For Function, specify the function of the column in Incorta.
  • In Encrypt, specify whether or not you want to encrypt the column data in Shared Storage.
• In the Action bar, select Done.

Manage formula columns

Create a formula column

You can add a formula column for a saved physical schema table or materialized view.

• Access the Table Editor for a given physical schema table or materialized view.
• In the Table Editor, do one of the following:
  • If there are no existing formula columns in the entity object, in the Formula Columns section, select + Add Formula Column.
  • In the Action bar, Select + New → Formula Column.
• For the new formula column, specify the following:
  • Select the Show in Analyzer checkbox to show the formula column as a selectable column in the Data Panel in the Analyzer.
  • For Name, enter the name of the formula column used in the formula column fully qualified name.
  • For Label, enter a friendly-user name for the formula column.
  • The Type box shows the Incorta Data Type of the formula column that the formula output determines automatically.
  • For Function, specify the Incorta function of the formula column: dimension or measure.
  • Select the Column Formula box to show the Formula Builder to create the formula expression for the formula column. In the Formula Builder, select Validate & Save.
• In the Table Editor, in the Action bar, select Done.

Edit a formula column

• Access the Table Editor for a given physical schema table or materialized view.
• In the Table Editor, for a formula column in the Formula Columns section, make the necessary updates.
• In the Action bar, select Done.

Select formula columns to show in Analyzer

By default, all formula columns in a physical schema entity object show in the Data panel in the Analyzer. However, you can specify which columns to show.

Here are the steps to specify which formula columns to show or hide in the Analyzer:

• Access the Table Editor for a given physical schema table or materialized view.
• In the Table Editor, in the Formula Columns section, clear the Show in Analyzer checkbox for each formula column you want to hide in the Data panel; select the Show in Analyzer checkbox for the formula columns you want to show.
• In the Action bar, select Done.

Delete a formula column

• Access the Table Editor for a given physical schema table or materialized view.
• In the Table Editor, in the Formula Columns section, for the formula column you want to delete, select X Remove Formula.
• In the dialog, select Delete.

Manage runtime security filters

You can add and manage runtime security filters for all physical schema entity objects, except for an alias that inherits the runtime security filters of the original object.

Add a regular runtime security filter

• Access the Table Editor for a given physical schema object.
• In the Table Editor, do one of the following:
  • If there are no existing security filters for the entity object, in the Runtime Security Filters section, select + Add Security Filter → Regular.
  • In the Action bar, Select + New → Security Filter → Regular.
• For the new runtime security filter, specify the following:
  • For Table, select the physical schema entity object to use one of its data-backed or formula columns for the filter expression. This can be the entity object itself or another object in the same physical schema that has a join relationship (as a Parent table) with the current entity object (as the Child table).
  • For Column, select the filterable column in the entity object you selected for the Table. This can be a data-backed column or a formula column.
  • For Operator, select the operator in the filter expression.
  • For Value, select the value in the filter expression. This can be a filter expression session variable, internal session variable, external session variable, or a global variable.
• In the Action bar, select Done.

Add a formula runtime security filter

• Access the Table Editor for a given physical schema object.
• In the Table Editor, do one of the following:
  • If there are no existing security filters for the entity object, in the Runtime Security Filters section, select + Add Security Filter → Formula.
  • In the Action bar, Select + New → Security Filter → Formula.
• For the new runtime security filter, select the text box to invoke the Formula Builder and create the filter expression.
• In the Formula Builder, select Validate & Save.
• In the Table Editor, in the Action bar, select Done.

Edit a runtime security filter

• Access the Table Editor for a given physical schema object.
• In the Table Editor, in the Runtime Security Filters section, do one of the following depending upon the security filter type:
  • For a regular security filter, make the necessary configuration updates.
  • In the case of a formula security filter, select the formula text box to access the Formula Builder and edit the filter expression. In the Formula Builder, select Validate & Save.
• In the Table Editor, in the Action bar, select Done.

Remove a runtime security filter

• Access the Table Editor for a given physical schema object.
• In the Table Editor, for a security filter in the Runtime Security Filters section, select X Remove Filter.
• In the dialog, select Delete.
• In the Action bar, select Done.

Manage joins

Create a join as parent

You can add a join for saved physical schema objects only.

• Access the Table Editor for a given physical schema object.
• In the Table Editor, do one of the following:
  • If there are no existing parent joins for the entity object, in the Parent Joins section, select + Add Parent Join.
  • In the Action bar, Select + New → Join (as parent).
• In the Join Editor, for the new join relationship, specify the join properties for the Child and Parent sides.
• In the Join Editor, in the Action bar, select Done.

Create a join as child

You can add a join for saved physical schema objects only.

• Access the Table Editor for a given physical schema object.
• In the Table Editor, do one of the following:
  • If there are no existing child joins for the entity object, in the Child Joins section, select + Add Child Join.
  • In the Action bar, Select + New → Join (as child).
• In the Join Editor, for the new join relationship, specify the join properties for the Child and Parent sides.
• In the Join Editor, in the Action bar, select Done.

View join relationship properties

• Access the Table Editor for a given physical schema object.
• In the Table Editor, for a given join relationship in the Parent Joins or Child Joins sections, in the Action menu (v arrow), select Join Details.
• In the Join Editor, review the join conditions and filters, if any.
• To exit the Join Editor, in the Action bar, select Cancel.

Edit a join relationship

• Access the Table Editor for a given physical schema object.
• In the Table Editor, for a given join relationship in the Parent Joins or Child Joins sections, in the Action menu (v arrow), select Join Details.
• In the Join Editor, make the necessary updates.
• In the Join Editor, in the Action bar, select Done.

Remove a join relationship

• Access the Table Editor for a given physical schema object.
• In the Table Editor, for a given join relationship in the Parent Joins or Child Joins sections, in the Action menu (v arrow), select Remove Join.
• In the dialog, select Delete.
• In the Action bar, select Done.

Manage the load filter

You can create load filters only for physical schema tables and materialized views.

Add a load filter

• Access the Table Editor for a given physical schema table or materialized view.
• In the Table Editor, in the Load Filter section, select the text box to invoke the Formula Builder to create the load filter expression.
• In the Formula Builder, select Validate & Save.
• In the Table Editor, in the Action bar, select Done.

Edit the load filter

• Access the Table Editor for a given physical schema table or materialized view.
• In the Table Editor, in the Load Filter section, select the text box to invoke the Formula Builder and update the load filter expression.
• In the Formula Builder, select Validate & Save.
• In the Table Editor, in the Action bar, select Done.

Remove the load filter

• Access the Table Editor for a given physical schema table or materialized view.
• In the Table Editor, in the Load Filter section, select the text box to invoke the Formula Builder and clear the load filter expression.
• In the Formula Builder, select Validate & Save.
• In the Table Editor, in the Action bar, select Done.