Table object

Tables are the core objects used to store data in Business Central. No matter how data is registered in the product - from a web service to a finger swipe on the phone app, the results of that transaction will be recorded in a table.

The structure of a table has four sections:

• The first block contains metadata for the overall table, such as the table type.
• The fields section describes the data elements that make up the table, such as their name and the type of data they can store.
• The keys section contains the definitions of the keys that the table needs to support.
• The final section details the triggers and code that can run on the table.

Table object limits

The table object has limitations that are mostly dictated by SQL Server, such as the maximum record size, number of fields, and the number of keys.

For more information about current limitations on the table object, see Object specifications and limitations.

Table extensibility limitations

System fields

The Business Central platform automatically adds several system fields to tables. For more information, see System fields.

Defining default values for fields

It's commonly used to have field value set to a default value. To do this, you set the InitValue property on the field.

For more information, see InitValue property.

Defining validation rules for fields

If you want to run business logic to validate the value of a field, you can define the OnValidate trigger on the field.

For more information, see OnValidate (Field) trigger.

Snippet support

Typing the shortcut ttable will create the basic layout for a table object when using the AL Language extension for Microsoft Dynamics 365 Business Central in Visual Studio Code.

Add tooltips on table fields

Starting in Business Central 2024 release wave 1, you can define tooltips on table fields. When a tooltip is defined on a table field, any page that uses the field automatically inherits the tooltip.

For more information, see Add tooltips to table and page fields.

Table example

This table stores address information and it has five fields; Address, Locality, Town/City, County, and IsValidated.

table 50104 Address
{
    Caption = 'Sample table';
    DataPerCompany = true;

    fields
    {
        field(1; Address; Text[50])
        {
            Caption = 'Address retrieved by Service';
        }
        field(2; Locality; Text[30])
        {
            Caption = 'Locality retrieved by Service';
            Description = 'Locality feature likely to change in vNext'; // Internal note (not shown in the client)
        }
        field(3; "Town/City"; Text[30])
        {
            Caption = 'Town/City retrieved by Service';
            // in 2024 release wave 1, you can define tooltips on the table field level
            // uncomment the Tooltip line below to try it out
            // ToolTip = 'Town/City retrieved by Service';
        }
        field(4; County; Text[30])
        {
            Caption = 'County retrieved by Service';

            // this is how you define field validation on the table level
            trigger OnValidate()
            begin
                ValidateCounty(County);
            end;

        }
        field(5; IsValidated; Boolean)
        {
            Caption = 'Address validated yet?';
            InitValue = false; // this is how you define default values 
        }        
    }
    keys
    {
        key(PrimaryKey; Address)
        {
            Clustered = true;
        }
    }
}

See also

Table overview
Table extension object
Adding tooltips to table and page fields
InitValue Property (defining default values for fields)
OnValidate (Field) Trigger
Table keys
Table, table fields, and table extension properties
Object specifications and limitations
AL development environment