--- title: "Extended Texts" slug: "extended-texts-1" description: "Extended Text enhances Information Codes and Values with rich, multi-language content, improving product descriptions for documents and webshops." status: "new" updated: 2026-04-30T12:50:47Z published: 2026-04-30T13:00:20Z canonical: "docs.abakion.com/extended-texts-1" --- > ## 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. # Extended Texts ## Feature Overview Extended Texts adds support for longer, richer content on Information Codes and Information Values — beyond what fits in the standard short Description field. Where the Description field holds a label or a brief caption, Extended Text holds the full narrative: a detailed product explanation, a material safety notice, a marketing paragraph, or any other longer content that needs to accompany a specification. Extended Text in Master Data Information exists in two formats. The **plain text** version is a simple multi-line text entry compatible with standard Business Central document flows. The **HTML** version uses a rich-text editor that supports formatting such as bold, italic, bullet lists, and headings, and is suitable for webshops, document layouts that support HTML rendering, and modern document templates. Both formats support multiple languages — you can add a separate Extended Text entry for each language code, and the correct version is selected automatically when the content flows to a document. Extended Text can be configured at two levels. At the **Information Code** level, the extended text describes the attribute itself — for example, a detailed explanation of what "Fire Resistance Class" means. At the **Information Value** level, the extended text describes a specific option — for example, a full description of what "Class A1" means within the Fire Resistance Class attribute. When Extended Text is configured to flow to documents via **Master Data on Documents**, it appears alongside or instead of the short description depending on how the document template is set up. **Key Facts** | Area | Detail | | --- | --- | | Where to set up | Via the **Extended Texts** or **Extended Texts (HTML)** action on the Information Code Card or Information Value List | | Two formats | Plain text (standard) and HTML (rich-text editor) | | Language support | Per-language entries; resolved automatically based on document language code | | Integration points | Information Codes, Information Values, Translations, Master Data on Documents | --- ## Getting Started 1. Open the **Information Code Card** for the code you want to add extended text to. 2. To add plain extended text to the code itself, choose the **Extended Texts** action. 3. Enter the text in the editor and save. 4. To use the HTML rich-text editor instead, choose the **Extended Texts (HTML)** action (shortcut: `Ctrl+E`). 5. Write and format the content using the editor toolbar, then save. 6. To add extended text to a specific Information Value, open **Information Values** from the code card, select the value line, and use the **Extended Texts** or **Extended Texts (HTML)** action on that line. 7. To add a language-specific version, first open the **Language** action on the code or value, create a language record, and then use the Extended Texts action from within that language record. 8. To make Extended Text flow to documents, configure the relevant **Master Data on Documents** template to include extended text from this code. --- ## Related Features Extended Texts builds on top of **Information Codes** and **Information Values** — it adds depth to the content already defined there. **Translations** works alongside Extended Texts: each language record can have its own Extended Text entry, so the correct content flows to documents in the right language. **Master Data on Documents** is the primary consumer of Extended Text — the document template configuration controls whether plain text, HTML text, or both are included on printed documents. If you use **Merge Descriptions**, note that merge descriptions use the short Description and Value fields, not Extended Text — Extended Text is intended for document output rather than for merged field values. --- ## User Stories ****US-01: Add a detailed description to an Information Code for internal reference**** **As a** Business Manager **I want to** add a full explanation of what the "Fire Resistance Class" attribute means and how to determine the correct value **So that** users who are unfamiliar with the attribute have guidance available without leaving Business Central **Setup:** 1. Open the **Information Code Card** for `FIRE-RESISTANCE`. 2. Choose the **Extended Texts** action. 3. Enter the explanation text. 4. Save. ****US-02: Write a formatted marketing description for a material value using the HTML editor**** **As a** Sales Manager **I want to** create a rich-text marketing description for the "Stainless Steel" material value **So that** this formatted content can flow to customer-facing documents and webshop listings **Setup:** 1. Open the **Information Value List** for the `MATERIAL` code. 2. Select the `STAINLESS-STEEL` value line and choose **Extended Texts (HTML)** (or press `Ctrl+E`). 3. Use the rich-text editor to write and format the description — apply bold for key terms, bullet points for properties, etc. 4. Save. 5. In the **Master Data on Documents** template, configure this code to include extended text on the relevant document types. ****US-03: Provide extended text in multiple languages**** **As a** Sales Manager **I want to** provide English and German versions of the extended text for the "Certification" Information Value **So that** the correct language version flows to documents for each customer **Setup:** 1. Open the **Information Value List** for the `CERTIFICATION` code and select the relevant value. 2. Choose the **Language** action and add a record for `DEU`. 3. From within the German language record, choose **Extended Texts (HTML)** and enter the German version of the content. 4. Repeat for the English default (set on the value directly) and any other languages needed. ****US-04: Include extended text on a sales quote**** **As a** Sales Order Processor **I want to** ensure that the full product description for each item's material appears on printed sales quotes **So that** customers receive complete product information without the sales team having to write it manually each time **Setup:** 1. Ensure the relevant Information Values have Extended Text configured. 2. Open the **Master Data on Documents** template for sales quotes. 3. Configure the `MATERIAL` code to include extended text on quote output. 4. Print a test quote and verify the extended text appears correctly. > **Note:** Whether plain text or HTML is rendered depends on the document layout. Consult the Master Data on Documents article for configuration details. ****US-05: Add a safety notice as extended text on a hazardous material value**** **As a** Business Manager **I want to** attach a safety notice to the "Flammable" value in the "Hazard Category" code **So that** the notice automatically appears on purchase and sales documents when this classification is present **Setup:** 1. Open the **Information Value List** for `HAZARD-CATEGORY` and select the `FLAMMABLE` line. 2. Choose **Extended Texts** and enter the safety notice text. 3. Save. 4. In the **Master Data on Documents** template for purchase and sales orders, configure this code to include extended text. --- ## Field Reference Extended Texts are managed through the Extended Text editor pages and do not have a simple field table — the content is free-form text or HTML entered via the editor. The relevant configuration fields are on the **Information Code Card** and the **Master Data on Documents** template, which control whether extended text is included in document output.