Custom Tables

Using Custom Tables, you can create tables within the Sage 300 company database. These tables will be accessible via view calls, will be in the Sage 300 dictionary and the table will dump and load with the associated company. These tables will automatically be upgraded when a newer version of Extender is loaded

Tip: If you create a table and subsequently add a new field, the new field will be added to the dictionary and the existing data preserved.

Enter a unique Table name and table description.

Extender will give a unique View ID to the table.

All custom tables require at least one key.

Notes:

If using a Module, ensure that the table name is entered as [MODULEID].TableName. Extender will save the Database Table Name with the names to the right of the "full stop".

In an Extender Python script, you can refer to the table by the Database Table Name or the View ID.

Import/Export

Use the File menu to Export / Import the Table definition.

You can also export records from and import records into the custom table.

Tips:

Use the Custom Table Editor to enter a few records, then export Records from the File menu. Add and Update data in the spreadsheet. Use File > Import Records to import into the custom table.

Custom Tables Field list

Custom Tables Keys Field List

Table design consideration

Rule 1: The primary key of your custom table must start with the first field in your custom table. That is the convention and design that Sage views/tables follow.

Rule 2: If the primary key includes multiple fields, the fields must be consecutive in the Table setup.

Rule 3: If you have only one key in the table, the key can be Duplicates Allowed or Duplicates Are Not Allowed.

If you have more than one key in the table, the primary key must be "Duplicates Are Not Allowed" and must start with the first field in your table. Your secondary, third, or fourth keys do not have to start with the first field, and they can be both Duplicates Allowed or Duplicates Not Allowed.