Documentation Index

Fetch the complete documentation index at: https://docs.abakion.com/llms.txt

Use this file to discover all available pages before exploring further.

Specifications on Pages

Prev Next

Feature Overview

Specifications on Pages embeds specification fields directly onto standard Business Central pages — such as the Item Card, Customer Card, Sales Order lines, and many others — without any development or page customisation. Instead of opening a separate specification page, users see and edit specification values as regular fields on the pages they already use.

The feature works by mapping each SCB MDI Field slot (up to 24 per page, per entity type) to a specific Information Code. Once the mapping is set up, the field appears on the page with a label driven by the Information Code Description field on the setup line — auto-populated from the Information Code's own description, but editable so you can show a custom label that differs from the standard code description. Users interact with it exactly like a standard BC field — clicking into it, selecting from a lookup, or typing a value. Changes are written directly to the underlying specification entry and, when a value is changed on the page, the corresponding Information Entry is created or updated automatically. Equally, when a specification is added or changed through the Information Setup page, the page field updates immediately.

The mapping is configured in the Specifications on Pages setup page, accessible from the Information Code Card or the Master Data Information navigation. Each row in the setup defines one mapping: the table, the field slot, the related Information Code, and the type of data to show (Information Value, Value, or Description). The mapping supports both Information Entry tables (master data records) and Master Data on Documents (document lines), which means specifications can be embedded not only on item and customer cards but also directly on sales and purchase document lines.

When an Information Code has Logical Dependencies configured, the lookup on the embedded field is automatically filtered based on other values already set — the same dependency rules apply whether the user is working in the full Information Setup page or the embedded field.

It is also possible to map the same Information Code to multiple SCB MDI Field slots on the same table — for example to show three different colour options for the same COLOUR code as three separate fields. This requires the Information Code to have Allow multiple Config Values enabled. When using multiple slots for the same code, each extra slot must use Master Data Field Type = Value or Description (not Information Value), and each extra slot must have a specific Information Value set — this tells the system which specific value each field slot maps to. You cannot mix Information Value type with Value/Description type across multiple slots for the same code.

Key Facts

Area Detail
Where to set up Specifications on Pages list — accessible via the Information Code Card action or Master Data Information navigation
Field slots Up to 24 SCB MDI Fields per table — each can be mapped to one Information Code
Field label Controlled by the Information Code Description field on the setup line — auto-populated from the code's description, but can be overridden with a custom label
Supported tables Items, Customers, Vendors, Sales Lines, Purchase Lines, Production Orders, Warehouse Documents, and many more
Data types shown Information Value (lookup from predefined list), Value (free text/numeric), or Description
Multiple values for same code Possible when Allow multiple Config Values is enabled on the Information Code — each extra slot must use Value or Description type with a specific Information Value set
Two-way sync Changes on the page field update the specification entry; changes on the specification entry update the page field
Logical Dependencies Dependency rules apply on the embedded field just as they do on the Information Setup page
Integration points Information Codes, Information Values, Logical Dependencies, Master Data on Documents

Getting Started

  1. Open the Information Code Card for the code you want to embed on a page.
  2. Choose the Specification on Pages action to open the Specifications on Pages setup list.
  3. Choose New to add a mapping line.
  4. Set the Table Description to the table where the field should appear (e.g. Item).
  5. In the Field column, use the lookup to select one of the available SCB MDI Field slots for that table (e.g. SCB MDI Field 1).
  6. The Field Caption is populated automatically from the field definition.
  7. Set the Related Information Code to the code you want to embed.
  8. Set the Master Data Field Type to Information Value (if the code has a predefined list), Value (for free-text/numeric input), or Description.
  9. Save. The field will now appear on the relevant pages for that table.
  10. If existing specification entries already exist for this code, use the Update Field Value action on the setup line to populate the page fields with existing data.

Supported Tables and Field Slots

Every supported table has the same 24 SCB MDI Field slots with fixed data types. The field slot number determines the data type — this is hardcoded in the table extension and cannot be changed. Choose the appropriate slot based on the data type your Information Code requires.

Field slots by data type:

Slots Data Type Compatible with Information Code Validation Datatype
1 – 10 Text (250) Text, or any code with no Validation Datatype set
11 – 13 Date Date
14 – 16 Decimal Decimal
17 Integer Integer
18 DateFormula DateFormula
19 DateTime DateTime
20 – 24 Boolean Boolean

Note: The Validation Datatype on the Information Code must match the data type of the field slot. If they do not match, a validation error is shown when saving the Specifications on Pages setup line.

Supported tables:

Tables are grouped by their Master Data Table Type — this determines how the specification value is stored. Information Entry tables store the value in the standard specification framework. Master Data on Documents tables store the value in the document-specific Master Data on Documents records.

Area Table BC Table No. Master Data Table Type
Inventory Item 27 Information Entry
Item Reference 5717 Information Entry
Item Unit of Measure 204 Information Entry
Sales Customer 18 Information Entry
Ship-to Address 222 Information Entry
Sales Header (open) 36 Master Data on Documents
Sales Line (open) 37 Master Data on Documents
Sales Invoice Header 112 Master Data on Documents
Sales Invoice Line 113 Master Data on Documents
Sales Shipment Header 110 Master Data on Documents
Sales Shipment Line 111 Master Data on Documents
Sales Cr. Memo Header 114 Master Data on Documents
Sales Cr. Memo Line 115 Master Data on Documents
Sales Header Archive 5107 Master Data on Documents
Sales Line Archive 5108 Master Data on Documents
Purchases Vendor 23 Information Entry
Purchase Header (open) 38 Master Data on Documents
Purchase Line (open) 39 Master Data on Documents
Purch. Invoice Header 122 Master Data on Documents
Purch. Invoice Line 123 Master Data on Documents
Purch. Receipt Header 120 Master Data on Documents
Purch. Receipt Line 121 Master Data on Documents
Purch. Cr. Memo Header 124 Master Data on Documents
Purch. Cr. Memo Line 125 Master Data on Documents
Purchase Header Archive 5109 Master Data on Documents
Purchase Line Archive 5110 Master Data on Documents
Manufacturing Production Order Header 5405 Master Data on Documents
Production Order Line 5406 Master Data on Documents
Prod. Order Component 5407 Master Data on Documents
Warehouse Warehouse Shipment Header 7320 Master Data on Documents
Warehouse Shipment Line 7321 Master Data on Documents
Posted Whse. Shipment Header 7324 Master Data on Documents
Posted Whse. Shipment Line 7325 Master Data on Documents
Item Tracking Lot No. Information 6505 Information Entry
Serial No. Information 6504 Information Entry
Package No. Information 6515 Information Entry
Finance Fixed Asset 5600 Information Entry
G/L Account 15 Information Entry
Assembly Assembly Header 900 Master Data on Documents

Related Features

Specifications on Pages reads from and writes to the same Information Entry data that Specification Entry (the Information Setup page) uses — they are two interfaces to the same underlying records. Information Codes define what is embedded and how it behaves, including whether users can add new values on the fly via the Allow Users to Add Information Values setting. Logical Dependencies apply automatically on embedded fields — the value lookup is filtered based on other specification values already set on the record. Master Data on Documents uses the same SCB MDI Field mechanism to embed specification fields on document header and line pages, sharing the Specifications on Pages infrastructure.


User Stories

US-01: Embed the Colour specification on the Item Card

As a IT Manager
I want to add the Colour specification as a visible field on the Item Card
So that users can see and set the item's colour without opening the separate Specifications page

Setup:

  1. Open the Information Code Card for COLOUR and choose Specification on Pages.
  2. Add a new line: Table = Item, Field = SCB MDI Field 1, Related Information Code = COLOUR, Master Data Field Type = Information Value.
  3. Save. The Colour field now appears on the Item Card and Item List.
US-02: Embed a numeric Value field on the Item Card

As a IT Manager
I want to embed the Weight (kg) specification as a numeric field directly on the Item Card
So that the weight is visible and editable without opening the specification page

Setup:

  1. Open the Information Code Card for WEIGHT and choose Specification on Pages.
  2. Add a new line: Table = Item, Field = SCB MDI Field 2, Related Information Code = WEIGHT, Master Data Field Type = Value.
  3. Save. The Weight field appears on the Item Card and accepts numeric input.
US-03: Embed a specification on a Sales Order line

As a IT Manager
I want to show the item's Material specification directly on Sales Order lines
So that sales order processors can confirm the material being ordered without leaving the order page

Setup:

  1. Open Specification on Pages setup and add a new line.
  2. Set Table = Sales Line, Field = SCB MDI Field 1, Related Information Code = MATERIAL, Master Data Field Type = Information Value.
  3. Save. The Material field appears on Sales Order line rows.

Note: For document line tables, the Master Data Table Type is automatically set to Master Data on Documents, meaning the value is stored in the document data rather than the item's master specification entry.

US-04: Populate existing page fields after adding a new Specification on Pages mapping

As a IT Manager
I want to ensure that the new Colour field on the Item Card is populated with existing colour specifications for all items that already have a colour assigned
So that the field is not empty for items that were already set up before the mapping was created

Setup:

  1. After adding the Colour mapping on the Specifications on Pages setup page, select the mapping line.
  2. Choose the Update Field Value action.
  3. The app reads all existing Colour Information Entries and populates the corresponding SCB MDI Field on each item record.
US-05: Allow users to add new Information Values directly from the embedded field

As a Business Manager
I want to allow users to type a new colour value directly in the embedded Colour field on the Item Card even if it is not yet in the predefined list
So that users are not blocked when they encounter a new value that has not been added to the Information Values yet

Setup:

  1. Open the Information Code Card for COLOUR.
  2. Enable Allow Users to Add Information Values.
  3. Save. When users enter a value in the embedded field that is not in the list, the app creates a new Information Value automatically.
US-06: Configure Logical Dependencies to filter the embedded field lookup

As a IT Manager
I want to ensure that the embedded Surface Treatment field on the Item Card only shows valid options based on the Material Type already set on the same card
So that users cannot select incompatible combinations even when working in the embedded fields

Setup:

  1. Ensure Logical Dependencies rules are configured between MATERIAL-TYPE and SURFACE-TREATMENT.
  2. Embed both codes on the Item Card via Specifications on Pages.
  3. No additional setup is needed — dependency filtering applies automatically on embedded fields.
US-07: Embed a description-type specification for a text attribute

As a IT Manager
I want to show the item's Marketing Tagline description as an embedded field on the Item Card
So that the tagline is visible and editable inline without opening the Texts specification page

Setup:

  1. Open Specification on Pages setup.
  2. Add a line: Table = Item, Field = SCB MDI Field 3, Related Information Code = TAGLINE, Master Data Field Type = Description.
  3. Save. The Description value of the Tagline specification entry appears in the embedded field.
US-08: Remove a Specification on Pages mapping

As a IT Manager
I want to remove the embedded Colour field from the Item Card because the team prefers to use the full Specifications page
So that the item card is less cluttered and the specification is managed through the dedicated page

Setup:

  1. Open Specification on Pages setup and find the Colour mapping for the Item table.
  2. Delete the line. The system will ask whether to clear the values currently stored in the SCB MDI Field slot on item records.
  3. Confirm if you want the field to be cleared, or decline to retain the data while removing the setup.

Note: Deleting a mapping clears the corresponding SCB MDI Field values on master records, but the underlying Information Entry records are not deleted — the specifications remain accessible via the Information Setup page.

US-09: Map the same Information Code to multiple page fields for different values

As a IT Manager
I want to show three separate fields on the Item Card for the CERTIFICATION code — one field per certification type (CE, UL, ISO-9001) — each showing whether that specific certification is assigned
So that users can see and set each certification independently without opening the full Specifications page

Setup:

  1. Ensure the CERTIFICATION Information Code has Allow multiple Config Values enabled.
  2. Open Specification on Pages and add the first mapping line:
    • Table = Item, Field = SCB MDI Field 1, Related Information Code = CERTIFICATION, Master Data Field Type = Value, Information Value = CE.
  3. Add a second line:
    • Table = Item, Field = SCB MDI Field 2, Related Information Code = CERTIFICATION, Master Data Field Type = Value, Information Value = UL.
  4. Add a third line:
    • Table = Item, Field = SCB MDI Field 3, Related Information Code = CERTIFICATION, Master Data Field Type = Value, Information Value = ISO-9001.
  5. Save. Three separate fields now appear on the Item Card, each linked to a different Information Value for the same code.

Note: When mapping the same Information Code to multiple slots, all slots must use the same Master Data Field Type (Value or Description — not Information Value), and each slot must have a distinct Information Value set. You cannot mix Information Value type with Value/Description type for the same code. The Information Value field must be filled in — leaving it blank on a second slot for the same code will cause a validation error.

US-10: Override the field label shown on a page with a custom description

As a IT Manager
I want to show the embedded Colour field on the Item Card with the label "Product Colour" instead of the default Information Code description "Colour"
So that the label matches the terminology used in our company's item card layout

Setup:

  1. Open the Specification on Pages setup list and find the Colour mapping for the Item table.
  2. In the Information Code Description column (labelled "Field Description" on the page), change the value from the auto-populated "Colour" to "Product Colour".
  3. Save. The embedded field on the Item Card will now show "Product Colour" as its label.

Note: The Information Code Description field is auto-populated from the Related Information Code's description when the code is first selected. Editing it here only changes the label on the embedded page field — it does not affect the Information Code's own description or any other part of the app.


Field Reference

Field Where to find it What it does Default
Table Description Specifications on Pages setup The table where the field should appear (e.g. Item, Customer, Sales Line)
Field Specifications on Pages setup The SCB MDI Field slot to use for this mapping
Field Caption Specifications on Pages setup Auto-populated from the field definition; the internal field name identifier
Data Type Specifications on Pages setup The field's underlying data type (Text, Decimal, Boolean, etc.) — determined by the field slot
Related Information Code Specifications on Pages setup The Information Code whose value is shown in this field
Master Data Field Type Specifications on Pages setup Whether the field shows the Information Value, Value, or Description from the specification entry
Information Value Specifications on Pages setup Required when the same Information Code is mapped to multiple field slots (Allow multiple Config Values must be enabled). Specifies which specific Information Value this slot maps to. Must be blank when Master Data Field Type = Information Value Blank
Information Code Description Specifications on Pages setup (shown as Field Description) The label shown on the embedded page field. Auto-populated from the Related Information Code's description when the code is first selected. Can be edited to show a custom label without affecting the Information Code itself Auto from code
Allow Users to Add Information Values Specifications on Pages setup (read-only) Reflects the setting from the Information Code Card; shown for reference