Check Master Record

The Check Master Record server behavior A server behavior is a reusable component for server-side development. They add blocks of code to your pages for accomplishing specific tasks. Dreamweaver comes with several default server behaviors and the InterAKT extensions add many more to this list. allows the developer add a check to ensure that the master record A database row from the master table. The master table is defined by a one-to-many relation to another table (the detail table) used by the page exists in the table.

To add a Check Master Record trigger A trigger is a SQL procedure that performs an action when a transaction (INSERT, UPDATE, DELETE) occurs. You can use triggers to perform validation of input data, to automatically generate a value for a newly inserted row, to read from other tables for cross-referencing purposes, or to support alerts through e-mail messages. into the page, you must follow the next steps:

1. First create an Insert, Update, Custom or Login transaction A transaction is a group of SQL statements whose effects are logically connected. Anything from simple queries to inserting, and deleting operations can be considered a transaction, as well as more complex groups of several statements which accomplish a specific task.. The server behavior is implemented as a trigger, therefore a transaction must exist on the page, so that the trigger can register to it. If more then one transaction exists, the trigger will register to all of them.
2. Access the server behavior from the Application panel, Server Behaviors -> + -> MX Kollection -> Form Validation -> Check Master Record.

3. The user interface that opens is divided into two tabs. Configure these tabs as follows:
   ·  The Basic tab, where options related to the actual check can be set.
   ·  The Advanced tab, where trigger specific options can be set.

4. Once you're done setting the options, click the OK button to apply the server behavior.

The Basic tab

The purpose of this user interface tab is to allow the developer set up the fields to be checked in the master table:

To set the dialog box options, follow the next steps:

1. In the Transaction table drop-down menu, the table used in the insert/update/custom/login transaction on page is automatically selected and the drop-down menu is disabled.

2. In the Foreign key drop-down menu select the table column containing the link to the master table.

3. In the Master table drop-down menu select the table which acts as a master table for the transaction one. The drop-down menu is populated based on the connection used in the page.

4. In the Master primary key drop-down menu select the master table column that stores the primary key.

5. In the Error message text area enter the text to be displayed when the check fails, meaning that the master record does not exist. You can use the InterAKT Dynamic Data (the lighting bolt icon) to build the message.

6. The three buttons in the top right corner of the interface offer you the next functionalities:
   ·  Click OK when you are done configuring the trigger.
   ·  Click Cancel to exit without applying the new settings.
   ·  The Help button opens this help page.
   These buttons are common to both tabs of the Check Master Record interface.

7. Click on the Advanced tab to continue with configuring the trigger.

The Advanced tab

The purpose of this user interface tab is to allow the developer to change the default trigger properties, to suit the particular situation. All trigger properties (name, type, priority, transactions) can be set from this dialog box:

For instructions on completing this step, see the Advanced tab. For the Check Master Record trigger, by default the Priority is set to 40 and the Type is BEFORE (because checking if the master record exists must be done before the transaction).

The server behavior added this way can be edited later by double-clicking its name in the Server Behaviors tab of the Application panel.

Related Topics