Table Edit MXDK

CAUTION The screen should not be used without first seeking advice from a technical consultant.

This screen provides full edit facilities from which you can maintain and create Tables.

Web Services Tab

The Administrator can configure against each table, which columns, if any, are to be Web Service exported.

Field	Description
Export Column Flag	Each column on the relevant Table can be flagged as needing to be included in the outgoing XML packet of data. There is an additional column to indicate that where that data is a code, do you also want the export to include the relevant code description. NOTE: keys to the table are always automatically exported, no flag is needed for those columns.
Export Code / Description flag	Each column on the relevant Table can be flagged as needing to be included in the outgoing XML packet of data. This column indicates that where the column is defined as having a List / Code description switch available, the export is also to include the relevant code description.
Export Name	This represents an optional override export name that will be included in the extract as an alternative to the column name.
Export Column Options	This setting is reserved for potential future use.
Export / Import	Defaults to none and can be set to Import / Export / Both. NOTE The Import setting is reserved for future use. (When export is in use the key columns for the Table are automatically included in the extracted data, there is no need to flag / un-flag key columns for a table as they will always be exported as part of the data content.)
Name	Defaults to blank, in which case the e5 Table name will be used as part of the data extract. Otherwise up to 60 characters are available to describe the source of the outgoing data extract.
Insert / Update / Delete Triggers	Three triggers can be set for INSERT / UPDATE / DELETE purposes. Each can be defined as Type: Never – The default setting, meaning do not output a data export record. Immediately – As soon as data is changed on the table, a data export will be triggered. Scheduled – The QED Export mapping will be scheduled. Volume – As soon as the trigger volume number of updates is reached a data export will be triggered. Age – As soon as the trigger age limit (in minutes) is reached a data export will be triggered.
Trigger Volume	Against each trigger, a trigger volume control can be defined. This can record a number control, such as 10, such that as at each 10th insert, update or delete is made to the table (depending on the trigger Type), the defined data content for the 10 changes will be output.
Trigger Age	Against each trigger, a trigger age control can be defined. This can record a “minutes” control number, such as 10, meaning minutes. In this case once one of the changes to the table reaches 10 minutes the defined data content will be output.
Export Options	A “catch all” 240 character field allowing for future unforeseen export requirements.
Generated Custom BEM Trigger	Visible against each table is the following information in respect of the Generated Custom BEM trigger: Name: Displays the BEM Custom trigger name for the trigger in respect of this table. Active Flag: Displays when the generated custom trigger is defined in the database. Company / Include: Displays the generated Include Company code and name for the table trigger. Generated Date / Time / User: Displayed for information.
Trigger Maintenance Actions	Actions are available to Submit the generation of the trigger, Recreate the trigger (for example when changes are made to the required data content), and to drop the trigger. (The recreate and Drop actions are only enabled when a trigger already exists). The Submit Generate button will navigate to the relevant QED Mapping parameter screen MQRA, where the QED may be submitted. If the Execute Generated Trigger parameter is set to Y, the created trigger will immediately be set to active. If not, the recreate trigger action button must be used as described below to set the trigger to active. (Visible on the relevant table via the Generated Custom BEM trigger panel). The Recreate and Drop actions both navigate to MXF3 BEM trigger Edit. This displays details of the customised BEM trigger that exists for the relevant table, and Update at this point will Recreate or Drop the trigger as needed. NOTE As with all functions, there is a performance overhead through switching the database trigger function on for a particular table. On a properly sized machine, with adequate resources this should generally be imperceptible. However, if the function is used on a table that is subject to constant, high volume update, there may be a noticeable impact.
Buttons
Set All	Will set the export column flags for all columns on the table.
Reset All	Will reset the export column flags to blank (not selected) for all columns on the table.
Related Tables	Opens Table Web Service Relations MXD6.

Field

Description

Export Column Flag

Each column on the relevant Table can be flagged as needing to be included in the outgoing XML packet of data. There is an additional column to indicate that where that data is a code, do you also want the export to include the relevant code description. NOTE: keys to the table are always automatically exported, no flag is needed for those columns.

Export Code / Description flag

Each column on the relevant Table can be flagged as needing to be included in the outgoing XML packet of data. This column indicates that where the column is defined as having a List / Code description switch available, the export is also to include the relevant code description.

Export Name

This represents an optional override export name that will be included in the extract as an alternative to the column name.

Export Column Options

This setting is reserved for potential future use.

Export / Import

Defaults to none and can be set to Import / Export / Both.

NOTE The Import setting is reserved for future use. (When export is in use the key columns for the Table are automatically included in the extracted data, there is no need to flag / un-flag key columns for a table as they will always be exported as part of the data content.)

Name

Defaults to blank, in which case the e5 Table name will be used as part of the data extract. Otherwise up to 60 characters are available to describe the source of the outgoing data extract.

Insert / Update / Delete Triggers

Three triggers can be set for INSERT / UPDATE / DELETE purposes. Each can be defined as Type:

Never – The default setting, meaning do not output a data export record.
Immediately – As soon as data is changed on the table, a data export will be triggered.
Scheduled – The QED Export mapping will be scheduled.
Volume – As soon as the trigger volume number of updates is reached a data export will be triggered.
Age – As soon as the trigger age limit (in minutes) is reached a data export will be triggered.

Trigger Volume

Against each trigger, a trigger volume control can be defined. This can record a number control, such as 10, such that as at each 10th insert, update or delete is made to the table (depending on the trigger Type), the defined data content for the 10 changes will be output.

Trigger Age

Against each trigger, a trigger age control can be defined. This can record a “minutes” control number, such as 10, meaning minutes. In this case once one of the changes to the table reaches 10 minutes the defined data content will be output.

Export Options

A “catch all” 240 character field allowing for future unforeseen export requirements.

Generated Custom BEM Trigger

Visible against each table is the following information in respect of the Generated Custom BEM trigger:

Name: Displays the BEM Custom trigger name for the trigger in respect of this table.
Active Flag: Displays when the generated custom trigger is defined in the database.
Company / Include: Displays the generated Include Company code and name for the table trigger.
Generated Date / Time / User: Displayed for information.

Trigger Maintenance Actions

Actions are available to Submit the generation of the trigger, Recreate the trigger (for example when changes are made to the required data content), and to drop the trigger. (The recreate and Drop actions are only enabled when a trigger already exists).

The Submit Generate button will navigate to the relevant QED Mapping parameter screen MQRA, where the QED may be submitted. If the Execute Generated Trigger parameter is set to Y, the created trigger will immediately be set to active. If not, the recreate trigger action button must be used as described below to set the trigger to active. (Visible on the relevant table via the Generated Custom BEM trigger panel).

The Recreate and Drop actions both navigate to MXF3 BEM trigger Edit. This displays details of the customised BEM trigger that exists for the relevant table, and Update at this point will Recreate or Drop the trigger as needed.

NOTE As with all functions, there is a performance overhead through switching the database trigger function on for a particular table. On a properly sized machine, with adequate resources this should generally be imperceptible. However, if the function is used on a table that is subject to constant, high volume update, there may be a noticeable impact.

Buttons

Set All

Will set the export column flags for all columns on the table.

Reset All

Will reset the export column flags to blank (not selected) for all columns on the table.

Related Tables

Opens Table Web Service Relations MXD6.

Menus\ Buttons

Action	Use
Values button	Click Values to access a Table field values.
Index button	Click Index to access the Index List MXDM for the current Table.
Commarea relationships button	Opens Commarea relationships.
Subdivision	Click Table: Subdivision.

Action

Use

Values button

Click Values to access a Table field values.

Index button

Click Index to access the Index List MXDM for the current Table.

Commarea relationships button

Opens Commarea relationships.

Subdivision

Click Table: Subdivision.

If not described in this topic, click on a field and press F1 to view help. See Common Fields for more information.

Fast prompt allows you to quickly view a list of options for certain fields.

NOTE Field visibility can be defined by your System Administrator, so not all fields documented may be shown.

See Using the Command Line on opening the screen without going through the menu.