niota

Any table or view that should be managed by niota must be configured as a so called catalog object. Every catalog object has a unique ID by which this object is referenced later on. See below how to create a catalog object.

navigate to the menu item

• add/edit a record → enter valid values for fields listed below

Unique ID for this catalog object. The catalog object ID for customer objects must be positive integer numbers. Negative integer numbers are reserved for system catalog object.

Database connection where object is stored. Via this connection access to the database object is established.

Physical name of the object on its original source database.

Short description of the object.

Date when object is logically activated in niota. Activation date is optional and not parsed or used anywhere.

Optional custom defined category to group catalog object by your needs. On grid edit page catalog object can be filtered by object category by default.

Name of a formatter file without file extions. The formatter file is used to execute format option. The formatter file must be on the server in a subfolder which name matches the name of the database connection for this catalogobject.

ID of an user account who is the data owner of this catalog object. There are some APIs which return this data owner so it can be used in own scripts.

ID of an usergroup which is the deputy group for data ownership. There are some APIs which return this deputy group so it can be used in own scripts.

protected - Checkbox to switch off logging for this object in case table is populated via Excel(R) upload

Checkboxes for custom use only.

An instance is a default or a configured representation of a catalogobject. By default for every catalog object the *default instance is created. You must not delete the *default instance of an catalogobject. If you want to have different represenations of a single physical object (table of or view) you can create different instances of this object with totally different settings.

Logical name for this instance. Do not use * anywhere in the name of your instance. * is a reserved character for system instances.

Description of instance to be used within niota.

List of columns in SQL notation in case not all columns should be selected or in case additional function on columns should be applied. When Join is used the columns must be qualified. See system defaults file for qualifier options.

The use Columnlist checkbox must be on to activate this option.

Optional (left outer) join condition to another table or view you want to join with the main table. The joined table must be qualified by schema name. When join is used, the columns in columnlist must be qualified as well if column names are ambigeous.

The use Join checkbox must be on to activate this option.

Filtering condition in SQL where - notation without WHERE keyword. The use Filter checkbox must be on to activate this option.

Group by clause in SQL notation without GROUP BY keyword. Group by needs aggregation functions in the column list.

The use Group by checkbox must be on to activate this option.

Order by clause in SQL notation without ORDER BY keyword. See system defaults file for default order by options.

Union clause in SQL notation without UNION keyword. Tables in the union clause must be fully qualified as the connection settings are not applied to the union - string.

Checkboxes to toggle usage of related SQL strings.

Flag to allow this table to be used in grid editor

Flag to allow this table to be used in a master-details scenario as a detail table. If not set, it will not appear in the grid dropdown list for detail tables.

Flag to allow this table to be used in a lookup scenario as a lookup instance. If not set, it will not appear in the grid dropdown list for lookup tables.

Flag to allow this table to be used in an advanced filter scenario as a filter instance. If not set, it will not appear in the grid dropdown list for filter tables.

ID of an application to which this table is assigned. If there is minimum one table assigned to an application, the application will pop up on application overview page automatically.

ID of a subject area to which this table is assigned. Within an application all used subject areas will appear in the second menu bar as tabs.

File of an icon, that is also shown then in the second menu bar.

Flag, to autoselect this table in the assigned application/subject area.

Relative number of sortorder within a subject area.
A sortorder value -1 will hide the table

Alternate description that is displayed in the menu bar when grid is shown in an application/subject area context

ID of an predefined layout. Layout defines e.g. grid display size and allowed features.

ID of a predefined form setting. Form is the element that pops up when a record is edited or inserted.

ID of a predefined gridmode. Gridmode set here overrules edit settings on usergroup level By this you may set here gridmode “VIEW” and prevent this table/view from beeing edited.

Flag to use different caption text for this table, in case it's used in a master-detail / related table scenario. If on, caption will be set from description of link in master-detail / related table link.

Flag to ignore/use existing catalog id/table specific layout definition.

ID of the layout that is defined in catalog (object) advanced format. The name here must match the layout ID there.