NAVAX Document Text

Manual

☰ Contents

General

• NAVAX Document Text
  NAVAX Document Text is an extension for Microsoft Dynamics 365 Business Central that allows you to centrally manage individual Extended Texts for sales, purchase, service, and job documents and automatically integrate them into your documents...

Setup

• Document Text Setup
  Before you can use NAVAX Document Text, you must make the basic settings. On this page, you define the most important options...
• Extended Texts
  An Extended Text is an individually defined text that is either automatically or manually inserted into a document - depending on the selected type and defined conditions. You create Extended Texts on the Standard Text Codes page, which you can find via search in Business Central...
• Beginning and Ending Texts
  Beginning and ending texts are Extended Texts that are automatically inserted before or after the document lines. They appear in sales, purchase, service, or job documents. Use these texts for notes, legal information, or individual messages to your customers...
• Personalized Texts
  Personalized texts are Extended Texts that are specifically created for a particular customer, vendor, or salesperson/purchaser. These texts are automatically used in documents when the corresponding business partner is selected...
• Line Texts
  Line texts are Extended Texts that are directly linked to master data such as items, resources, G/L accounts, or service items. The text appears automatically as line text below the respective line when you use the corresponding master data record in a document...
• Miscellaneous Texts
  Miscellaneous texts are Extended Texts that are linked to master data such as payment terms, shipment methods, or service configurations. These texts appear automatically in documents when the corresponding configuration is used in the document...

Working with the App

• Using Beginning and Ending Texts
  This page describes how to use, edit, and manage beginning and ending texts in your daily documents...
• Using Personalized Texts
  This page describes how to use, review, and manage personalized texts in your daily documents...
• Using Line Texts
  This page describes how to use, edit, and manage line texts in your daily documents...
• Using Miscellaneous Texts
  This page describes how to use Miscellaneous Texts in your daily documents...
• Sorting and Conditions
  With the advanced text conditions in NAVAX Document Text, you can flexibly control which texts are used and transferred to your documents. You can specify that certain texts are automatically inserted only for selected languages, within a specific time period, or for specific document types. This ensures that all relevant information always appears correctly and contextually in your sales, purchase, service, and job documents...
• Example Scenarios
  This page provides practical examples for various use cases of NAVAX Document Text. Each scenario shows step-by-step how to set up and use specific features...
• FAQ and Troubleshooting
  Here you will find answers to frequently asked questions about NAVAX Document Text as well as solutions to typical problems...

Advanced Features

• Item Attributes
  NAVAX Document Text extends the Business Central standard functionality for item attributes by automatically transferring them as document text lines to your documents. This allows important product properties such as material, color, size, or technical specifications to appear directly on quotes, orders, and invoices...
• Text Editor and Placeholders
  NAVAX Document Text provides a text editor that allows you to easily create and edit extended texts for documents. The editor supports placeholders to insert dynamic content from the respective tables. You can copy pre-formatted texts from other programs and paste them into the text editor...
• Formatting
  With the formatting functions in NAVAX Document Text, you can design your extended texts professionally and in accordance with corporate identity guidelines. You can adjust font type, size, and color, as well as control paragraph alignment and indentation...
• Copy Documents
  When you copy documents, a window may appear - depending on the setup - asking whether and which texts should be transferred with the document...
• Report Layout Selection
  The Report Layout Selection window defines which layout should be used when printing a document. For document texts to be printed on A4 documents, the corresponding NAVAX Document Text report layouts must be set up...
• Export/Import
  With the export and import function, you transfer configured Standard Text Codes between different Business Central installations. This enables efficient management of your extended texts and saves time during setup...

Field Descriptions

• Standard Text Code Fields
  Using Standard Text Codes, you can manage Extended Texts for documents in Dynamics 365 Business Central. These codes allow you to store frequently used texts centrally and insert them on documents as needed...
• Extended Texts
  Extended texts are individually defined texts that can be automatically inserted into documents. You create extended texts on the Standard Text Codes page, which you can easily find via search...
• Document Header Fields
  With NAVAX Document Text, you can add beginning and ending texts to all documents in Dynamics 365 Business Central. These texts appear in the document header and are suitable, for example, for greetings, notes, legal information, or individual messages...
• Personalized Texts
  The fields for personalized texts allow you to store Extended Texts specifically for a particular customer, vendor, or salesperson/purchaser...
• Document Lines Fields
  In all documents in Dynamics 365 Business Central, you can add line texts. This lets you print additional information directly below the respective document line. Line texts are suitable, for example, for product information, notes, or legal information...
• Line Positions on Master Data Cards
  NAVAX Document Text allows you to link Extended Texts directly to master data such as items, resources, G/L accounts, or service items. These texts appear automatically as line texts below the respective line when you use the corresponding item, resource, G/L account, or service item in a document...
• Miscellaneous Texts
  Miscellaneous texts in NAVAX Document Text allow you to display additional information on documents that is not directly associated with the usual document types such as sales or purchase documents. These texts can be used for various purposes, e.g., for legal notices, special instructions, or individual messages that cannot be captured in the standard fields of the documents...
• Document Text Line Fields
  Document text lines are created automatically as soon as you use texts via NAVAX Document Text in documents. These lines contain the actual content that is displayed on the respective documents. They allow flexible design of the document texts, e.g., through formatting such as bold, italic, colors, or individual fonts and sizes. The text lines can be used for different document types and customized individually...
• Field List
  The field list provides you with an overview of all fields that can be selected from the chosen tables in document texts or extended texts to be used as placeholders...

Information for Developers

• Extending Documents
  NAVAX Document Texts provides a set of standard documents that contain the Document Texts and can be used without customization. If this is not sufficient for your company or your documents need to be customized, you can also use NAVAX Document Texts on your own documents...
• Extending NAVAX Document Text
  This page contains a list of all available events for the individual objects that can be used to extend the core functionality of NCDT Document Text...
• Events

Appendix

• NAVAX License Management
  The NAVAX License Management page (in older versions NAVAX License Overview or NCEX License Overview) displays the current license status of the NAVAX extensions...
• Installation Notes
  This page contains important information about the installation and technical requirements of NAVAX Document Text. The information is primarily intended for administrators and IT managers...
• Release Notes

Docs  /  App  /  NAVAX Document Text  /  General
 NAVAX Document Text

Brief Overview of Features

• Beginning and Ending Texts: General texts, greeting texts before or after the document lines For more information, see Setup, Beginning and Ending Texts.
• Line Texts: Texts directly under individual document positions for items, G/L accounts, resources, service items For more information, see Setup, Line Texts.
• Miscellaneous Texts: Texts for shipment methods, payment terms, service order types, reminders, etc. For more information, see Setup, Miscellaneous Texts.
• Personalized Texts: Individual beginning and ending texts for specific customers, vendors, or salespeople/purchasers For more information, see Setup, Personalized Texts.
• Conditions: Texts only in specific time periods, selected documents, or for specific languages For more information, see Working with the App, Sorting and Conditions.
• Placeholders: Automatically insert dynamic content such as date, customer name, or amounts For more information, see Advanced Features, Text Editor and Placeholders.
• Formatting: Font type, size, color, alignment, and more for attractive design For more information, see Advanced Features, Formatting.
• Item Attributes: Automatically insert texts based on item attributes For more information, see Advanced Features, Item Attributes.
• Export/Import: Extended Texts can be easily backed up, transferred, and exchanged between companies For more information, see Advanced Features, Export/Import.

Getting Started

1. Open Document Text Setup and configure basic settings For more information, see Setup, Document Text Setup.
2. Create Extended Texts for beginning/ending texts, line texts, or miscellaneous texts For more information, see Setup, Extended Texts.
3. Select report layouts that support document texts For more information, see Advanced Features, Report Layout Selection.
4. Use texts in documents - insert automatically or manually For more information, see Working with the App, Using Beginning and Ending Texts.

Navigation

Tell me what you want to do

• Document Text Setup - Basic settings and default values
• Standard Text Codes - Manage and edit Extended Texts

Installation Notes

Docs  /  App  /  NAVAX Document Text  /  Setup
 Document Text Setup

Setup Steps

1. Open the NCDT Document Text Setup page via search.
   
2. Activate Document Texts Activated in the Document Text Setup.
   
3. Configure the options in General according to your requirements. This includes settings for activation, copying texts when transferring documents, and printing item attributes.
4. Define the Default Formattings. Specify font type, font size, font color, paragraph direction, and formatting such as bold or italic that should be used as default settings for new text lines. You can also specify spacing and indentation for new text lines. This ensures a consistent and CI-compliant appearance. For more information, see Advanced Features, Formatting.
5. Create the Standard Text Codes using the action of the same name. These contain Extended Texts that can be automatically inserted into documents based on defined conditions. For more information, see Setup, Extended Texts.
6. Define the Extended Texts for the following master data via the respective action:
   • Payment Terms
   • Shipment Methods
   • Reminder Terms
   • Finance Charge Terms
   • Service Order Types
   • Service Contract Groups
   • Standard Service Codes
   These Extended Texts are called Miscellaneous Texts. For more information, see Setup, Miscellaneous Texts.

Actions

• Standard Text Codes

  Opens the Standard Text Codes page where you can define and set up general texts, these texts can be used in various areas.

Setup, Actions

• Payment Terms

  Sets up the Extended Texts for payment terms that are inserted on documents for your customers.

• Shipment Methods

  Sets up the Extended Texts for shipment methods that are inserted on shipments for your customers.

• Reminder Terms

  Set up Extended Texts for reminder terms that are inserted on reminders.

• Finance Charge Terms

  Set up Extended Texts for finance charge terms that are inserted on documents in case of late payment by the customer.

• Service Order Types

  Here the Extended Texts for service order types are set up, which can be inserted on service orders, service contracts, or contract quotes.

• Service Contract Groups

  Here the Extended Texts for service contract types are set up, which can be inserted on service orders, service contracts, or contract quotes.

• Standard Service Codes

  Here the Extended Texts for standard service codes are set up, which can be inserted on service orders, service contracts, or contract quotes.

System, Actions

• NAVAX License Management

  Opens the NAVAX License Management, which displays the current license status of the NAVAX extensions.

Docs  /  App  /  NAVAX Document Text  /  Setup
 Extended Texts

Extended Text Types

Beginning Texts

Ending Texts

Line Texts

Miscellaneous Texts

Basic Structure of an Extended Text

How to Create an Extended Text

General Step-by-Step Guide

1. Open the Standard Text Codes page via search.
   
   
2. Click New to create a new Standard Text Code.
3. Enter a unique Code (e.g., GREETING, TERMS, NOTE). This code serves as an identifier for the Extended Text.
4. Enter a meaningful Description that explains the purpose of the text.
5. Select the desired Text Type:
   • Beginning Text - Text appears before the document lines
   • Ending Text - Text appears after the document lines
   • Other types depending on configuration
6. Click in the Extended Text Exists field or choose the Extended Texts action to go to the Extended Text overview.
7. Click New to create a new Extended Text.
   
8. On the Extended Text page, you can make all settings for the text.
   
9. Define additional conditions to control when the Extended Text is applied. Options include:
   • Language Code - Text appears only for a specific document language
   • Starting Date/Ending Date - Text is only valid during a specific period
   • Sorting Sequence No. - Determines the order when there are multiple Extended Texts
   For more information, see Working with the App, Sorting and Conditions.
10. Enter the Text that should appear on the document. Click in the Text field to open the text editor. For more information, see Advanced Features, Text Editor and Placeholders.
    
11. Optional: Use placeholders for dynamic content (e.g., ##Bill-to Customer No.##, ##Document Date##). For more information, see Advanced Features, Text Editor and Placeholders.
12. Optional: Use the formatting options to customize the appearance. For more information, see Advanced Features, Formatting.
13. Define the document types for which the Extended Text should apply:
    • On the Sales FastTab: Sales Quote, Sales Order, Sales Invoice, etc.
    • On the Purchase FastTab: Purchase Order, Purchase Invoice, etc.
    • On the Service FastTab: Service Order, Service Quote, etc.
    • On the Job FastTab: Job Quote
    
    

    Tip

    When you select or deselect multiple documents, a query appears asking whether you want to select or deselect all documents. Using the actions Belegfolgefelder deaktivieren and Belegfolgefelder deaktivieren, you can select or deselect all values at once.
14. Save the Extended Text by closing the page. The changes are automatically applied.

Important Concepts

Placeholders

Conditions

Formatting

Next Steps

• Set up beginning and ending texts: Detailed guide with examples For more information, see Setup, Beginning and Ending Texts.
• Set up line texts: Extended Texts for items, resources, and G/L accounts For more information, see Setup, Line Texts.
• Set up miscellaneous texts: Texts for payment terms, shipment methods, etc. For more information, see Setup, Miscellaneous Texts.
• Available table fields: List of all fields for placeholders Field Descriptions, Extended Texts

Tips and Best Practices

• Meaningful codes: Assign descriptive codes like GREETING, TERMS_EN, NOTE_QUOTE instead of cryptic abbreviations.
• Use descriptions: A good description helps in quickly finding Extended Texts.
• Create test documents: Always test new Extended Texts in a test document before using them productively.
• Use formatting sparingly: Too much formatting can impair readability.
• Plan for multilingual: Create Extended Texts in all required languages for international customers.
• Use versioning: Use starting and ending dates to use different text versions at different times.

Docs  /  App  /  NAVAX Document Text  /  Setup
 Beginning and Ending Texts

Difference Between Beginning Texts and Ending Texts

• Greetings and introductions
• Validity notes for quotes
• General notes about the order
• Job descriptions

• Legal notes and terms and conditions references
• Closing greetings and contact information

How to Set Up Automatic Beginning and Ending Texts

Example 1: Beginning Text for Sales Quotes

Step-by-Step Guide: Creating the Beginning Text

1. Open the Standard Text Codes page via search.
   
   
2. Click New to create a new Extended Text.
3. Enter a Code, for example VALIDITY. This allows you to easily identify the Extended Text later.
4. Enter a Description, for example Validity Note. The description helps you recognize the purpose of the text.
5. Select the Beginning Text checkbox.
6. Click in the Extended Text Exists field or choose the Extended Texts action to go to the overview.
7. Click New to create a new Extended Text.
   
8. On the Extended Text page, you can make all settings for the text.
   
9. Enter the Text that should appear on the document. Example: This quote is valid until . Click in the Text field to open the text editor. There you can enter the text or paste it from other programs. For more information, see Advanced Features, Text Editor and Placeholders.
   
10. Optional: In the text editor, you can use placeholders for table fields. This allows you to automatically insert, for example, the quote's valid-to date (##Quote Valid To Date##) or the customer name (##Bill-to Name##). For more information, see Advanced Features, Text Editor and Placeholders.
11. On the Sales FastTab, activate the Sales Quote option. This makes the Extended Text available on sales quotes.
    

    Tip

    When you select or deselect multiple documents, a query appears asking whether you want to select or deselect all documents. Using the actions Belegfolgefelder deaktivieren and Belegfolgefelder deaktivieren, you can select or deselect all values at once.
12. Optional: Use the formatting options to customize the text (font type, size, color, paragraph alignment). For more information, see Advanced Features, Formatting.
13. Optional: Define additional conditions, for example the language or a validity period. This controls when the Extended Text is automatically inserted.
14. Save the Extended Text by closing the page. The changes are automatically applied.

Example 2: Ending Text for Sales Documents

Best Practices

• Maintain consistency: Use uniform wording for similar documents (e.g., all sales documents).
• Keep beginning texts short: Long beginning texts can distract from the essentials. Focus on what's important.
• Ending texts for legal notes: Place payment and delivery terms as well as terms and conditions references in ending texts.
• Use placeholders: Use placeholders for dynamic content such as date, customer name, or amounts.
• Consider multilingual: For international customers, create texts in different languages with corresponding language codes.
• Version control: Use validity periods to control different text versions over time.

Frequently Asked Questions

Can I have multiple beginning texts or ending texts in one document?

How do I manually insert a beginning text or ending text into a document?

Why doesn't my Extended Text appear in the document?

• Is the correct document type activated?
• Does the language code match the document?
• Is the current date within the validity period?
• Is NAVAX Document Text activated in the Document Text Setup?

Can beginning and ending texts be formatted?

Can I transfer beginning and ending texts from previous documents?

Usage Notes

• A list of available table fields can be found in the section Field Descriptions, Document Header Fields.
• Assign meaningful descriptions to make texts easier to find later.
• Use formatting sparingly to maintain readability.
• Test new texts in a test document before using them productively.

Docs  /  App  /  NAVAX Document Text  /  Setup
 Personalized Texts

Purpose of Personalized Texts

• Individual greetings - e.g., personal salutation for important customers
• Customer-specific notes - e.g., special delivery terms or agreements
• Contractual specifics - e.g., discount agreements, special conditions
• Legal information - e.g., specific terms and conditions for certain business partners
• Multilingual communication - e.g., texts in the customer's preferred language

Where Are Personalized Texts Set Up?

How to Create Personalized Texts

Example: Personalized Beginning Text for a Customer

Step-by-Step Guide

1. Open the card of the vendor, customer, or salesperson/purchaser for whom you want to set up a personalized text. For example: Customer 10000.
2. Click Beginning Text to open the Extended Text overview.
3. Click New to create a new Extended Text.
4. Enter the desired Code and a Description for the Extended Text. For example: Code: CUSTB10000, Description: Personalized text for Customer 10000
   
5. When you click on Ext. Text Exists, a list of available Extended Texts is displayed.
6. Click New to create a new Extended Text.
7. Enter the desired text in the Text field. For example: Dear Mr. Robert Townes, for the beginning text. For more information, see Advanced Features, Text Editor and Placeholders.
   
8. Optional: In the text editor, you can use placeholders for table fields. This allows you to automatically insert, for example, the customer's address (##Bill-to Address##) or customer name (##Bill-to Name##). For more information, see Advanced Features, Text Editor and Placeholders.
9. On the Sales FastTab, activate the Sales Quote option. This makes the Extended Text available on sales quotes.
   

   Tip

   When you select or deselect multiple documents, a query appears asking whether you want to select or deselect all documents. Using the actions Belegfolgefelder deaktivieren and Belegfolgefelder deaktivieren, you can select or deselect all values at once.
10. Optional: Define conditions, for example the language, validity period, or document types for which the Extended Text should apply. For more information, see Working with the App, Sorting and Conditions.
11. Optional: Use the formatting options to customize the text (font type, size, color, paragraph alignment). For more information, see Advanced Features, Formatting.
12. Save the Extended Text by closing the page. The changes are automatically applied.

Additional Examples

Personalized Ending Text for a Customer

• Customer: 20000 - Contoso Ltd.
• Ending Text: GREETING_CONTOSO
• Text Content: "Thank you for your long-standing loyalty! If you have any questions, your personal contact Mr. Mueller is available at mueller@example.com."

Personalized Beginning Text for a Vendor

• Vendor: 30000 - Supplier Ltd.
• Beginning Text: ORDER_SUPPLIER
• Text Content: "Please use our item numbers and descriptions in your order confirmation."

Personalized Text for a Salesperson

• Salesperson: BC - Benjamin Chiu
• Ending Text: CONTACT_BC
• Text Content: "Your contact: Benjamin Chiu, Phone: +43 123 456789, Email: b.chiu@example.com"

Best Practices

• Consider data privacy: Make sure that personalized texts do not contain sensitive information that should not appear on all documents.
• Use placeholders: Use placeholders for names and addresses to keep texts dynamic.
• Regular maintenance: Check personalized texts regularly, especially when contacts or conditions change.
• Unique codes: Use meaningful codes like CUST10000 instead of generic designations.
• Multilingual: Create texts in the language of international business partners with the appropriate language code.
• Test documents: Test personalized texts in test documents before using them productively.

Frequently Asked Questions

May the "Beginning Text" or "Ending Text" fields be activated in the text block?

What is the difference between personalized texts and general beginning/ending texts?

Can personalized texts be combined with general texts?

How can I use the same text for multiple customers?

What happens when I change the customer in the document?

Can I also manually change personalized texts in the document?

Usage Notes

• Detailed field descriptions can be found in the section Field Descriptions, Personalized Texts.
• Assign meaningful descriptions to make texts easier to find later.
• Use formatting sparingly to maintain readability. For more information, see Advanced Features, Formatting.
• Personalized texts are only displayed when the defined conditions are met. For more information, see Working with the App, Sorting and Conditions.
• Use the print preview of the document to check the result.
• Information about using placeholders can be found under: For more information, see Advanced Features, Text Editor and Placeholders.

Docs  /  App  /  NAVAX Document Text  /  Setup
 Line Texts

Purpose of Line Texts

• Items - e.g., care instructions, technical specifications, delivery notes, warranty conditions
• Resources - e.g., qualifications, availability, hourly rates, working hours
• G/L Accounts - e.g., explanations for fees, cost center assignments, posting notes
• Service Items - e.g., maintenance notes, service conditions, spare parts notes

Difference from Other Text Types

How to Create Line Texts

Example: Line Text for an Item

Step-by-Step Guide: Creating Line Texts

1. Open the Item Card for the desired item, for example 1896-S.
2. Click Extended Texts or in the Ext. Text Exists field to store an Extended Text.
   
3. Click New to create a new Extended Text.
4. The value in the No. field for the Extended Text is automatically taken from the item. This uniquely assigns the Extended Text to the item.
   
5. Enter a Description, for example Item text for 1896-S.
6. Enter the Text that should appear on the document. For example: Please note the care instructions on the packaging. Click in the Text field to open the text editor. There you can enter the text or paste it from other programs. For more information, see Advanced Features, Text Editor and Placeholders.
   
7. Optional: In the text editor, you can use placeholders for table fields. This allows you to automatically insert, for example, the quote date or customer name. For more information, see Advanced Features, Text Editor and Placeholders.
8. On the Sales FastTab, activate the Sales Quote option. This makes the Extended Text available on sales quotes.

   Tip

   When you select or deselect multiple documents, a query appears asking whether you want to select or deselect all documents. Using the actions Belegfolgefelder deaktivieren and Belegfolgefelder deaktivieren, you can select or deselect all values at once.
9. Optional: Define conditions, for example the language, validity period, or document types for which the Extended Text should apply.
10. Optional: Use the formatting options to customize the text (font type, size, color, paragraph alignment). For more information, see Advanced Features, Formatting.
11. Save the Extended Text by closing the page.
12. Back on the Item Card, you will see that the Ext. Text Exists field is set to Yes. For the text to be automatically inserted in new document lines, activate the Automatic Ext. Texts field.
    

Additional Examples

Line Text for a Resource

• Resource: Technician - Electrical
• Ext. Text Exists: Yes
• Automatic Ext. Texts: Activated
• Text Content: "Minimum booking duration: 2 hours. Travel costs are charged separately."

Line Text for a G/L Account

• G/L Account: 8900 - Shipping Costs
• Ext. Text Exists: Yes
• Automatic Ext. Texts: Activated
• Text Content: "Shipping via freight forwarder, insured up to 10,000 EUR. Delivery time: 3-5 business days."

Line Text for a Service Item

• Service Item: Annual Maintenance - Heating System
• Ext. Text Exists: Yes
• Automatic Ext. Texts: Activated
• Text Content: "Includes inspection, cleaning, and adjustment of the system. Duration approx. 2-3 hours."

Important Fields on Master Data Cards

Best Practices

• Selective activation: Only activate Automatic Ext. Texts for master data where the texts should really appear in every document.
• Use conditions: Use language codes and document type filters to display texts only for relevant documents.
• Brief and concise: Keep line texts short, as they appear directly below the lines and should not overload the document.
• Multilingual: Create Extended Texts in all required languages for international customers.
• Regular maintenance: Check the Extended Texts regularly for currentness, especially with product changes.
• Manual alternative: If Automatic Ext. Texts is not activated, users can manually insert the texts as needed via the Extended Texts action in the document line.
• Item attributes: For item-specific attributes, you can define additional Extended Texts. For more information, see Advanced Features, Item Attributes.

Usage Notes

• A list of available table fields for placeholders can be found in the section Field Descriptions, Document Lines Fields.
• Use formatting sparingly to maintain readability. For more information, see Advanced Features, Formatting.
• Line texts are only displayed when the defined conditions are met. For more information, see Working with the App, Sorting and Conditions.
• Use the print preview of the document to test the positioning and appearance.

Frequently Asked Questions

What happens when I add an item with automatic Extended Texts to a document?

Can I still change the automatically inserted texts in the document?

What if I don't activate "Automatic Ext. Texts"?

Can I have multiple Extended Texts for the same item?

Docs  /  App  /  NAVAX Document Text  /  Setup
 Miscellaneous Texts

Purpose of Miscellaneous Texts

General Business Terms

• Payment Terms - e.g., discount notes, payment deadlines, bank details
• Shipment Methods - e.g., shipping types, delivery times, packaging notes

Reminder Management

• Reminder Terms - e.g., reminder notes, consequences of payment delays
• Finance Charge Terms - e.g., interest calculations, legal notes

Service

• Service Order Types - e.g., standard notes for different service types
• Service Contract Groups - e.g., contract conditions, scope of services
• Standard Service Codes - e.g., descriptions for standard services

How to Create Miscellaneous Texts

Example: Extended Text for Payment Terms

Step-by-Step Guide: Creating Miscellaneous Texts

1. Open the Payment Terms page via search. Alternatively, you can access it from the Document Text Setup via the action.
   
2. Search for the desired term in the list of payment terms and click on it. In the example: 1M(8D) - 1 Month/2% Discount within 8 Days.
3. Click in the Standard Text Code field to create a new Extended Text.
   
4. The value in the No. field for the Extended Text is automatically taken from the payment terms. This uniquely assigns the Extended Text.
   
5. Enter a Description that describes the purpose of the text, for example 1M(8D).
6. Enter the Text that should appear on the document. Example: Payment is due within one month with 8 days discount. Click in the Text field to open the text editor. There you can enter the desired text or paste longer texts from other programs. For more information, see Advanced Features, Text Editor and Placeholders.
   
7. Optional: In the text editor, you can use placeholders for table fields. This allows you to automatically insert, for example, the quote date or customer name. For more information, see Advanced Features, Text Editor and Placeholders.
8. On the Sales FastTab, activate the Sales Quote option. This makes the Extended Text available on sales quotes.

   Tip

   When you select or deselect multiple documents, a query appears asking whether you want to select or deselect all documents. Using the actions Disable Sequel Fields and Activate Sequel Fields, you can deselect or select all values at once.
9. Optional: Define conditions, for example the language, validity period, or document types for which the Extended Text should apply.
10. Optional: Use the formatting options to customize the text (font type, size, color, paragraph alignment). For more information, see Advanced Features, Formatting.
11. Save the Extended Text by closing the page. The changes are automatically applied.

Additional Examples

Extended Text for Shipment Methods

• Shipment Method: FREIGHT
• Description: Shipping via Freight Forwarder
• Text Content: "Delivery is made to the curb via freight forwarder. Delivery time: 5-7 business days after order confirmation."

Extended Text for Reminder Terms

• Reminder Terms: REMINDER1
• Description: First Reminder
• Text Content: "Please settle the outstanding amount within 10 days. If you have questions about the invoice, contact us at accounting@example.com."

Extended Text for Service Order Types

• Service Order Type: MAINTENANCE
• Description: Maintenance Order
• Text Content: "Regular maintenance according to maintenance contract. Includes inspection, cleaning, and functional testing."

Accessing Miscellaneous Texts

Via Document Text Setup

1. Open the Document Text Setup via search in Business Central.
2. Choose the corresponding action in the Setup area:
   • Payment Terms
   • Shipment Methods
   • Reminder Terms
   • Finance Charge Terms
   • Service Order Types
   • Service Contract Groups
   • Standard Service Codes

Directly via the Respective Page

1. Open the respective page via search (e.g., Payment Terms).
2. Select the desired record.
3. Click in the Standard Text Code field or use the AssistEdit button.

Best Practices

• Consistent wording: Use uniform wording for similar Extended Texts.
• Legal review: Have texts with legal relevance (e.g., reminders, finance charge terms) reviewed by your legal department.
• Multilingual: Create Extended Texts in all required languages with corresponding language codes.
• Currentness: Check regularly whether payment and shipment terms are still current.
• Use placeholders: Use placeholders for dynamic content such as amounts or dates.
• Create test documents: Test new Extended Texts in test documents before using them productively.

Frequently Asked Questions

How can I use the same text for multiple payment terms?

Where do miscellaneous texts appear in the document?

Can I also manually add or remove miscellaneous texts in the document?

What happens when I change the payment terms in the document?

Usage Notes

• A list of available table fields for placeholders can be found in the section Field Descriptions, Miscellaneous Texts.
• Assign meaningful descriptions to make texts easier to find later.
• Miscellaneous texts are only displayed when the defined conditions are met. For more information, see Working with the App, Sorting and Conditions.
• Use formatting sparingly to maintain readability. For more information, see Advanced Features, Formatting.
• Use the print preview of the document to check the result.

Docs  /  App  /  NAVAX Document Text  /  Working with the App
 Using Beginning and Ending Texts

When Are Beginning and Ending Texts Used?

Automatic Insertion

• Corresponding Standard Text Codes are configured as beginning text or ending text
• The conditions are met (document type, language, period)
• You select a customer/vendor or change a document field

Manual Insertion

• Via the Beginning Text - current/following documents or Ending Text - current/following documents fields in the document header
• Via the Beginning Text or Ending Text actions in the ribbon
• Directly on the Document Text Lines page

Example: Beginning Text on a Sales Quote

Step-by-Step Guide: Automatic Insertion of Beginning and Ending Texts

1. Open the Sales Quotes page. You can find this via Tell me what you want to do or directly on the home page if you have the role Sales Order Processor.
2. Click on the desired sales Quote in the list. The detail view of the document opens.
3. Fill in the fields in the sales Quote header as usual, e.g., Customer Name, Address, Posting Date, and other relevant information. This information will later also be used for the automatic filling of beginning and ending texts. The assigned texts are automatically inserted as soon as you leave the Customer Name field or save the document header.
   In the Beginning Text - current/following documents field, the value changes to Yes | Yes or Yes | No.
   
4. Using the AssistEdit function, you can open the Document Text Lines page. There you can see all automatically inserted text lines and adjust them if necessary.
   
   
5. Optional: You can further edit the automatically inserted texts in the Text Editor, e.g., supplement or format them. For more information, see Advanced Features, Text Editor and Placeholders.

   Note

   Changes to the text in the document only affect this document, not the master data or other documents.
6. Optional: In the text editor, you can use placeholders for table fields. This allows you to automatically insert, for example, the quote date or customer name. In this example, a placeholder (##Quote Valid Until Date##) was used. The placeholder is automatically replaced with the actual value from the document. For more information, see Advanced Features, Text Editor and Placeholders.
7. Optional: Use the formatting options to design the text according to your preferences (font type, size, color, paragraph alignment). For more information, see Advanced Features, Formatting.
8. With the fields Sales Quote, Sales Order, Sales Shipment, Sales Invoice, Sales Proforma Invoice, and Sales Draft Invoice, you control on which documents the text should appear. Example: If you select Sales Invoice and post the document, the text appears on the posted invoice.
9. When you print the document as a preview, the document header displays, for example, This quote is valid until 01.01.2001. The date is automatically filled from the Quote Valid Until Date field.

Step-by-Step Guide: Changing or Manually Inserting Beginning and Ending Texts

1. Open the Sales Quotes page. You can find this via Tell me what you want to do or directly on the home page if you have the role Sales Order Processor.
2. Click on the desired sales Quote in the list. The detail view of the document opens.
3. Click on the Beginning Text - current/following documents field or select the Beginning Text action. You will go to the Document Text Lines page.
   
   
4. Click in the Text field to open the text editor. Enter the desired text, e.g., This quote is valid until . You can also paste longer texts from other programs.

   Note

   If the page from which the text editor is called is not editable or is not in edit mode, the text in the editor is also not editable.
   For more information, see Advanced Features, Text Editor and Placeholders.
5. Optional: In the text editor, you can use placeholders for table fields. This allows you to automatically insert, for example, the quote date or customer name. For more information, see Advanced Features, Text Editor and Placeholders.
6. Optional: Use the formatting options to customize the text (font type, size, color, alignment). For more information, see Advanced Features, Formatting.
7. Select the appropriate sequel document fields (Sales Quote, Sales Order, Sales Shipment, Sales Invoice, Proforma Invoice, Draft Invoice). This determines on which documents the text appears. Example: If you select Sales Invoice and post the document, the text appears on the posted invoice.
8. When you print the document as a preview, the document header displays, for example, This quote is valid until 01.01.2001. The date is automatically filled from the Quote Valid Until Date field.

Meaning of "Yes | No" in Text Fields

Practical Scenarios

Scenario 1: Automatic Texts for All Quotes

• Solution: Set up a Standard Text Code with Document Beginning Text enabled and select Sales Quote as the document type.
• Result: The text appears automatically on every new sales quote.

Scenario 2: Customer-Specific Greeting

• Solution: Store a personalized Standard Text Code in the Ending Text field on the customer card.
• Result: When this customer is selected, the personalized ending text is automatically inserted. For more information, see Setup, Personalized Texts.

Scenario 3: One-Time Notice for a Document

• Solution: Open the Document Text Lines from within the document and insert the text manually. Deactivate all sequel documents.
• Result: The text appears only on this document, not on posted follow-up documents.

Tips for Daily Work

• Use fields in the document header: The Beginning Text - current/following documents fields quickly show whether texts are present without having to open the document.
• Check texts before posting: Use the print preview to see how beginning and ending texts appear on the document.
• Disable automatic insertion: If you do not want texts to be automatically inserted, you can deactivate the Sales Quote, Sales Order, etc. fields in the document text lines.
• Control follow-up documents: Decide individually for each text whether it should also appear on follow-up documents (e.g., posted invoice).
• Copy texts: In the document text setup, you can specify whether texts should be copied when copying documents. For more information, see Advanced Features, Copy Documents.

Frequently Asked Questions

Why are my beginning or ending texts not automatically inserted?

• Is NAVAX Document Text activated in the document text setup?
• Is the Standard Text Code marked as Document Beginning Text or Document Ending Text?
• Are the Extended Texts activated for the correct document type (e.g., Sales Order)?
• Do the conditions (language, period) match the document?

Can I change automatically inserted texts in the document?

What does "Yes | No" mean in the Beginning Text - current/following documents field?

Can there be multiple beginning texts or ending texts in a document at the same time?

How do I remove an automatically inserted text from a document?

Are texts transferred to posted documents?

Troubleshooting

Problem: Texts appear twice

Problem: Texts appear on wrong documents

Problem: Placeholders are not replaced

Best Practices

Text Organization

• Beginning texts for greetings, introductions, general notes
• Ending texts for payment information, terms and conditions, closing phrases, legal notices
• Use several short text blocks instead of one very long text — better maintainability

Formatting and Readability

• Use formatting sparingly to preserve readability
• Highlight important information in bold
• Use spacing (pt) for better structure

Testing and Quality Assurance

• Test new texts in a test document before using them in production
• Check the print preview — the on-screen display may differ
• Test with different language codes when you use multilingual texts

Docs  /  App  /  NAVAX Document Text  /  Working with the App
 Using Personalized Texts

When Are Personalized Texts Used?

Automatic Insertion

• A Standard Text Code is stored as beginning text or ending text on the Customer Card, Vendor Card, or Salesperson/Purchaser Card
• You select the corresponding business partner in a document
• The defined conditions (document type, language, period) are met

Example: Personalized Beginning Text for VIP Customers

Step-by-Step Guide: Working with Personalized Texts

1. Open a document, e.g., a Sales Order. You can find this via Tell me what you want to do or directly on the home page.
2. In the Customer Name field, select a customer for whom a personalized text is set up (e.g., Customer 10000).
   The personalized texts are automatically inserted as soon as you leave the field or save the document header. In the field Beginning Text - current/following documents or Ending Text - current/following documents, the value changes to Yes | Yes or Yes | No.
3. To see the inserted texts, click on the field Beginning Text - current/following documents or select the action Beginning Text. The Document Text Lines page opens and shows all text lines for this document.
   
4. In the Standard Text Code column, you can see the code of the personalized text (e.g., VIP_GREETING).
5. Optional: You can edit the text in the document by clicking on the Text field. The Text Editor opens. For more information, see Advanced Features, Text Editor and Placeholders.

   Note

   Changes to the text in the document only affect this document, not the master data or other documents.
6. Optional: Check the print preview to see how the personalized text appears on the printed document.

Step-by-Step Guide: Changing Personalized Texts in Documents

1. Open the document whose personalized text you want to change.
2. Click on the field Beginning Text - current/following documents or Ending Text - current/following documents to open the Document Text Lines.
   
3. Click in the Text field of the line you want to change. The text editor opens.
   
4. Make the desired changes, e.g., additions for this specific case.
5. Optional: Adjust the formatting. For more information, see Advanced Features, Formatting.
6. Close the text editor. The changes are saved in the document.
7. Optional: If you want the text to also appear on subsequent documents (e.g., posted invoice), enable the corresponding fields such as Sales Invoice.

Practical Scenarios

Scenario 1: VIP Customer with Personalized Greeting

• Setup: A beginning text with a personalized greeting was stored on the customer card.
• Result: With every new sales document for this customer, the personal greeting appears automatically.
• Advantage: Consistent, professional communication without manual effort.

Scenario 2: Multilingual Business Partner

• Setup: Two extended texts with different language codes (EN and DE) were stored on the customer card.
• Result: Depending on the language code of the document, the appropriate language version appears automatically.
• Advantage: Automatic language selection, no manual switching necessary.

Scenario 3: Salesperson-Specific Contact Information

• Setup: An ending text with name, phone, and email is stored on each Salesperson/Purchaser Card.
• Result: The correct contact person appears automatically on all documents.
• Advantage: Customers always know who to contact.

Scenario 4: Vendor with Special Order Instructions

• Setup: A beginning text with the order instructions is stored on the vendor card.
• Result: Every order to this supplier automatically contains the required instructions.
• Advantage: Avoidance of inquiries and delays.

Tips for Daily Work

• Quick check: The fields Beginning Text - current/following documents show at a glance whether personalized texts are present.
• Use print preview: Before sending, check how personalized texts appear on the printed document.
• Adjust texts as needed: For special cases, you can change personalized texts directly in the document without affecting the master data.
• Change customer: If you change the customer in the document, the personalized texts are automatically updated.
• Combination with general texts: Personalized texts can be combined with general beginning/ending texts - the sorting order determines the sequence.

Frequently Asked Questions

What happens if I change the customer in the document?

Can general and personalized texts be in the document at the same time?

Can I use the same personalized text for multiple customers?

Troubleshooting

Why does my personalized text appear on all documents?

Problem: Personalized Texts Appear Twice

Problem: Text Appears in Wrong Language

Best Practices

Organizing Personalized Texts

• Use consistent naming conventions for Standard Text Codes (e.g., CUST_[Number], SALES_[Abbreviation])
• Document in the Description of the Standard Text Code which business partner the text is intended for
• Use shared extended texts for multiple business partners with similar requirements

Content Design

• Keep personalized texts up to date - regularly check whether contact persons or conditions are still correct
• Use placeholders for dynamic content instead of fixed values (e.g., ##Customer Name## instead of "Mr. Smith")
• Ensure a professional tone that fits your company and the business partner

Multilingualism and Internationalization

• Create extended texts in all required languages for international business partners
• Use the Language Code to automatically use the correct language version
• Consider cultural differences in greetings and tone

Testing and Quality Assurance

• Always test new personalized texts in a test document before using them in production
• Check the print preview - screen display may differ from print
• Test the transfer to subsequent documents by posting a test document
• When using placeholders: Ensure that all fields are filled

Docs  /  App  /  NAVAX Document Text  /  Working with the App
 Using Line Texts

What Are Line Texts?

• Product descriptions - e.g., technical specifications, care instructions
• Delivery information - e.g., delivery time, availability
• Notes - e.g., handling, safety instructions
• Resource details - e.g., qualifications, availability
• Account explanations - e.g., fee descriptions

When Are Line Texts Used?

Automatic Insertion

• On the master data card (item card, resource card, etc.) the Automat. Ext. Texts field is enabled
• Corresponding Extended Texts are set up
• The conditions are met (document type, language, period)
• You add an item, resource, G/L account, or service item to the document line

Manual Insertion

• Via the Line Text field in the document line
• Via the Line action > Line Texts in the ribbon
• Directly on the Document Text Lines page

Example: Line Text on a Sales Order

Step-by-Step Guide: Automatic Insertion of Line Texts

1. Open the Sales Orders page. You can find this via Tell me what you want to do? or directly on the home page if you have the role Sales Order Processor.
2. Click on the desired sales order in the list. The detail view of the document opens.
3. Fill in the fields in the sales order header as usual
4. Create a line with Type Item, select the desired item and add it, e.g., Item 1896-S.
5. As soon as you leave the No. or Description field, the line texts are inserted
6. Using the AssistEdit function of the Line Text field, you can open the Document Text Lines page. There you can see all automatically inserted line texts and adjust them if necessary.
   
   
7. Optional: You can further edit the automatically inserted texts in the Text Editor, e.g., supplement or format them. For more information, see Advanced Features, Text Editor and Placeholders.
   
8. Optional: In the text editor, you can use placeholders for table fields of the document line. This allows you to automatically insert, for example, the Description or the GTIN. For more information, see Advanced Features, Text Editor and Placeholders.
9. Optional: Use the formatting options to design the text according to your preferences (font type, size, color, paragraph alignment). For more information, see Advanced Features, Formatting.
10. With the fields Sales Quote, Sales Order, Sales Shipment, Sales Invoice, Sales Proforma Invoice, and Sales Draft Invoice, you control on which documents the text should appear. Example: If you select Sales Invoice and post the document, the text appears on the posted invoice.
11. When you print the document as a preview, below the item line, for example, Please note the care instructions on the packaging. is displayed. The date is automatically filled from the Quote Valid Until Date field.

Step-by-Step Guide: Changing or Manually Adding Line Texts

1. Open the Sales Orders page. You can find this via Tell me what you want to do or directly on the home page if you have the role Sales Order Processor.
2. Click on the desired sales order in the list. The detail view of the document opens.
3. Click on the Line Text field or select the Line action, Line Texts. You will go to the Document Text Lines page.
   
   
4. Click in the Text field to open the text editor. Enter the desired text, e.g., Please note the care instructions on the packaging. You can also paste longer texts from other programs. For more information, see Advanced Features, Text Editor and Placeholders.
   

   Note

   If the page from which the text editor is called is not editable or is not in edit mode, the text in the editor is also not editable.
5. Optional: In the text editor, you can use placeholders for table fields. This allows you to automatically insert, for example, the Description or the GTIN. For more information, see Advanced Features, Text Editor and Placeholders.
6. Optional: Use the formatting options to customize the text (font type, size, color, alignment). For more information, see Advanced Features, Formatting.
7. Select the appropriate fields (Sales Quote, Sales Order, Sales Shipment, Sales Invoice, Proforma Invoice, Draft Invoice). This determines on which documents the text appears. Example: If you select Sales Invoice and post the document, the text appears on the posted invoice.
8. When you print the document as a preview, below the item line, for example, Please note the care instructions on the packaging. is displayed. The date is automatically filled from the Quote Valid Until Date field.

Practical Scenarios

Scenario 1: Automatic Care Instructions for Textiles

• Solution: Set up an Extended Text with care instructions for each item and enable Automatic Ext. Texts on the item card.
• Result: When adding the item, the text appears automatically below the item line.

Scenario 2: Resource-Specific Notes

• Solution: Store an Extended Text with the qualifications on the resource card.
• Result: When this resource is selected, the text is automatically inserted below the resource line.

Scenario 3: One-Time Note for an Item Line

• Solution: Open the Document Text Lines via the Line Text field and insert the text manually.
• Result: The text appears only below this specific item line in this document.

Scenario 4: G/L Account Explanations

• Solution: Set up an Extended Text on the G/L account card for shipping costs.
• Result: When using the G/L account, the explanation appears automatically.

Tips for Daily Work

• Check Line Text field: A symbol or value in the Line Text field shows whether texts exist for this line.
• Check texts before posting: Use the print preview to see how line texts appear on the document.
• Use automatic insertion selectively: Enable Automatic Ext. Texts only for items/resources where the text should really appear in every document.
• Manual alternative: If Automatic Ext. Texts is not enabled, you can insert texts manually as needed via the Line Texts action.
• Control follow-up documents: Decide individually for each text whether it should also appear on follow-up documents (e.g., posted invoice).
• Multiple Extended Texts: You can create multiple Extended Texts for the same item with different conditions (e.g., different languages). For more information, see Working with the App, Sorting and Conditions.
• Item attributes: NAVAX Document Text offers the ability to use line texts for item attributes. For more information, see Advanced Features, Item Attributes.

Frequently Asked Questions

Why are my line texts not automatically inserted?

• Is NAVAX Document Text activated in the document text setup?
• Is the Automatic Ext. Texts field enabled on the master data card?
• Are the Extended Texts activated for the correct document type (e.g., Sales Order)?
• Do the conditions (language, period) match the document?

Can I change automatically inserted line texts in the document?

Where exactly do line texts appear in the document?

Can there be multiple line texts below an item line?

How do I remove an automatically inserted line text?

Are line texts transferred to posted documents?

What is the difference between line texts and beginning/ending texts?

Troubleshooting

Problem: Line texts appear for all items, although configured for only one

Problem: Texts for different items are identical

Problem: Line texts do not appear in the correct language

Problem: Placeholders in line texts are not replaced

Best Practices

Text Organization

• Create separate text modules for different items or item groups to ensure flexibility.
• Use meaningful names for standard text codes so you can see at a glance what the text is used for.
• Use sorting in text modules to control the order of multiple line texts.

Formatting and Readability

• Use placeholders for dynamic content such as quantity, unit, or delivery date.
• Use formatting (bold, italic) sparingly and purposefully for important information.
• Ensure consistent text design across all items.

Docs  /  App  /  NAVAX Document Text  /  Working with the App
 Using Miscellaneous Texts

What Are Miscellaneous Texts?

Business Terms:

• Payment Terms (e.g., payment period and discount)
• Shipment Methods (e.g., shipping method, Incoterms)
• Shipping Agents (e.g., delivery notes)

Reminders:

• Reminder Terms (e.g., legal notices)
• Finance Charge Terms (e.g., interest rates)

Service:

• Service Order Types (e.g., maintenance notes)
• Service Contract Groups (e.g., contract conditions)

When Are Miscellaneous Texts Used?

How to Use Miscellaneous Texts in Documents

Example: Payment Terms Text on a Sales Order

Step-by-Step: Automatic Insertion of Miscellaneous Texts

1. Open the Sales Orders page. You can find it via Tell me what you want to do or directly on the home page if you have the Sales Order Processor role.
2. Click on the desired sales order in the list. The detail view of the document opens.
3. Fill in the fields in the sales order header as usual
4. Select the desired payment terms, e.g.: 1M(8D).
5. As soon as you leave the Payment Terms Code field, the payment terms texts are inserted
6. Using the AssistEdit function of the Payment Terms Text field, you can open the Document Text Lines page. There you can see all automatically inserted payment terms texts and adjust them if necessary.
   
   
7. Optional: You can further edit the automatically inserted texts in the Text Editor, e.g., add or format them. For more information, see Advanced Features, Text Editor and Placeholders.
8. Optional: In the text editor, you can use placeholders for table fields of the document header. This allows you to automatically insert, for example, the Posting Date or the Order Date. For more information, see Advanced Features, Text Editor and Placeholders.
9. Optional: Use the formatting options to design the text according to your preferences (font type, size, color, paragraph alignment). For more information, see Advanced Features, Formatting.
10. With the fields Sales Quote, Sales Order, Sales Shipment, Sales Invoice, Sales Proforma Invoice, and Sales Draft Invoice, you control on which documents the text should appear. Example: If you select Sales Invoice and post the document, the text appears on the posted invoice.
11. When you print the document as preview, the document header displays, for example, Payment is due within one month with 8 days discount. below the payment terms.

Step-by-Step: Changing or Manually Inserting Miscellaneous Texts

1. Open the Sales Orders page. You can find it via Tell me what you want to do or directly on the home page if you have the Sales Order Processor role.
2. Click on the desired sales order in the list. The detail view of the document opens.
3. Click on the Payment Terms Text field, you will go to the Document Text Lines page.
   
   
4. Click in the Text field to open the text editor. Enter the desired text, e.g., Payment is due within one month with 8 days discount. You can also paste longer texts from other programs. For more information, see Advanced Features, Text Editor and Placeholders.

   Note

   If the page from which the text editor is called is not editable or is not in edit mode, the text in the editor is also not editable.
5. Optional: In the text editor, you can use placeholders for table fields. This allows you to automatically insert, for example, the Posting Date or the Order Date. For more information, see Advanced Features, Text Editor and Placeholders.
6. Optional: Use the formatting options to customize the text (font type, size, color, alignment). For more information, see Advanced Features, Formatting.
7. Select the appropriate fields (Sales Quote, Sales Order, Sales Shipment, Sales Invoice, Proforma Invoice, Draft Invoice). This determines on which documents the text appears. Example: If you select Sales Invoice and post the document, the text appears on the posted invoice.
8. When you print the document as preview, the document header displays, for example, Payment is due within one month with 8 days discount.

Practical Scenarios

Scenario 1: Payment Terms with Discount Note

• Solution: Set up an extended text for payment terms "1M(8D)" with text such as "We grant 2% discount if paid within 8 days."
• Result: As soon as you select payment terms "1M(8D)" in the sales order, the text is automatically inserted.

Scenario 2: Shipment Methods for Export

• Solution: Create an extended text for shipment method "EXW" with an explanation of the delivery conditions.
• Result: The text appears automatically in the document when the shipment method is selected.

Scenario 3: Reminder Notes by Reminder Level

• Solution: Set up separate extended texts for each reminder level with adjusted wording.
• Result: Depending on the reminder level, the appropriate text appears automatically on the reminder.

Scenario 4: Service Order Types with Maintenance Notes

• Solution: Create an extended text for service order type "Maintenance" with the maintenance notes.
• Result: When the service order type is selected, the notes are automatically inserted.

Tips for Daily Work

• Check texts before posting: Use the print preview to see how the texts appear on the document.
• Customer-specific adjustments: You can manually adjust automatically inserted texts for individual documents without changing the master data.
• Use multilingualism: Set up extended texts for different languages that are automatically inserted depending on the document language. For more information, see Working with the App, Sorting and Conditions.
• Control follow-up documents: Decide for each text on which follow-up documents it should appear (e.g., only on invoice, not on shipment).
• Use placeholders: Use placeholders such as ##Posting Date## or ##Order Date## to insert dynamic content. For more information, see Advanced Features, Text Editor and Placeholders.

Frequently Asked Questions

Why are my miscellaneous texts not automatically inserted?

• Is NAVAX Document Text activated in the document text setup?
• Is the extended text activated for the correct document type (e.g., Sales Order, Sales Invoice)?
• Is the payment term/shipment method etc. correctly linked to the Standard Text Code?
• Do the conditions (language, period) match the document?

Can I change automatically inserted miscellaneous texts in the document?

Where do miscellaneous texts appear in the document?

Can multiple miscellaneous texts be in a document at the same time?

How do I remove an automatically inserted miscellaneous text?

Are miscellaneous texts transferred to posted documents?

What is the difference between miscellaneous texts and beginning/ending texts?

Troubleshooting

Problem: Text appears on wrong document type

Problem: Text is empty even though extended text exists

Problem: Placeholders are not replaced

Problem: Texts appear in wrong language

Best Practices

When to Use Miscellaneous Texts

• Use miscellaneous texts for context-dependent information that relates to payment terms/shipment methods, shipping agents, etc.
• Use this text type for standardized notes that should be automatically inserted depending on the selected method.
• Combine miscellaneous texts with beginning/ending texts and line texts for comprehensive document texts.

Master Data Configuration

• Maintain extended texts centrally on the master data cards (payment terms, shipment methods, etc.).
• Create language-specific variants for international business partners.
• Use meaningful names for Standard Text Codes so that the assignment is clearly recognizable.

Formatting and Testing

• Use placeholders for dynamic content such as due date or discount amount.
• Use formatting sparingly for important information.
• Test new texts in a test document with different combinations of payment terms/shipment methods.

Docs  /  App  /  NAVAX Document Text  /  Working with the App
 Sorting and Conditions

Language Conditions

• Language-independent: A text is always inserted regardless of the document language - All Languages (e.g., general delivery terms).
• Specific language: A text appears only for documents in a specific language - Language Code (e.g., English export notice only for language code ENU).
• Multiple language variants: Different texts are stored for the same purpose, which are inserted independently of the document language - Language Code and All Languages remain empty (e.g., warranty text in German and English).

Validity Conditions

• Valid from Starting Date: A text is inserted if the document date is after a specific date - Starting Date (e.g., new regulations from 01/01/2026).
• Limited until Ending Date: An extended text is only inserted if the document date is before a specific date - Ending Date (e.g., only valid until 12/31/2025).
• Campaign period: A notice text appears only for documents within a defined time period - Starting Date and Ending Date (e.g., Christmas campaign from 12/01/2025 to 12/31/2025).

Document Conditions

• Only for specific document type: A text is only inserted for sales invoices, not for quotes or orders (e.g., payment notice only on invoices).
• Automatically on subsequent documents: A text is automatically transferred from quote to order, invoice, and credit memo (e.g., project notice consistently on all documents).

Sorting Order

• Beginning texts: With Sorting Order 10 are inserted first.
• Customer-specific texts: With Sorting Order 20 appear afterwards.
• Processor texts: With Sorting Order 30 are added last (e.g., salesperson-specific notes).

Setting Up Conditions

1. Open the Standard Text Codes page via the search in Business Central.
2. Select the desired Standard Text Code and open the associated texts via the Extended Texts action.
3. Select the desired extended text or create a new one.
4. In the General FastTab, you will find the following fields:
   • Language Code: Specify for which language the text applies (empty = language-independent).
   • Starting Date: The text is only inserted from this date (empty = no starting date).
   • Ending Date: The text is only inserted until this date (empty = no ending date).
   • Sorting Order: Specify the order in which multiple extended texts appear (see Sorting Order).
5. Select the document type - restrict usage to specific document types (e.g., only invoice).
6. Save the settings. The extended text will now be automatically inserted only when all defined conditions are met.

Best Practices

Use Language Variants Wisely

• Create corresponding text variants for all important business languages
• Use All Languages = yes for a fallback variant (e.g., English)
• Test your language variants with documents in different languages
• Maintain language variants centrally to ensure consistency

Use Time Periods Effectively

• Plan seasonal texts (e.g., Christmas, summer break) in advance
• Use Starting Date for new legal regulations
• Set Ending Date for limited campaigns or expiring regulations
• Regularly review expiring texts and update them

Assign Sorting Order Systematically

• Assign sorting orders in steps of 10 (10, 20, 30...) to be able to insert texts in between later
• Define a fixed strategy: e.g., General (10), Customer (20), Salesperson (30)
• Document your sorting logic for the team
• Lower values = higher priority (appear first)

Select Document Types Strategically

• Payment notices only on invoices, not on quotes
• General terms and conditions consistently on all documents
• Job-specific notes on all job-related subsequent documents
• Enable only the document types that are really needed

Frequently Asked Questions

What happens if multiple extended texts meet the same conditions?

How does the language selection work with "All Languages"?

Can I combine conditions?

Common Problems

Problem: Text does not appear, although all conditions seem to be met

• Check all fields in the General FastTab: Language Code, Starting Date, Ending Date, All Languages
• Check in the FastTabs (Sales, Purchase, Service, Job) whether the desired document type is enabled
• Verify that the document date is within the defined time period

Problem: Texts appear in wrong order

• Open the Extended Texts and check the Sorting Order field
• Lower values appear first - adjust the values accordingly

Docs  /  App  /  NAVAX Document Text  /  Working with the App
 Example Scenarios

Structure of Examples

• Basic Functions: Line texts for G/L accounts, resources, and personalized texts
• Advanced Functions: Item attributes, multilingual texts, time period conditions
• Complex Scenarios: Combination of multiple features for special requirements

Basic Functions

Example 1: Line Text for a G/L Account

1. Open the Chart of Accounts page and select the desired G/L account.
2. Click Extended Texts or in the Ext. Text Exists field and select an extended text. Alternatively, you can create a new extended text with the New action.
   
3. Enter the desired text, e.g., "This G/L account is reserved for internal postings."
4. Activate Automatic Ext. Texts so that it is automatically inserted in new document lines.
5. Create a document line of type G/L Account in, e.g., a sales invoice, the line text appears automatically in the document line.

Example 2: Line Text for a Resource

1. Open the Resources page and select the desired resource.
2. Click Extended Texts or in the Ext. Text Exists field and select an extended text. Alternatively, you can create a new extended text with the New action.
   
3. Enter a notice text, e.g., "This resource is certified for system maintenance with ISO-XYZ."
4. Activate Automatic Ext. Texts so that it is automatically inserted in new document lines.
5. Create a service order line of type Resource, the line text appears automatically in the document line.

Example 3: Personalized Beginning Text for a Salesperson/Purchaser

1. Open the Salespeople/Purchasers page and select the desired person.
2. Click Beginning Text and select an extended text. Alternatively, you can create a new extended text with the New action.
   
3. Enter an individual text, e.g., "Your contact for inquiries: Bernhard Köhler."
4. Save the extended text.
5. Create a sales or purchase document where this salesperson/purchaser is assigned. The personalized text appears in the document header.

Example 4: Miscellaneous Text for a Service Contract Group

1. Open the Service Contract Groups page and select the desired type.
2. Click Extended Texts or in the Ext. Text Exists field and select an extended text. Alternatively, you can create a new extended text with the New action.
   
3. Add a notice text, e.g., "For Vaillant customers in this service contract group, extended maintenance intervals and special service benefits apply according to manufacturer agreement."
4. Save the extended text.
5. Create a service contract quote with this type. The extended text appears in the order in the document header.

Advanced Functions

Example 5: Linking Item Attributes with Texts

1. Open the Item Attributes page and select the attribute "Material"
2. Click Attribute Values and select the value "Leather"
3. Click Extended Texts and create a new extended text with the care instructions: "Care instructions for leather products: Please treat only with special leather care products. Do not wash."
4. Activate the desired document types (e.g., Sales Invoice, Sales Shipment)
5. When you now insert an item with Material="Leather" into a document, the care instructions appear automatically below the item line

Example 6: Multilingual Beginning and Ending Texts

1. Open the Customer Card of the customer
2. Click Beginning Text and create two extended texts:
3. German Text:
   • Set Language Code = DEA (or DEU)
   • Text: "Sehr geehrte Damen und Herren, vielen Dank für Ihre Bestellung."
4. English Text:
   • Set Language Code = ENU
   • Text: "Dear Sir or Madam, thank you for your order."
5. Fallback for other languages:
   • Create a third extended text
   • Activate All Languages = Yes
   • Text: "Dear Customer, thank you for your order."
6. Business Central automatically selects the appropriate text based on the document's language code.

Example 7: Time-Limited Campaign Notice

1. Open the Standard Text Codes page
2. Create a new Standard Text Code, e.g., "XMAS2025"
3. Create an extended text with the following text: "Christmas Campaign: Order by 24.12.2025 and receive 10% discount on your entire order!"
4. Set the time period conditions:
   • Starting Date: 01.12.2025
   • Ending Date: 24.12.2025
5. Activate the desired document types in the Sales FastTab (e.g., Sales Quote)
6. Link this Standard Text Code to the desired customer or all customers
7. The campaign notice appears only on documents with a date within the defined period

Example 8: Placeholders for Dynamic Content

1. Open the Customer Card
2. Create a Beginning Text and open the Text Editor
3. In the text editor, click the action Insert Placeholder
4. A list opens with all available fields of the respective document
5. Select the desired fields (e.g., Bill-to Name and Order Date) - they are automatically inserted into the text enclosed in ##
6. Your text might then look like this: "Dear ##Bill-to Name##,
   Thank you for your order dated ##Order Date##. We confirm receipt as follows."
7. The placeholders are automatically replaced with the actual values when inserted into the document

Complex Scenarios

Example 9: Combination of Multiple Conditions

1. Open the Standard Text Codes page and create a new code "EXPORT-INFO"
2. Create an extended text with the export notice: "Export Notice: This shipment is subject to customs regulations. Please ensure all documentation is complete."
3. Configure the conditions:
   • Language Code: ENU (English)
   • Starting Date: 01.01.2026 (new export regulations)
   • Ending Date: blank (valid indefinitely)
4. Activate only the document type Sales Invoice in the Sales FastTab
5. Link this text to customers who are export customers
6. The notice appears only when all conditions are met:
   • Document language = ENU
   • Document date ≥ 01.01.2026
   • Document type = Sales Invoice

Example 10: Multi-Level Sorting of Texts

1. Create three different extended texts for a customer:
2. Greeting (Sorting Sequence: 10) "Dear ##Bill-to Name##,"
3. General Notice (Sorting Sequence: 20) "Thank you for your trust and we confirm your order as follows."
4. Delivery Notice (Sorting Sequence: 30) "Delivery will be made within 5 working days after order receipt."
5. Create a sales order for this customer
6. The texts appear in the document in the order defined by the sorting sequence:
   • 1. Greeting (10)
   • 2. General Notice (20)
   • 3. Delivery Notice (30)

7. Tip

   Use increments of 10 to be able to insert texts in between later

Tips from Examples

• Test first: Create test documents to verify results before using texts in production
• Use placeholders: Dynamic content makes your texts more flexible and personal
• Plan multilingually: Create text variants for all relevant languages from the start
• Check time periods: Regularly review expiring texts and update them in time
• Plan sorting: Define clear sorting logic and document it for your team
• Use item attributes: Instead of maintaining texts for each item individually, use attributes for groups
• Test combinations: For complex conditions, test all possible cases
• Documentation: Document complex configurations for maintenance

Docs  /  App  /  NAVAX Document Text  /  Working with the App
 FAQ and Troubleshooting

Why don't my texts appear on the document?

1. Text type correctly assigned: Ensure that the text is correctly classified as beginning text, ending text, or line text.
2. Check document type: Check in the FastTabs Sales, Purchase, Service, or Job whether the corresponding document type is enabled.
3. Check language code: If a Language Code is stored, the text is only displayed for documents with this language code. Use All Languages = yes for language-independent texts.
4. Check validity period: Check the Starting Date and Ending Date fields. The text only appears if the document date is within this period.
5. Automatic insertion enabled: Check whether the option for automatic insertion is enabled in the setup.

How do I find the right extended text?

1. Open the Standard Text Codes page via the search.
2. Use the filter function to search for specific codes or descriptions.
3. Open the associated texts via the Extended Texts action.
4. In the list, you will see all variants with their conditions (language code, time period, document type).
5. Use the Language Code, Starting Date, Ending Date columns to filter for the correct variant.

How do I edit existing texts on a document?

1. Before posting: Open the document and navigate to the document text lines. There you can directly edit, delete, or add new texts.
2. After posting: For posted documents, you can edit texts as long as the document has not yet been printed. The preview function does not lock editing. After the first actual print, no more changes are possible.
3. Change master data: To permanently change texts, open the Standard Text Codes page via the search in Business Central. Select the desired code and open the associated texts via the Extended Texts action. The change then applies to all future documents.

How can I prepare texts for future documents?

1. Open the Standard Text Codes page via the search in Business Central. Select the desired code and open the associated texts via the Extended Texts action. Create a new extended text.
2. Set a Starting Date in the future (e.g., for a campaign from 01/01/2026).
3. Optional: Also set an Ending Date if the text should only be valid for a limited time.
4. Define all other conditions (language code, document type, sorting order).
5. Save the extended text. It will automatically appear on new documents from the starting date.

Use case:

What to do with text display or formatting problems?

1. Line breaks: Use multiple text lines instead of very long lines for better readability.
2. Formatting: Use the available formatting options (bold, italic, color) sparingly.
3. Check placeholders: Verify that placeholders are correctly written (e.g., ##Bill-to Name##).
4. Text length: Pay attention to the maximum character count per line (standard: 1024 characters).
5. Print preview: Use the print preview to check the display before sending the document.

How can I adjust or extend the text length?

1. Multiple lines: Distribute long texts across multiple text lines within an extended text.
2. Multiple extended texts: Use multiple extended texts with different Sorting Orders to arrange texts in the desired order.

How can I use extended texts for different document types?

1. Navigate to the FastTabs Sales, Purchase, Service, or Job.
2. Enable all desired document types (e.g., Quote, Order, Invoice).
3. Optional: Use the option for Subsequent documents to automatically transfer texts from quote to invoice.

How do I set up multilingual texts?

1. Open the Standard Text Codes page via the search in Business Central. Select the desired code and open the associated texts via the Extended Texts action. Create multiple extended texts for the same Standard Text Code.
2. Assign each extended text the corresponding Language Code (e.g., DEU, ENU, FRA).
3. Optional: Create an additional extended text with All Languages = yes as a fallback for undefined languages.
4. The system automatically selects the appropriate text based on the language code of the customer/vendor.

Example:

How do I copy documents with texts?

1. Use the standard Copy Document function in Business Central
2. If the Copy Documents with Texts option in the Document Text Setup is set to On Request, a query appears
3. Select which texts should be copied:
   • Beginning/Ending Texts: Copies header and footer texts
   • Line Texts: Copies position-related texts
4. Both options can be combined

Can I permanently change the copy function?

• Always: All texts are automatically copied without prompt
• On Request: You decide for each copy operation (recommended)
• Never: Texts are never copied

Are texts from archived documents also copied?

Does copying differ between sales and purchase documents?

Troubleshooting

Setup and Installation

Problem: Document Text Setup is not visible

• Check in the Extension Management whether NAVAX Document Text is installed
• Ensure you have the NVXDT, SETUP permission
• Sign out and sign in again to update permissions

Problem: No menu items appear after installation

• Open the Extension Management and check the status
• Search for "NCDT" or "Document Text" in "Tell me what you want to do"
• If nothing is found: reinstall the extension

Extended Texts Are Not Inserted

Problem: Beginning texts do not appear on sales orders

• Check whether the Sales FastTab in the extended text has the Sales Order document type enabled
• Check the customer's Language Code and compare with the extended text
• Check Starting Date and Ending Date - is the order date within the valid period?
• Ensure that NAVAX Document Text is enabled in the setup

Problem: Line texts for items do not appear automatically

• Open the Item Card
• Check whether the Automatic Ext. Texts field is enabled
• Verify that an extended text is stored (Ext. Text Exists field)
• Check in the extended text whether the desired document type is enabled

Problem: Miscellaneous texts (payment terms) do not appear

• Open the Payment Terms page
• Select the desired payment term
• Check the Standard Text Code field - is a code stored?
• Check in the Standard Text Code whether an extended text with the correct document type exists

Conditions and Sorting

Problem: Texts appear in wrong order

• Open the Extended Texts of the relevant Standard Text Code
• Check the Sorting Order field - lower values appear first
• Adjust the values: use steps of 10 (10, 20, 30...)
• Create a test document for verification

Problem: Text does not appear only for certain customers

• Check the customer's Language Code
• Verify whether the extended text has a variant for this language code
• If necessary, create a variant with All Languages = Yes as a fallback
• Check whether a personalized text exists for this customer that overrides the general text

Problem: Time-limited text does not appear

• Check Starting Date and Ending Date in the extended text
• Compare with the Order Date or Document Date (not Posting Date!)
• Ensure that Starting Date ≤ Document Date ≤ Ending Date

Formatting and Display

Problem: Placeholders are not replaced

• Check the exact spelling: ##FieldName## (with double hash marks)
• Field must exist in the corresponding table:
  • Document header: Field Descriptions, Document Header FieldsAvailable fields
  • Document lines: Field Descriptions, Document Lines FieldsAvailable fields
• Note case sensitivity and spaces in the field name

Problem: Formatting does not appear in print

• Ensure you are using a NAVAX report layout For more information, see Advanced Features, Report Layout Selection.
• Check in the Document Text Setup whether HTML formatting is enabled
• Use the Print Preview to test the formatting

Problem: Text is truncated or too long

• Split long texts across multiple text lines
• Use multiple extended texts with different sorting orders
• Maximum length per line: 1024 characters

Printing and Reports

Problem: Texts do not appear in the printed document

• Open the Report Layout Selection page
• Select the NAVAX layouts for the desired documents
• List of supported reports: For more information, see Advanced Features, Report Layout Selection.

Problem: Texts appear on screen but not in PDF

• Check the Report Layout Selection for the respective document type
• Ensure that the NAVAX layout is selected for both preview and print
• Test with Print > PDF Preview instead of just screen preview

Problem: Posted documents show no texts

• Open the extended text
• Enable the subsequent document types in the corresponding FastTab (e.g., Sales Invoice for posted invoices)
• The change only applies to future documents - already posted documents are not updated

Personalized and Special Texts

Problem: Personalized texts do not appear even though stored on the master data card

• Check whether the correct document types are enabled in the extended text (e.g., Sales Order)
• Verify that the extended text’s Language Code matches the document language
• Check Starting Date and Ending Date — is the document date within the validity period?
• Ensure that NAVAX Document Text is enabled in the Document Text Setup

Problem: Personalized text does not appear on posted documents

• Before posting, open the document’s document text lines
• Enable the desired subsequent documents (e.g., Sales Invoice)
• Alternatively: Adjust the default setting in the Standard Text Code on the master data card

Problem: Personalized text appears on wrong document types

• Open the Standard Text Code from the master data card
• Check the Sales, Purchase, Service FastTabs
• Disable the unwanted document types

Problem: How do I recognize whether a text is personalized?

• In the document text lines you see the Standard Text Code column with the code
• If this code is stored on a Customer Card, Vendor Card, or Salesperson/Purchaser Card, it is a personalized text

Problem: Personalized texts do not override general texts

• Personalized texts need a lower Sorting Order than general texts
• Example: Personalized text = 10, General text = 20
• Both texts will appear — if you only want the personalized one, disable the general text for this customer

Problem: Can I use the same personalized text for multiple customers?

• Yes, create a Standard Text Code
• Reference it in the Beginning Text or Ending Text fields on multiple Customer Cards
• This way, multiple customers share the same text

Problem: Placeholders in the personalized text are not replaced

• Check the exact spelling (format: ##FieldName##)
• Use the placeholder function in the text editor
• Available fields can be found under Field Descriptions, Personalized Texts

Item Attribute Texts

Problem: Item attribute texts do not appear

• Check on the Item Card whether the attribute is assigned with the correct value
• Open Item Attributes > Attribute Values > Extended Texts
• Verify that an extended text exists for this value and the document type is enabled

Copying Documents

Problem: Only part of the texts were copied

• Repeat the copy operation and activate both options
• Or add the missing texts manually

Problem: Texts are copied unwantedly

• Switch to On Request or Never in the Document Text Setup
• Alternatively, you can manually delete the unwanted texts after copying

Problem: Copied texts do not fit the new document type

• Create corresponding extended texts with conditions for the new document type
• Or adjust the copied texts manually

Problem: Placeholders show incorrect values after copying

• This is the expected behavior
• If you want to keep the original value, replace the placeholder with fixed text before copying

Problem: Texts are missing when copying posted documents

• Add missing texts manually
• Or use the unposted original document as a copy template, if still available

Import/Export

Problem: Import fails

• Open the XML file with a text editor and check for errors
• Create a new export from the source system
• Check the Business Central versions - large version differences can cause problems

Problem: Extended texts are missing after import

• Check the import statistics - it shows skipped records
• Repeat the import with the "Overwrite" or "Update" option

Further Help

• Search documentation: Use the search function in the help
• View examples: Working with the App, Example Scenarios
• Contact support: Contact NAVAX support at www.navax.com

Docs  /  App  /  NAVAX Document Text  /  Advanced Features
 Item Attributes

What are Item Attributes?

• Material: Wood, Metal, Plastic
• Color: Red, Blue, Green
• Size: S, M, L, XL
• Technical data: Power, Voltage, Capacity
• Certifications: CE, ISO, TUV

How Does the Integration Work?

• Material: Solid oak
• Color: Natural oiled
• Seat height: 46 cm

• Material: Solid oak
• Color: Natural oiled
• Seat height: 46 cm

Setting Up Item Attributes for Printing

Step 1: Activate Document Text Setup

1. Open the Document Text Setup page via the search in Business Central.
2. Enable the Print Item Attributes field.
3. Save the setting.

Step 2: Enable Item Attributes for Printing

1. Open the Item Attributes page via the search in Business Central.
2. Select the desired item attribute from the list (e.g., "Material" or "Color").
   
3. Enable editing and place a checkmark in the Print column.
4. Repeat this for all attributes that should appear on documents.

Multilingual Item Attributes

Translations for Item Attributes (Names)

1. Open the Item Attributes page and select the desired attribute (e.g., "Material").
2. Click the Translations action.
3. Add translations for the required languages (e.g., DEU: Material, ENU: Material, FRA: Matériau).
4. Also enable the Print field here for each language variant.

Translations for Item Attribute Values

1. Open the Item Attribute Values page and select the desired attribute value (e.g., "Solid oak").
2. Click the Translations action.
   
3. Add translations for the required languages (e.g., DEU: Eiche massiv, ENU: Solid oak, FRA: Chêne massif).

Using on Documents

1. Create a new document (e.g., sales order).
2. Add an item that has item attributes.
3. NAVAX Document Text checks which item attributes have the Print field enabled.
4. The system automatically creates document text lines only for these attributes.
5. The texts appear as line texts under the item position.
6. You can manually edit or delete the automatically created text lines if needed.

Formatting and Customization

• Change font, size, or color
• Adjust spacing and indentation
• Manually edit the text
• Delete individual attribute lines if they are not needed

Practical Examples

Technical Products

• Power: 2000 W
• Voltage: 230 V
• Energy class: A++
• Protection class: IP65

Fashion Items

• Size: M
• Color: Navy
• Material: 100% Cotton
• Care instructions: Washable at 40°C

Furniture and Furnishings

• Material: Solid oak
• Surface: Natural oiled
• Dimensions: 80 x 120 x 75 cm (W x D x H)
• Weight: 25 kg

Tips and Best Practices

• Selective activation: Enable only relevant attributes for printing. Too much information can make the document confusing.
• Consistent naming: Use uniform names for attributes (e.g., always "Color" instead of sometimes "Shade").
• Order: Item attributes are displayed in the order in which they are created in Business Central.
• Default values: Set default values for frequently used attributes to simplify data maintenance.
• Multilingual: Maintain translations for all languages in which you create documents.
• Maintenance: Regularly check whether all item attributes are current and complete.

Frequently Asked Questions

What happens if an item has no attributes?

Can item attributes be combined with other text types?

Common Problems

Problem: Item attributes do not appear on the document

• Open the Document Text Setup and check whether Print Item Attributes is enabled
• Open the Item Attributes page and check whether the Print field is enabled
• Check on the Item Card whether attributes are assigned to the item
• Verify that the attributes have values (empty attributes are not displayed)

Problem: Item attributes appear in the wrong language

• Open Item Attributes > Translations and check whether translations exist for the desired language
• Also check the Item Attribute Values > Translations
• Ensure that the Print field is also enabled in the translations
• Check the customer's language code - this determines the language used

See Also

• Setup, Line Texts
• Working with the App, Using Line Texts
• Field Descriptions, Document Lines Fields
• Advanced Features, Formatting
• Working with the App, Example Scenarios

Docs  /  App  /  NAVAX Document Text  /  Advanced Features
 Text Editor and Placeholders

Using the NAVAX Document Text Editor

Opening the Text Editor

1. From a document: Open a document and navigate to the desired text type (Beginning Text, Ending Text, Line Text, or Miscellaneous Texts). Click the Edit Text Line action to open the editor.
2. From Standard Text Codes: Open the Standard Text Codes page via the search in Business Central. Select the desired code and open the associated texts via the Extended Texts action. Open a text line to start the editor.

Basic Functions of the Text Editor

• Text input: Enter your text directly into the input field. Use the Enter key for line breaks.
• Copy and paste: You can copy texts from other programs (e.g., Word, Excel) and paste them directly into the editor.
• Insert placeholders: Use the Insert Placeholder function to insert dynamic content from Business Central tables (see section below).
• Multiple lines: For longer texts, you can create multiple text lines. Each line is edited separately in the editor.

Tips for Text Design

• Clarity: Distribute longer texts across multiple lines for better readability.
• Use formatting sparingly: Too much formatting can impair readability.
• Use preview: Check your texts in the print preview before sending documents.
• Test placeholders: Create a test document to verify that placeholders are replaced correctly.

Working with Placeholders

Example: Extended Text for a Beginning Text with Document Validity

Step-by-Step Guide: Inserting Placeholders

• Open the text editor for the desired document text:
  • Directly in a document by opening it and calling the editor via the desired text type (Beginning Text, Ending Text, Line Text, or Miscellaneous Texts). For more information, see the respective chapters under Working with the App.
  • When setting up an extended text that will later be automatically inserted into the selected documents. To do this, open the Standard Text Codes and select the desired extended text. For more information, see Setup, Extended Texts.
• Enter the text "This quote is valid until " (note the space at the end).
• Click Insert Placeholder.
  
• Select the table from which you want to insert the placeholder.

  Note

  This selection only appears when you open the editor from an extended text. If you open the text editor from a document text line, the table is automatically selected.
  
  
• Select the desired field from the list and click OK.
  
• The selected field placeholder is inserted at the current cursor position in the editor. You can continue typing, insert additional placeholders, or adjust spacing and punctuation as needed.
  
• When printing or in the preview, you will see in the beginning text: "This quote is valid until ##Quote Valid Until Date##".

Available Placeholders

Document Header Placeholders

• Customer fields: ##Bill-to Name##, ##Bill-to Address##, ##Bill-to City##
• Date fields: ##Order Date##, ##Document Date##, ##Posting Date##, ##Quote Valid Until Date##
• Amounts: ##Amount Including VAT##, ##Amount##
• Other fields: ##Your Reference##, ##External Document No.##, ##Shipment Date##

Document Line Placeholders

• Item fields: ##Description##, ##Unit of Measure##, ##Quantity##
• Amounts: ##Unit Price##, ##Line Amount##, ##Line Discount %##
• Other fields: ##Variant Code##, ##Location Code##, ##Shipment Date##

Placeholder Format

• Begin and end with double hash marks (##)
• Contain the English field name from Business Central
• Note case sensitivity and spaces
• Example: ##Bill-to Name##, ##Order Date##, ##Amount##

More Placeholder Examples

Example 1: Personalized Greeting with Customer Name

Example 2: Payment Terms with Due Date

Example 3: Delivery Information in Line Text

Example 4: External Reference

Common Problems

Problem: Placeholder is not replaced

• Check the exact spelling: Does the placeholder begin and end with ##?
• Use the Insert Placeholder function instead of manual entry
• Verify that the field exists in the corresponding table:
  • For beginning/ending texts: Field Descriptions, Document Header Fields
  • For line texts: Field Descriptions, Document Lines Fields
• Note case sensitivity and spaces in the field name

Problem: Placeholder shows empty value

• Check whether the field has a value in the document
• Example: ##Your Reference## remains empty if no customer reference was entered
• Optional: Use a standard text as an alternative

Frequently Asked Questions

Can I create my own placeholders?

Are placeholders also considered in formatting?

Are placeholders also replaced in the print preview?

Docs  /  App  /  NAVAX Document Text  /  Advanced Features
 Formatting

How to Use the Formatting Functions

1. Open the text editor:
   • From a document: Open the document and select a Document Text Line for editing.
   • From Standard Text Codes: Open the Standard Text Codes page via the search in Business Central. Select the desired code and open the associated texts via the Extended Texts action.
2. Use the formatting fields in the text line to adjust font type, size, and color.
   
3. Optional: Change the paragraph alignment (left-aligned, centered, right-aligned).
4. Optional: Set padding top/bottom and indentation.
5. Changes are automatically saved when you close the line or switch to another line.

Formatting Defaults

Practical Examples

Highlight Headings

• Bold: Yes
• Font Size: 12 pt
• Padding Bottom: 4 pt (for visual separation)

Mark Important Notes

• Color: Red
• Bold: Yes
• Padding Top/Bottom: 3 pt (for better visibility)

Structure Lists

• Indentation: 10 pt for first level, 20 pt for second level
• Padding Bottom: 1 pt between items

Formatting Tips

• Consistency: Use consistent formatting for the same text types (e.g., format all headings the same way).
• Readability: Use spacing and indentation to visually structure texts and improve readability.
• Use colors sparingly: Use colors only for important highlights, not for the entire text.
• Fonts: Choose easily readable fonts. Arial, Segoe UI, or Times New Roman are particularly suitable for business documents.
• Check preview: Test the formatting in the print preview, as the on-screen display may differ from the printout.
• Missing fonts: If a font is not installed on the system, a default font is automatically used. Therefore, choose standard Windows fonts for maximum compatibility.

Frequently Asked Questions

Why does the formatting look different in the preview than in the text editor?

Can different formatting be used within a single text line?

How can I set default formatting for all texts?

Common Problems

Problem: Formatting does not appear in print

• Ensure you are using a NAVAX report layout For more information, see Advanced Features, Report Layout Selection.
• Open the Document Text Setup and check whether HTML formatting is enabled
• Test with the Print Preview instead of just the screen preview

Problem: Font is not displayed correctly

• Choose a standard Windows font (Arial, Segoe UI, Times New Roman)
• Install the desired font on all systems where documents are printed
• Note that customer systems also need the font if you send PDF documents

Docs  /  App  /  NAVAX Document Text  /  Advanced Features
 Copy Documents

How to Copy a Sales Document

Example: Extended Text for a Beginning Text with Document Validity

Step-by-Step Guide: Copying a Document

1. Open the Sales Orders page. You can reach this via Tell me what you want to do or directly from the Business Central home page if you have the Sales Order Processor role.
2. Click New to create a new sales order. The Sales Order page opens.
3. Click in the Customer Name field. The AssistEdit function displays all customers.
4. Select the desired customer from the list.
5. Click the Copy Document action in the Prepare menu. The Copy Sales Document page opens.
   
6. Select the Document Type to copy (Sales Invoice) and Document No.. The grayed-out fields are automatically filled with the data of the selected document and serve as a control.
   
7. Use the Include Header and Recalculate Lines fields to specify which information should be transferred. Click OK.
8. If the value On Request is set in the Document Text Setup in the Copy Documents with Texts field, the query Do you want to insert the document texts into the copied document? appears. Select whether you want to transfer beginning and ending texts, line texts, or both.
9. Upon completion, you will see the new sales document with all transferred information and texts.

Frequently Asked Questions

The prompt to copy texts does not appear—why?

What happens to extended texts with document-type conditions?

Are personalized texts and formatting carried over?

Docs  /  App  /  NAVAX Document Text  /  Advanced Features
 Report Layout Selection

How to Set Up the NAVAX Document Text Report Layouts

1. Open the Report Layout Selection page via search.
2. Select the desired report layout from the list.
   

   Tip

   Use the search term 117|118|210|404|405|406|407|408|410|1016|1302|1303|1304|1305|1306|1307|1308|1309|5900|5902|5911|5912|5913|5936|5970|5971|5972|5973|6631|6636|6641 to filter all documents that are supported by document texts.
3. In the Layout Type field, select the desired type (RDLC or Word). The available NAVAX Document Text layouts are displayed according to your selection.
   

   Note

   From Business Central 2024 Wave 2 (BC25) onwards, both layout types are available. In earlier versions, only RDLC layouts are available.
4. Click Select Layout to display the list of available report layouts.
5. Select the desired layout from the list. The layout provided by NAVAX Document Text is named NVXDT Standard Layout and can be found in the Report Name column.
   
6. Save your changes by clicking OK.

Frequently Asked Questions

Why are the NAVAX Document Text layouts not displayed in the selection list?

Can I customize the NAVAX Document Text layout?

Do I have to set up the layouts for all documents individually?

What happens if I want to reset the layout to standard later?

Are the texts also printed on posted documents?

Troubleshooting

Problem: No NAVAX Document Text layouts visible

• Layout type not matching: In the Layout Type field, select either RDLC or Word (from Business Central 2024 Wave 2 (BC25) onwards).
• NAVAX Document Text not installed: Check whether the NAVAX Document Text extension is installed and activated in the Extension Management.
• Permissions missing: Make sure you have sufficient permissions to manage report layouts.

Problem: Texts do not appear on the printed document

• Wrong layout selected: Check whether the NVXDT Standard Layout is set up for the report.
• No texts stored: Verify whether beginning texts, line texts, or ending texts have actually been entered for the document.
• Conditions not met: Check the validity conditions (language, document type, period) of the Extended Texts.
• Layout has been customized: If you have modified the layout, make sure that the document text fields are present in the layout.

Problem: Layout cannot be selected

Tips and Best Practices

• Use test environment: Test the layouts first in a test environment before using them productively.
• All documents at once: Use the search filter from step 2 to display all supported documents at once and set up the layouts in one go.
• Document customizations: If you customize layouts, document your changes so you can track them during updates.
• Use print preview: Use the print preview to check the result before actually printing or sending documents.
• Create backup: Export customized layouts as a backup before making major changes.

Managing Report and Document Layouts

Docs  /  App  /  NAVAX Document Text  /  Advanced Features
 Export/Import

When is Export/Import Useful?

• Company change: Transfer extended texts from a test company to the production company
• Version change: Migrate configurations when switching to a new Business Central version
• Data backup: Create regular backups of your extended texts
• Multiple environments: Synchronize extended texts between different systems (e.g., Test, Staging, Production)
• Use templates: Create standard configurations that you can use for new companies
• Collaboration: Share extended texts with other companies or locations

Export of Standard Text Codes

1. Open the Standard Text Codes page via the search in Business Central.
2. Click Actions > Export.
   
3. All Standard Text Codes and their Extended Texts are combined in an XML file and automatically downloaded.
4. The file is saved in your standard download folder and can now be used for import into another system.

Import of Standard Text Codes

1. Open the Standard Text Codes page via the search in Business Central.
2. Click Actions > Import.
   
3. Click click here to browse and select the XML file to import.
   

   Note

   Alternatively, drag and drop the file into the blue frame.
4. If Standard Text Codes already exist, a selection dialog appears with the following options:
   
   • Create if not existing Creates only new records that do not yet exist. Existing records remain unchanged. Use case: Addition of new extended texts without changing existing configurations.
   • Create & overwrite existing records Completely replaces existing records with the imported records. All local changes are lost. Use case: Complete restoration of a backup or overwriting outdated configurations.
   • Create & update existing records (keep settings) Updates the text content but retains existing settings (beginning text/ending text, language code, formatting, document types, etc.). Use case: Update text content while keeping individual customizations.
5. Select the desired option and confirm with OK. The import is started.
6. After a successful import, statistics are displayed showing how many records were imported, updated, or skipped.
   

Best Practices

Regular Backups

• Before major configuration changes
• After completing important setup work
• Before a Business Central update
• At regular intervals (e.g., monthly) as a routine

Naming Export Files

• Date: e.g., "2025-12-15"
• System/Company: e.g., "Production" or "Test"
• Purpose: e.g., "Backup" or "Template"
• Example: "NCDT_2025-12-15_Production_Backup.xml"

Import Strategy

• Test first: Always perform imports in a test environment first
• Choose timing: Import outside business hours to avoid conflicts
• Documentation: Record which files were imported when
• Validation: Spot-check some critical extended texts after import

Version Control

• Keep multiple versions of your exports
• Do not delete old exports immediately - keep at least the last 3-5 versions
• Store important exports in a secure location (e.g., network drive, cloud storage)

Important Notes

• Compatibility: The export file is compatible between different Business Central versions, provided the field structure is identical.
• Data backup: Create a backup of your existing configuration through an export before each import.
• Test import: Perform the first import in a test environment to check the effects.
• Verification after import: Spot-check some extended texts for completeness and correct settings after import.
• Reminders: Manually activate the corresponding extended texts for reminders after import.

Frequently Asked Questions

Are formatting options retained during export/import?

Can I export only individual extended texts?

What happens to placeholders during import?

Can I use exports between different Business Central versions?

How can I check what is contained in an export file?

Are conditions (language, time period) also exported?

What is the difference between "Update" and "Overwrite"?

• Overwrite: Replaces the entire record - all settings are taken from the import file
• Update: Updates only the text content but retains your local settings (document types, formatting, etc.)

Can I use exports between different Business Central versions?

Common Problems

Problem: Import fails with error message

• Open the XML file with a text editor and check for obvious errors
• Create a new export and try again
• Ensure that the file was completely downloaded

Problem: Undo import

Docs  /  App  /  NAVAX Document Text  /  Field Descriptions
 Standard Text Code Fields

Actions

• Import

  The import function allows you to import the Standard Text Codes and their Extended Texts as well as all settings. This can be helpful if you have already created texts in your sandbox or in another database and want to transfer them to the production database. For more information, see Advanced Features, Export/Import.

• Export

  The export function allows you to export the Standard Text Codes and their Extended Texts as well as all settings. This can be helpful if you want to transfer already created texts from your database to your sandbox or another database. For more information, see Advanced Features, Export/Import.

• Text Blocks

  Opens the list of extended texts for the selected Standard Text Code. Here you can manage individual text variants with their conditions (language, period, document type). For more information, see Field Descriptions, Extended Texts.

Practical Notes

Beginning Text and Ending Text

• Beginning Text = Yes: The text appears automatically at the beginning of the document (before the document lines)
• Ending Text = Yes: The text appears automatically at the end of the document (after the document lines)
• Both options can be enabled at the same time if the text should appear in both positions

Ext. Text Exists

Naming Conventions

• Use meaningful codes: e.g., "TERMS-SALES" instead of "TEXT01"
• Use prefixes for different areas: e.g., "SL-" for Sales, "PU-" for Purchase
• The description should clearly communicate the content of the text
• Codes are case-sensitive – ensure consistent spelling

Frequently Asked Questions

How do I create a new Standard Text Code?

Can I rename a Standard Text Code?

See Also

• For more information, see Setup, Extended Texts.Set up extended texts
• Field Descriptions, Extended TextsField descriptions for extended texts
• Advanced Features, Export/ImportExport and import extended texts

Docs  /  App  /  NAVAX Document Text  /  Field Descriptions
 Extended Texts

Actions

• Copy from Extended Text

  With this action, you can copy the lines from an existing extended text to the current extended text.

• Disable Sequel Fields

  With this action, you can deactivate all document sequel fields.

• Activate Sequel Fields

  With this action, you can activate all document sequel fields.

Practical tips for key fields

Language Code and All Languages

• Leave Language Code empty and enable All Languages for language-independent texts
• Create multiple extended texts with the same code but different language codes for multilingual texts
• The system automatically selects the appropriate text based on the customer/vendor language code

Sorting Sequence

• Use steps of 10 (10, 20, 30, ...) to insert texts later between existing ones
• Lower values appear first on the document
• If the sorting sequence is the same, the Text No. (assigned automatically) decides the order

Periods with Start and End Date

• Ideal for seasonal notes, time-limited promotions, or year-end changes
• Leave both fields empty for texts that are always valid
• The document date (not the posting date!) is used for validation

Enable document types

• Enable only the document types on which the text should appear
• To carry over to subsequent documents (e.g., Quote → Order → Invoice), enable all relevant document types
• FastTabs are grouped by area: Sales, Purchase, Service, Project

See also

• Setup, Extended TextsSet up extended texts
• Working with the App, Sorting and ConditionsSorting and conditions
• Advanced Features, FormattingFormatting
• Advanced Features, Text Editor and PlaceholdersText editor and placeholders
• Field Descriptions, Standard Text Code FieldsStandard Text Code Fields

Docs  /  App  /  NAVAX Document Text  /  Field Descriptions
 Document Header Fields

Actions

• Beginning texts

  This action opens the list of configured beginning texts that should be printed for the vendor on documents.

• Ending texts

  This action opens the list of configured ending texts that should be printed for the vendor on documents.

Practical notes

Field "Line Texts"

Automatic line texts

• Item text modules: Texts linked directly to the item
• Item attributes: Product properties such as material, color, size
• Standard text modules: General texts with conditions (language, period, document type)

See also

• Working with the App, Using Line TextsWorking with line texts
• Setup, Line TextsSet up line texts
• Advanced Features, Item AttributesUse item attributes
• Advanced Features, Text Editor and PlaceholdersText editor and placeholders
• Advanced Features, FormattingFormatting

Docs  /  App  /  NAVAX Document Text  /  Field Descriptions
 Personalized Texts

Where to Find These Fields

• Customer Card
• Vendor Card
• Salesperson/Purchaser Card

Docs  /  App  /  NAVAX Document Text  /  Field Descriptions
 Document Lines Fields

Actions

• Insert Ext. Texts

  Use this action to select standard text blocks and insert them into the lines.

• Line Texts

  This action opens the overview of configured line texts that should be printed on documents.

Practical Tips

Field "Line Texts"

Automatic Line Texts

• Item text blocks: Texts linked directly to the item
• Item attributes: Product properties such as material, color, size
• Standard text blocks: General texts with conditions (language, period, document type)

See also

• Working with the App, Using Line TextsWorking with Line Texts
• Setup, Line TextsSet Up Line Texts
• Advanced Features, Item AttributesUse Item Attributes
• Advanced Features, Text Editor and PlaceholdersText Editor and Placeholders
• Advanced Features, FormattingFormatting

Docs  /  App  /  NAVAX Document Text  /  Field Descriptions
 Line Positions on Master Data Cards

Where to Find These Fields

• Item Card - for item-specific texts
• Resource Card - for resource-specific texts
• G/L Account Card - for G/L account-specific texts
• Service Item Card - for service item-specific texts

How It Works

1. Extended Texts are stored for this master data record
2. The Automatic Ext. Texts option is activated
3. The Extended Texts meet the appropriate conditions (language, document type, period)

Actions

• Extended Texts

  Opens the list of Extended Texts for the current master data record. Here you can:
  • Create new Extended Texts
  • Edit existing Extended Texts
  • Delete Extended Texts
  • Define conditions for Extended Texts (language, document type, period)
  • Adjust the sorting sequence of the texts

Docs  /  App  /  NAVAX Document Text  /  Field Descriptions
 Miscellaneous Texts

Practical Tips

What are miscellaneous texts?

• Payment Terms: Texts about payment deadlines, cash discount conditions
• Shipping Advice: Texts about shipping methods, delivery conditions
• Interest Methods: Texts for reminders and interest calculations
• Service Order Types: Specific texts for service scenarios
• Service Contract Groups: Texts for service contracts

Setup

Automatic insertion

See also

• Working with the App, Using Miscellaneous TextsWorking with miscellaneous texts
• Setup, Miscellaneous TextsSet up miscellaneous texts
• Field Descriptions, Document Header FieldsDocument header fields

Docs  /  App  /  NAVAX Document Text  /  Field Descriptions
 Document Text Line Fields

Actions

• Insert Ext. Texts

  With this action, you can select and insert extended texts.

Practical Notes

Text Field

Formatting Fields

Document Type Fields

See also

• Working with the App, Using Beginning and Ending TextsWorking with Beginning and Ending Texts
• Working with the App, Using Line TextsWorking with Line Texts
• Advanced Features, Text Editor and PlaceholdersText Editor and Placeholders
• Advanced Features, FormattingFormatting

Docs  /  App  /  NAVAX Document Text  /  Field Descriptions
 Field List

Practical Notes

Using the Field List

Field Name vs. Field Caption

• Field Caption: The readable (localized) name of the field (e.g., "Customer Name")
• Field Name: The technical English name used for placeholders (e.g., "Bill-to Name")
• For placeholders always use the Field Name: ##Bill-to Name##

Available Fields by Table

• Document Header Tables: For pre- and post-texts and other texts
• Document Line Tables: For line texts
• Availability depends on whether you use the text in the document header or in a document line

See also

• For more information, see Advanced Features, Text Editor and Placeholders.Text Editor and Placeholders
• Field Descriptions, Document Header FieldsDocument Header Fields
• Field Descriptions, Document Lines FieldsDocument Line Fields

Docs  /  App  /  NAVAX Document Text  /  Information for Developers
 Extending Documents

Customize individual reports to use NAVAX Document Text

NVXDT Report Management

GetReportText

procedure GetReportText(RecordVariant: Variant; NVXDTTextType: Enum "NVXDT Text Type"; AsHTML: Boolean): Text

Parameters

• RecordVariant Here the record for which the texts are to be inserted is passed as a Variant. This can be e.g.: a Sales Header, Purchase Header or also Sales Line or Purchase Line.

  Important

  It is important to make sure that the correct filters are set on the RecordVariant.
• NVXDTTextType The parameter specifies what kind of text lines should be inserted. Ex: Beginning Text, Ending Text, Line Text, Payment Terms Text etc....
• AsHTML Specifies whether a text should be returned html formatted, this is used in RDL(C) reports, or as normal text, this is used e.g. in Word reports.

  Important

  If the text has to be implemented as HTML text in your report, a placeholder with the option HTML - interpret HTML tags as styles must be activated in the RDL(C) layout.

Implementation

reportextension 70714787 "NVXDT Purchase Order" extends Order
{
    dataset
    {
        add(CopyLoop)
        {
            column(NVXDTBeginningText_RDLCText; NVXDTReportManagement.GetReportText("Purchase Header", Enum::"NVXDT Text Type"::"Beginning Text", true)) { }
            column(NVXDTBeginningText_WordText; NVXDTReportManagement.GetReportText("Purchase Header", Enum::"NVXDT Text Type"::"Beginning Text", false)) { }
            column(NVXDTEndingText_RDLCText; NVXDTReportManagement.GetReportText("Purchase Header", Enum::"NVXDT Text Type"::"Ending Text", true)) { }
            column(NVXDTEndingText_WordText; NVXDTReportManagement.GetReportText("Purchase Header", Enum::"NVXDT Text Type"::"Ending Text", false)) { }
            column(NVXDTShipmentText_RDLCText; NVXDTReportManagement.GetReportText("Purchase Header", Enum::"NVXDT Text Type"::"Shipment Method Text", true)) { }
            column(NVXDTShipmentText_WordText; NVXDTReportManagement.GetReportText("Purchase Header", Enum::"NVXDT Text Type"::"Shipment Method Text", false)) { }
            column(NVXDTPaymentText_RDLCText; NVXDTReportManagement.GetReportText("Purchase Header", Enum::"NVXDT Text Type"::"Payment Terms Text", true)) { }
            column(NVXDTPaymentText_WordText; NVXDTReportManagement.GetReportText("Purchase Header", Enum::"NVXDT Text Type"::"Payment Terms Text", false)) { }
        }
        add(RoundLoop)
        {
            column(NVXDTLineText_RDLCText; NVXDTReportManagement.GetReportText("Purchase Line", Enum::"NVXDT Text Type"::"Line Text", true)) { }
            column(NVXDTLineText_WordText; NVXDTReportManagement.GetReportText("Purchase Line", Enum::"NVXDT Text Type"::"Line Text", false)) { }
        }
    }

    rendering
    {
        layout("NVXDT Purchase Order")
        {
            Caption = 'NVXDT Default Layout', comment = 'DEU="NVXDT Standardlayout"';
            Type = RDLC;
            LayoutFile = './NVXDTPurchaseOrder.rdlc';
            Summary = 'The default layout from NAVAX Document Text.', Comment = 'DEU="Das Standardlayout von NAVAX Belegtext."';
        }
    }

    var
        NVXDTReportManagement: Codeunit "NVXDT Report Management";
}

Docs  /  App  /  NAVAX Document Text  /  Information for Developers
 Extending NAVAX Document Text

Table - NVXDT Doc. Text Line

• OnBeforeGetFormattedText

  The event is used to format the text before it is rendered for reports.

  [BusinessEvent(false)]
  local procedure OnBeforeGetFormattedText(Text: Text[2048]; var RetText: Text; AsHTML: Boolean; var IsHandled: Boolean)
  begin
  end;

  Parameters

  Type	Name	Description
  Text[2048]	Text	The input text to be formatted.
  Text	RetText	[Pass by Reference] The formatted output text.
  Boolean	AsHTML	If true, the text is formatted as HTML. If false the text returned as saved in the database.
  Boolean	IsHandled	[Pass by Reference] If set to true, the execution of the calling function is interrupted.

• OnAfterCreateStyleExpression

  The event is used to create the style expression for the text.

  [BusinessEvent(false)]
  local procedure OnAfterCreateStyleExpression(StyleText: Text)
  begin
  end;

  Parameters

  Type	Name	Description
  Text	StyleText	The style expression for the text.

• OnBeforeEditText

  The event is used to edit the text before it is saved.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeEditText(var NVXDTDocTextLine: Record "NVXDT Doc. Text Line"; var IsHandled: Boolean)
  begin
  end;

  Parameters

  Type	Name	Description
  Record "NVXDT Doc. Text Line"	NVXDTDocTextLine	[Pass by Reference] The document text line.
  Boolean	IsHandled	[Pass by Reference] If set to true, the execution of the calling function is interrupted.

Table - NVXDT Doc. Text Line Archive

• OnBeforeGetFormattedText

  The event is used to format the text before it is rendered for reports.

  [BusinessEvent(false)]
  local procedure OnBeforeGetFormattedText(Text: Text[2048]; var RetText: Text; AsHTML: Boolean; var IsHandled: Boolean)
  begin
  end;

  Parameters

  Type	Name	Description
  Text[2048]	Text	The input text to be formatted.
  Text	RetText	[Pass by Reference] The formatted output text.
  Boolean	AsHTML	If true, the text is formatted as HTML. If false the text returned as saved in the database.
  Boolean	IsHandled	[Pass by Reference] If set to true, the execution of the calling function is interrupted.

• OnAfterCreateStyleExpression

  The event is used to create the style expression for the text.

  [BusinessEvent(false)]
  local procedure OnAfterCreateStyleExpression(StyleText: Text)
  begin
  end;

  Parameters

  Type	Name	Description
  Text	StyleText	The style expression for the text.

Table - NVXDT Posted Doc. Text Line

• OnBeforeGetFormattedText

  The event is used to format the text before it is rendered for reports.

  [BusinessEvent(false)]
  local procedure OnBeforeGetFormattedText(Text: Text[2048]; var RetText: Text; AsHTML: Boolean; var IsHandled: Boolean)
  begin
  end;

  Parameters

  Type	Name	Description
  Text[2048]	Text	The input text to be formatted.
  Text	RetText	[Pass by Reference] The formatted output text.
  Boolean	AsHTML	If true, the text is formatted as HTML. If false the text returned as saved in the database.
  Boolean	IsHandled	[Pass by Reference] If set to true, the execution of the calling function is interrupted.

• OnAfterCreateStyleExpression

  The event is used to create the style expression for the text.

  [BusinessEvent(false)]
  local procedure OnAfterCreateStyleExpression(StyleText: Text)
  begin
  end;

  Parameters

  Type	Name	Description
  Text	StyleText	The style expression for the text.

• OnBeforeEditText

  The event is used to edit the text before it is saved.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeEditText(var NVXDTDocTextLine: Record "NVXDT Doc. Text Line"; var IsHandled: Boolean)
  begin
  end;

  Parameters

  Type	Name	Description
  Record "NVXDT Doc. Text Line"	NVXDTDocTextLine	[Pass by Reference] The document text line.
  Boolean	IsHandled	[Pass by Reference] If set to true, the execution of the calling function is interrupted.

Table - NVXDT Job Text Line

• OnBeforeGetFormattedText

  The event is used to format the text before it is rendered for reports.

  [BusinessEvent(false)]
  local procedure OnBeforeGetFormattedText(Text: Text[2048]; var RetText: Text; AsHTML: Boolean; var IsHandled: Boolean)
  begin
  end;

  Parameters

  Type	Name	Description
  Text[2048]	Text	The input text to be formatted.
  Text	RetText	[Pass by Reference] The formatted output text.
  Boolean	AsHTML	If true, the text is formatted as HTML. If false the text returned as saved in the database.
  Boolean	IsHandled	[Pass by Reference] If set to true, the execution of the calling function is interrupted.

• OnAfterCreateStyleExpression

  The event is used to create the style expression for the text.

  [BusinessEvent(false)]
  local procedure OnAfterCreateStyleExpression(StyleText: Text)
  begin
  end;

  Parameters

  Type	Name	Description
  Text	StyleText	The style expression for the text.

• OnBeforeEditText

  The event is used to edit the text before it is saved.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeEditText(var NVXDTDocTextLine: Record "NVXDT Doc. Text Line"; var IsHandled: Boolean)
  begin
  end;

  Parameters

  Type	Name	Description
  Record "NVXDT Doc. Text Line"	NVXDTDocTextLine	[Pass by Reference] The document text line.
  Boolean	IsHandled	[Pass by Reference] If set to true, the execution of the calling function is interrupted.

TableExt - Sales Header

• NVXDTOnGetDocTextFlagsOnBeforeExit

  This event is used to set flags indicating whether document texts exist for the selected document or subsequent documents. This event is called if no other document text lines exists for the selected document.

  [IntegrationEvent(false, false)]
  local procedure NVXDTOnGetDocTextFlagsOnBeforeExit(var NVXDTDocTextLine: Record "NVXDT Doc. Text Line"; var DocTextExist: Boolean; var FollDocTextExist: Boolean; SalesHeader: Record "Sales Header")
  begin
  end;

  Parameters

  Type	Name	Description
  Record "NVXDT Doc. Text Line"	NVXDTDocTextLine	[Pass by Reference] The document text line record that is filtered to search for specific criteria.
  Boolean	DocTextExist	[Pass by Reference] Indicates whether a document text exists for the selected document. This will be shown on the pages.
  Boolean	FollDocTextExist	[Pass by Reference] Indicates whether a document text exists for sequel documents. This will be shown on the pages.
  Record "Sales Header"	SalesHeader	The sales header record.

• NVXDTOnAfterGetDocTextFlags

  This event is used to set flags indicating whether document texts exist for the selected document or subsequent documents.

  [IntegrationEvent(false, false)]
  local procedure NVXDTOnAfterGetDocTextFlags(var NVXDTDocTextLine: Record "NVXDT Doc. Text Line"; var DocTextExist: Boolean; var FollDocTextExist: Boolean)
  begin
  end;

  Parameters

  Type	Name	Description
  Record "NVXDT Doc. Text Line"	NVXDTDocTextLine	[Pass by Reference] The document text line record that is filtered to search for specific criteria.
  Boolean	DocTextExist	[Pass by Reference] Indicates whether a document text exists for the selected document. This will be shown on the pages.
  Boolean	FollDocTextExist	[Pass by Reference] Indicates whether a document text exists for sequel documents. This will be shown on the pages.
  Record "Sales Header"	SalesHeader	The sales header record.

TableExt - Purchase Header

• NVXDTOnGetDocTextFlagsOnBeforeExit

  This event is used to set flags indicating whether document texts exist for the selected document or subsequent documents. This event is called if no other document text lines exists for the selected document.

  [IntegrationEvent(false, false)]
  local procedure NVXDTOnGetDocTextFlagsOnBeforeExit(var NVXDTDocTextLine: Record "NVXDT Doc. Text Line"; var DocTextExist: Boolean; var FollDocTextExist: Boolean; PurchaseHeader: Record "Purchase Header")
  begin
  end;

  Parameters

  Type	Name	Description
  Record "NVXDT Doc. Text Line"	NVXDTDocTextLine	[Pass by Reference] The document text line record that is filtered to search for specific criteria.
  Boolean	DocTextExist	[Pass by Reference] Indicates whether a document text exists for the selected document. This will be shown on the pages.
  Boolean	FollDocTextExist	[Pass by Reference] Indicates whether a document text exists for sequel documents. This will be shown on the pages.
  Record "Purchase Header"	PurchaseHeader	The purchase header record.

• NVXDTOnAfterGetDocTextFlags

  This event is used to set flags indicating whether document texts exist for the selected document or subsequent documents.

  [IntegrationEvent(false, false)]
  local procedure NVXDTOnAfterGetDocTextFlags(var NVXDTDocTextLine: Record "NVXDT Doc. Text Line"; var DocTextExist: Boolean; var FollDocTextExist: Boolean)
  begin
  end;

  Parameters

  Type	Name	Description
  Record "NVXDT Doc. Text Line"	NVXDTDocTextLine	[Pass by Reference] The document text line record that is filtered to search for specific criteria.
  Boolean	DocTextExist	[Pass by Reference] Indicates whether a document text exists for the selected document. This will be shown on the pages.
  Boolean	FollDocTextExist	[Pass by Reference] Indicates whether a document text exists for sequel documents. This will be shown on the pages.
  Record "Purchase Header"	PurchaseHeader	The purchase header record.

TableExt - Service Header

• NVXDTOnGetDocTextFlagsOnBeforeExit

  This event is used to set flags indicating whether document texts exist for the selected document or subsequent documents. This event is called if no other document text lines exists for the selected document.

  [IntegrationEvent(false, false)]
  local procedure NVXDTOnGetDocTextFlagsOnBeforeExit(var NVXDTDocTextLine: Record "NVXDT Doc. Text Line"; var DocTextExist: Boolean; var FollDocTextExist: Boolean; ServiceHeader: Record "Service Header")
  begin
  end;

  Parameters

  Type	Name	Description
  Record "NVXDT Doc. Text Line"	NVXDTDocTextLine	[Pass by Reference] The document text line record that is filtered to search for specific criteria.
  Boolean	DocTextExist	[Pass by Reference] Indicates whether a document text exists for the selected document. This will be shown on the pages.
  Boolean	FollDocTextExist	[Pass by Reference] Indicates whether a document text exists for sequel documents. This will be shown on the pages.
  Record "Service Header"	ServiceHeader	The service header record.

• NVXDTOnAfterGetDocTextFlags

  This event is used to set flags indicating whether document texts exist for the selected document or subsequent documents.

  [IntegrationEvent(false, false)]
  local procedure NVXDTOnAfterGetDocTextFlags(var NVXDTDocTextLine: Record "NVXDT Doc. Text Line"; var DocTextExist: Boolean; var FollDocTextExist: Boolean)
  begin
  end;

  Parameters

  Type	Name	Description
  Record "NVXDT Doc. Text Line"	NVXDTDocTextLine	[Pass by Reference] The document text line record that is filtered to search for specific criteria.
  Boolean	DocTextExist	[Pass by Reference] Indicates whether a document text exists for the selected document. This will be shown on the pages.
  Boolean	FollDocTextExist	[Pass by Reference] Indicates whether a document text exists for sequel documents. This will be shown on the pages.
  Record "Service Header"	ServiceHeader	The service header record.

TableExt - Service Contract Header

• NVXDTOnGetDocTextFlagsOnBeforeExit

  This event is used to set flags indicating whether document texts exist for the selected document or subsequent documents. This event is called if no other document text lines exists for the selected document.

  [IntegrationEvent(false, false)]
  local procedure NVXDTOnGetDocTextFlagsOnBeforeExit(var NVXDTDocTextLine: Record "NVXDT Doc. Text Line"; var DocTextExist: Boolean; var FollDocTextExist: Boolean; ServiceHeader: Record "Service Contract Header")
  begin
  end;

  Parameters

  Type	Name	Description
  Record "NVXDT Doc. Text Line"	NVXDTDocTextLine	[Pass by Reference] The document text line record that is filtered to search for specific criteria.
  Boolean	DocTextExist	[Pass by Reference] Indicates whether a document text exists for the selected document. This will be shown on the pages.
  Boolean	FollDocTextExist	[Pass by Reference] Indicates whether a document text exists for sequel documents. This will be shown on the pages.
  Record "Service Contract Header"	ServiceContractHeader	The service contract header record.

• NVXDTOnAfterGetDocTextFlags

  This event is used to set flags indicating whether document texts exist for the selected document or subsequent documents.

  [IntegrationEvent(false, false)]
  local procedure NVXDTOnAfterGetDocTextFlags(var NVXDTDocTextLine: Record "NVXDT Doc. Text Line"; var DocTextExist: Boolean; var FollDocTextExist: Boolean)
  begin
  end;

  Parameters

  Type	Name	Description
  Record "NVXDT Doc. Text Line"	NVXDTDocTextLine	[Pass by Reference] The document text line record that is filtered to search for specific criteria.
  Boolean	DocTextExist	[Pass by Reference] Indicates whether a document text exists for the selected document. This will be shown on the pages.
  Boolean	FollDocTextExist	[Pass by Reference] Indicates whether a document text exists for sequel documents. This will be shown on the pages.
  Record "Service Contract Header"	ServiceContractHeader	The service contract header record.

TableExt - Job

• NVXDTOnGetDocTextFlagsOnBeforeExit

  This event is used to set flags indicating whether document texts exist for the selected document or subsequent documents. This event is called if no other document text lines exists for the selected document.

  [IntegrationEvent(false, false)]
  local procedure NVXDTOnGetDocTextFlagsOnBeforeExit(var NVXDTDocTextLine: Record "NVXDT Doc. Text Line"; var DocTextExist: Boolean; var FollDocTextExist: Boolean; Job: Record "Job")
  begin
  end;

  Parameters

  Type	Name	Description
  Record "NVXDT Doc. Text Line"	NVXDTDocTextLine	[Pass by Reference] The document text line record that is filtered to search for specific criteria.
  Boolean	DocTextExist	[Pass by Reference] Indicates whether a document text exists for the selected document. This will be shown on the pages.
  Boolean	FollDocTextExist	[Pass by Reference] Indicates whether a document text exists for sequel documents. This will be shown on the pages.
  Record "Job"	Job	The job record.

• NVXDTOnAfterGetDocTextFlags

  This event is used to set flags indicating whether document texts exist for the selected document or subsequent documents.

  [IntegrationEvent(false, false)]
  local procedure NVXDTOnAfterGetDocTextFlags(var NVXDTDocTextLine: Record "NVXDT Doc. Text Line"; var DocTextExist: Boolean; var FollDocTextExist: Boolean)
  begin
  end;

  Parameters

  Type	Name	Description
  Record "NVXDT Doc. Text Line"	NVXDTDocTextLine	[Pass by Reference] The document text line record that is filtered to search for specific criteria.
  Boolean	DocTextExist	[Pass by Reference] Indicates whether a document text exists for the selected document. This will be shown on the pages.
  Boolean	FollDocTextExist	[Pass by Reference] Indicates whether a document text exists for sequel documents. This will be shown on the pages.
  Record "Job"	Job	The job record.

TableExt - NVXDT Extended Text Line

• NVXDTOnBeforeEditText

  The event is used to edit the text before it is saved.

  [IntegrationEvent(false, false)]
  local procedure NVXDTOnBeforeEditText(var ExtendedTextLine: Record "Extended Text Line"; var IsHandled: Boolean)
  begin
  end;

  Parameters

  Type	Name	Description
  Record "Extended Text Line"	ExtendedTextLine	[Pass by Reference] The extended text line.
  Boolean	IsHandled	[Pass by Reference] If set to true, the execution of the calling function is interrupted.

Codeunit - NVXDT Document Text Mgt.

• OnBeforeGetRecordRefData

  The event is used to read all necessary values of a document and store them in global variables. These global variables are then needed in the various functions of the codeunit. If IsHandled is set to true, the execution of the called function is interrupted.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeGetRecordRefData(RecordRef: RecordRef; var _TableID: Integer; var _DocNo: Code[20]; var _DocDate: Date; var _DocType: Enum "NVXDT Document Type"; var _DocStatus: Option; var _DocLineNo: Integer; var _DocLineTheNo: Code[20]; var _DocLineTheType: Option; var IsHandled: Boolean; LanguageCode: Code[10])
  begin
  end;

  Parameters

  Type	Name	Description
  RecordRef	RecordRef	The RecordRef that refers to the document.
  Integer	_TableID	[Pass by Reference] The Table Id for this document.
  Code[20]	_DocNo	[Pass by Reference] The document number.
  Date	_DocDate	[Pass by Reference] The document date.
  Enum "NVXDT Document Type"	_DocType	[Pass by Reference] The document type.
  Option	_DocStatus	[Pass by Reference] The document status.
  Integer	_DocLineNo	[Pass by Reference] The document line number.
  Code[20]	_DocLineTheNo	[Pass by Reference] The number of line type.
  Option	_DocLineTheType	[Pass by Reference] The type of transaction that is being posted for the document line.
  Boolean	IsHandled	[Pass by Reference] If set to true, the execution of the calling function is interrupted.
  Code[10]	LanguageCode	The language code.

• OnAfterGetRecordRefData

  The event is used to read all necessary values of a document and store them in global variables. These global variables are then needed in the various functions of the codeunit.

  [IntegrationEvent(false, false)]
  local procedure OnAfterGetRecordRefData(RecordRef: RecordRef; var _TableID: Integer; var _DocNo: Code[20]; var _DocDate: Date; var _DocType: Enum "NVXDT Document Type"; var _DocStatus: Option; var _DocLineNo: Integer; var _DocLineTheNo: Code[20]; var _DocLineTheType: Option; LanguageCode: Code[10])
  begin
  end;

  Parameters

  Type	Name	Description
  RecordRef	RecordRef	The RecordRef that refers to the document.
  Integer	_TableID	[Pass by Reference] The Table Id for this document.
  Code[20]	_DocNo	[Pass by Reference] The document number.
  Date	_DocDate	[Pass by Reference] The document date.
  Enum "NVXDT Document Type"	_DocType	[Pass by Reference] The document type.
  Option	_DocStatus	[Pass by Reference] The document status.
  Integer	_DocLineNo	[Pass by Reference] The document line number.
  Code[20]	_DocLineTheNo	[Pass by Reference] The number of line type.
  Option	_DocLineTheType	[Pass by Reference] The type of transaction that is being posted for the document line.
  Code[10]	LanguageCode	The language code.

• OnGetRecordRefDataUnknownTable

  The event is used to read all necessary values of a non standard Business Central table and store them in global variables. These global variables are then needed in the various functions of the codeunit.

  [IntegrationEvent(false, false)]
  local procedure OnGetRecordRefDataUnknownTable(RecordRef: RecordRef; var _TableID: Integer; var _DocNo: Code[20]; var _DocDate: Date; var _DocType: Enum "NVXDT Document Type"; var _DocStatus: Option; var GlobalVersionNo: Integer; var _DocLineNo: Integer; var _DocLineTheNo: Code[20]; var _DocLineTheType: Option; var Handled: Boolean)
  begin
  end;

  Type	Name	Description
  RecordRef	RecordRef	The RecordRef that refers to the document.
  Integer	_TableID	[Pass by Reference] The Table Id for this document.
  Code[20]	_DocNo	[Pass by Reference] The document number.
  Date	_DocDate	[Pass by Reference] The document date.
  Enum "NVXDT Document Type"	_DocType	[Pass by Reference] The document type.
  Option	_DocStatus	[Pass by Reference] The document status.
  Integer	GlobalVersionNo	[Pass by Reference] The version number of the document.
  Integer	_DocLineNo	[Pass by Reference] The document line number.
  Code[20]	_DocLineTheNo	[Pass by Reference] The number of line type.
  Option	_DocLineTheType	[Pass by Reference] The type of transaction that is being posted for the document line.

• OnBeforeDeleteText

  The event is used to delete the text lines before deleting the document.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeDeleteText(RecordRef: RecordRef; var IsHandled: Boolean)
  begin
  end;

  Type	Name	Description
  RecordRef	RecordRef	The RecordRef that refers to the document.
  Boolean	IsHandled	[Pass by Reference] If set to true, the execution of the calling function is interrupted.

• OnAfterDoPrintUnknownTableID

  The event is used to print the text lines of a non standard Business Central table.

  [IntegrationEvent(false, false)]
  local procedure OnAfterDoPrintUnknownTableID(TableID: Integer; DocLineTheType: Option; DocLineTheType2: Option; DocLineTheNo: Code[20]; Unconditionally: Boolean; var AutoText: Boolean; var Handled: Boolean)
  begin
  end;

  Type	Name	Description
  Integer	TableID	The Table Id for this document.
  Option	DocLineTheType	The type of transaction that is being posted for the document line.
  Option	DocLineTheType2	The type of transaction that is being posted for the document line.
  Code[20]	DocLineTheNo	The number of line type.
  Boolean	Unconditionally	Print the text unconditionally.
  Boolean	AutoText	[Pass by Reference] Print the text automatically.
  Boolean	Handled	[Pass by Reference] If set to true, the execution of the calling function is interrupted.

• OnBeforeDoPrintText

  The event is used to edit the text lines before printing.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeDoPrintText(var TableID: Integer; var DocLineTheType: Option; var DocLineTheType2: Option; var DocLineTheNo: Code[20]; var Unconditionally: Boolean; var AutoText: Boolean; var IsHandled: Boolean)
  begin
  end;

  Type	Name	Description
  Integer	TableID	[Pass by Reference] The Table Id for this document.
  Option	DocLineTheType	[Pass by Reference] The type of transaction that is being posted for the document line.
  Option	DocLineTheType2	[Pass by Reference] The type of transaction that is being posted for the document line.
  Code[20]	DocLineTheNo	[Pass by Reference] The number of line type.
  Boolean	Unconditionally	[Pass by Reference] Print the text unconditionally.
  Boolean	AutoText	[Pass by Reference] Print the text automatically.
  Boolean	IsHandled	[Pass by Reference] If set to true, the execution of the calling function is interrupted.

• OnBeforeExtTextToDocTextSetSequelFields

  The event is used to set the sequel fields for the document flow of the document text line.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeExtTextToDocTextSetSequelFields(var TempDocTextLine: Record "NVXDT Doc. Text Line"; var ExtendedTextHeader: Record "Extended Text Header")
  begin
  end;

  Type	Name	Description
  Record "NVXDT Doc. Text Line"	TempDocTextLine	[Temporary] [Pass by Reference] The document text line.
  Record "Extended Text Header"	ExtendedTextHeader	[Pass by Reference] The extended text header.

• OnBeforeExtTextToJobTextSetSequelFields

  The event is used to set the sequel fields for the job flow of the document text line.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeExtTextToJobTextSetSequelFields(var TempNVXDTJobTextLine: Record "NVXDT Job Text Line"; var ExtendedTextHeader: Record "Extended Text Header")
  begin
  end;

  Type	Name	Description
  Record "NVXDT Job Text Line"	TempNVXDTJobTextLine	[Temporary] [Pass by Reference] The job text line.
  Record "Extended Text Header"	ExtendedTextHeader	[Pass by Reference] The extended text header.

• OnBeforeResetDocTypeFilterSetFilterGroup

  The event is used to set the filter group for the document type.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeResetDocTypeFilterSetFilterGroup(var ExtendedTextHeader: Record "Extended Text Header")
  begin
  end;

  Type	Name	Description
  Record "Extended Text Header"	ExtendedTextHeader	[Pass by Reference] The extended text header.

• OnBeforeSetExtTextHeaderFilters

  The event is used to set the filters for the extended text header.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeSetExtTextHeaderFilters(var ExtendedTextHeader: Record "Extended Text Header"; LanguageCode: Code[10]; TableID: Integer; DocNo: Code[20]; var DocType: Enum "NVXDT Document Type"; var DocDate: Date; DocLineTheType: Option; DocLineTheNo: Code[20]; var DocLineNo: Integer; var TextType: Enum "NVXDT Text Type"; var Unconditional: Boolean; var AddedLines: Boolean; var IsHandled: Boolean)
  begin
  end;

  Type	Name	Description
  Record "Extended Text Header"	ExtendedTextHeader	[Pass by Reference] The extended text header.
  Code[10]	LanguageCode	The language code.
  Integer	TableID	The Table Id for this document.
  Code[20]	DocNo	The document number.
  Enum "NVXDT Document Type"	DocType	[Pass by Reference] The document type.
  Date	DocDate	The document date.
  Option	DocLineTheType	The type of transaction that is being posted for the document line.
  Code[20]	DocLineTheNo	The number of line type.
  Integer	DocLineNo	[Pass by Reference] The document line number.
  Enum "NVXDT Text Type"	TextType	[Pass by Reference] The text type.
  Boolean	Unconditional	[Pass by Reference] Print the text unconditionally.
  Boolean	AddedLines	[Pass by Reference] Print the text automatically.
  Boolean	IsHandled	[Pass by Reference] If set to true, the execution of the calling function is interrupted.

• OnAfterSetExtTextHeaderFilters

  The event is used to set the filters for the extended text header.

  [IntegrationEvent(false, false)]
      local procedure OnAfterSetExtTextHeaderFilters(var ExtendedTextHeader: Record "Extended Text Header"; var AddedLines: Boolean; var LanguageCode: Code[10]; var TableID: Integer; var DocNo: Code[20]; var DocType: Enum "NVXDT Document Type"; var DocDate: Date; var DocLineTheType: Option; var DocLineTheNo: Code[20]; var DocLineNo: Integer; var TextType: Enum "NVXDT Text Type"; Unconditionally: Boolean)
      begin
      end;

  Type	Name	Description
  Record "Extended Text Header"	ExtendedTextHeader	[Pass by Reference] The extended text header.
  Boolean	AddedLines	[Pass by Reference] Print the text automatically.
  Code[10]	LanguageCode	The language code.
  Integer	TableID	[Pass by Reference] The Table Id for this document.
  Code[20]	DocNo	[Pass by Reference] The document number.
  Enum "NVXDT Document Type"	DocType	[Pass by Reference] The document type.
  Date	DocDate	The document date.
  Option	DocLineTheType	[Pass by Reference] The type of transaction that is being posted for the document line.
  Code[20]	DocLineTheNo	[Pass by Reference] The number of line type.
  Integer	DocLineNo	[Pass by Reference] The document line number.
  Enum "NVXDT Text Type"	TextType	[Pass by Reference] The text type.
  Boolean	Unconditionally	Print the text unconditionally.

• OnAfterSetExtTextHeaderFiltersJobPlanningLine

  The event is used to set the filters for the extended text header for job planning lines.

  [IntegrationEvent(false, false)]
  local procedure OnAfterSetExtTextHeaderFiltersJobPlanningLine(var ExtendedTextHeader: Record "Extended Text Header"; var AddedLines: Boolean; var LanguageCode: Code[10]; var JobNo: Code[20]; var JobTaskNo: Code[20]; var DocDate: Date; var DocLineTheType: Option; var DocLineTheNo: Code[20]; var DocLineNo: Integer; Unconditionally: Boolean)
  begin
  end;

  Type	Name	Description
  Record "Extended Text Header"	ExtendedTextHeader	[Pass by Reference] The extended text header.
  Boolean	AddedLines	[Pass by Reference] Print the text automatically.
  Code[10]	LanguageCode	The language code.
  Code[20]	JobNo	The job number.
  Code[20]	JobTaskNo	The job task number.
  Date	DocDate	The document date.
  Option	DocLineTheType	[Pass by Reference] The type of transaction that is being posted for the document line.
  Code[20]	DocLineTheNo	[Pass by Reference] The number of line type.
  Integer	DocLineNo	[Pass by Reference] The document line number.
  Boolean	Unconditionally	Print the text unconditionally.

• OnBeforeSetDocTextLineFields

  The event is used to set the fields for the document text line.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeSetDocTextLineFields(TableID: Integer; var DocType: Enum "NVXDT Document Type"; DocNo: Code[20]; var DocLineNo: Integer; var TextType: Enum "NVXDT Text Type"; var IsHandled: Boolean)
  begin
  end;

  Type	Name	Description
  Integer	TableID	The Table Id for this document.
  Enum "NVXDT Document Type"	DocType	[Pass by Reference] The document type.
  Code[20]	DocNo	The document number.
  Integer	DocLineNo	[Pass by Reference] The document line number.
  Enum "NVXDT Text Type"	TextType	[Pass by Reference] The text type.
  Boolean	IsHandled	[Pass by Reference] If set to true, the execution of the calling function is interrupted.

• OnBeforeShowTexts

  The event is used to show the texts.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeShowTexts(RecordRef: RecordRef; TextType: Enum "NVXDT Text Type"; var Handled: Boolean)
  begin
  end;

  Type	Name	Description
  RecordRef	RecordRef	The RecordRef that refers to the document.
  Enum "NVXDT Text Type"	TextType	The text type.
  Boolean	Handled	[Pass by Reference] If set to true, the execution of the calling function is interrupted.

• OnAfterSetDocTextLineFilterOnUnknownTableID

  The event is used to set the filter for the document text line of a non standard Business Central table.

  [IntegrationEvent(false, false)]
  local procedure OnAfterSetDocTextLineFilterOnUnknownTableID(TableID: Integer; DocType: Enum "NVXDT Document Type"; DocNo: Code[20]; DocLineNo: Integer; var DocTextLine: Record "NVXDT Doc. Text Line"; var Handled: Boolean)
  begin
  end;

  Type	Name	Description
  Integer	TableID	The Table Id for this document.
  Enum "NVXDT Document Type"	DocType	The document type.
  Code[20]	DocNo	The document number.
  Integer	DocLineNo	The document line number.
  Record "NVXDT Doc. Text Line"	DocTextLine	[Pass by Reference] The document text line.
  Boolean	Handled	[Pass by Reference] If set to true, the execution of the calling function is interrupted.

• OnAfterSetExtTextHeaderDocTypeFiltersOnUnknownTableID

  The event is used to set the filter for the extended text header of a non standard Business Central table.

  [IntegrationEvent(false, false)]
  local procedure OnAfterSetExtTextHeaderDocTypeFiltersOnUnknownTableID(TableID: Integer; DocType: Enum "NVXDT Document Type"; var ExtendedTextHeader: Record "Extended Text Header"; var Handled: Boolean)
  begin
  end;

  Type	Name	Description
  Integer	TableID	The Table Id for this document.
  Enum "NVXDT Document Type"	DocType	The document type.
  Record "Extended Text Header"	ExtendedTextHeader	[Pass by Reference] The extended text header.
  Boolean	Handled	[Pass by Reference] If set to true, the execution of the calling function is interrupted.

• OnAfterSetExtTextHeaderTableFilterOnUnknownTableID

  The event is used to set the filter for the extended text header of a non standard Business Central table.

  [IntegrationEvent(false, false)]
  local procedure OnAfterSetExtTextHeaderTableFilterOnUnknownTableID(TableID: Integer; DocLineTheType: Option; DocLineTheNo: Code[20]; var ExtendedTextHeader: Record "Extended Text Header"; var Handled: Boolean)
  begin
  end;

  Type	Name	Description
  Integer	TableID	The Table Id for this document.
  Option	DocLineTheType	The type of transaction that is being posted for the document line.
  Code[20]	DocLineTheNo	The number of line type.
  Record "Extended Text Header"	ExtendedTextHeader	[Pass by Reference] The extended text header.
  Boolean	Handled	[Pass by Reference] If set to true, the execution of the calling function is interrupted.

• OnInsertItemAttributeTextLineUnknownTableID

  The event is used to insert the item attribute text line of a non standard Business Central table.

  [IntegrationEvent(false, false)]
  local procedure OnInsertItemAttributeTextLineUnknownTableID(RecordRef: RecordRef; TableID: Integer; DocType: Enum "NVXDT Document Type"; DocNo: Code[20]; DocLineNo: Integer; TextType: Enum "NVXDT Text Type"; var AddedLines: Boolean; var IsHandled: Boolean)
  begin
  end;

  Type	Name	Description
  RecordRef	RecordRef	The RecordRef that refers to the document.
  Integer	TableID	The Table Id for this document.
  Enum "NVXDT Document Type"	DocType	The document type.
  Code[20]	DocNo	The document number.
  Integer	DocLineNo	The document line number.
  Enum "NVXDT Text Type"	TextType	The text type.
  Boolean	AddedLines	[Pass by Reference] Print the text automatically.
  Boolean	IsHandled	[Pass by Reference] If set to true, the execution of the calling function is interrupted.

• OnSetDocTextLineFieldTableNotDefined

  The event is used to set the fields for the document text line of a non standard Business Central table.

  [IntegrationEvent(false, false)]
  local procedure OnSetDocTextLineFieldTableNotDefined(TableID: Integer; var DocType: Enum "NVXDT Document Type"; DocNo: Code[20]; var DocLineNo: Integer; var TextType: Enum "NVXDT Text Type"; var IsHandled: Boolean)
  begin
  end;

  Type	Name	Description
  Integer	TableID	The Table Id for this document.
  Enum "NVXDT Document Type"	DocType	[Pass by Reference] The document type.
  Code[20]	DocNo	The document number.
  Integer	DocLineNo	[Pass by Reference] The document line number.
  Enum "NVXDT Text Type"	TextType	[Pass by Reference] The text type.
  Boolean	IsHandled	[Pass by Reference] If set to true, the execution of the calling function is interrupted.

• OnBeforeGetCustomerOrVendorTextCodes

  The event is used to get the customer or vendor Text Codes.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeGetCustomerOrVendorTextCodes(GlobalTableID: Integer; Customer: Record Customer; Vendor: Record Vendor; var IsHandled: Boolean)
  begin
  end;

  Type	Name	Description
  Integer	GlobalTableID	The Table Id for this document.
  Record Customer	Customer	The customer record.
  Record Vendor	Vendor	The vendor record.
  Boolean	IsHandled	[Pass by Reference] If set to true, the execution of the calling function is interrupted.

• OnCopyJobTextToDocText

  The event is used to copy the job text to the document text.

  [IntegrationEvent(false, false)]
  local procedure OnCopyJobTextToDocText(var FromNVXDTJobTextLine: Record "NVXDT Job Text Line"; var ToNVXDTDocTextLine: Record "NVXDT Doc. Text Line")
  begin
  end;

  Type	Name	Description
  Record "NVXDT Job Text Line"	FromNVXDTJobTextLine	[Pass by Reference] The job text line.
  Record "NVXDT Doc. Text Line"	ToNVXDTDocTextLine	[Pass by Reference] The document text line.

• OnAfterCopyJobTextLineToTempDocTextLineOnSetSequelFields

  The event is used to set the sequel fields for the document text line.

  [IntegrationEvent(false, false)]
  local procedure OnAfterCopyJobTextLineToTempDocTextLineOnSetSequelFields(var FromNVXDTJobTextLine: Record "NVXDT Job Text Line"; var TempNVXDTDocTextLine: Record "NVXDT Doc. Text Line");
  begin
  end;

  Type	Name	Description
  Record "NVXDT Job Text Line"	FromNVXDTJobTextLine	[Pass by Reference] The job text line.
  Record "NVXDT Doc. Text Line"	TempNVXDTDocTextLine	[Pass by Reference] The document text line.

• OnBeforeSetFilterOnCopyText

  The event is used to set the filter on copy text.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeSetFilterOnCopyText(FromRecordRef: RecordRef; ToRecordRef: RecordRef; DeleteFromText: Boolean)
  begin
  end;

  Type	Name	Description
  RecordRef	FromRecordRef	The RecordRef that refers to the document.
  RecordRef	ToRecordRef	The RecordRef that refers to the document.
  Boolean	DeleteFromText	Delete the text from the text line.

• OnAfterSetFilterOnCopyText

  The event is used to set the filter on copy text.

  [IntegrationEvent(false, false)]
  local procedure OnAfterSetFilterOnCopyText(FromRecordRef: RecordRef; ToRecordRef: RecordRef; DeleteFromText: Boolean)
  begin
  end;

  Type	Name	Description
  RecordRef	FromRecordRef	The RecordRef that refers to the document.
  RecordRef	ToRecordRef	The RecordRef that refers to the document.
  Boolean	DeleteFromText	Delete the text from the text line.

• OnBeforeFindDocTextLinesCopyTextNormal

  The event is used to filter document text lines in the CopyText function. The event is called before the document text lines are collected from the database.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeFindDocTextLinesCopyTextNormal(FromRecordRef: RecordRef; ToRecordRef: RecordRef; FromNVXDTDocTextLine: Record "NVXDT Doc. Text Line");
  begin
  end;

  Type	Name	Description
  RecordRef	FromRecordRef	The RecordRef that refers to the source document.
  RecordRef	ToRecordRef	The RecordRef that refers to the destination document.
  Record "NVXDT Doc. Text Line"	FromNVXDTDocTextLine	The document text line record.

• OnBeforeInsertCopyTextNormal

  The event is used to set the sequel fields for the document text lines when integrate new document types.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeInsertCopyTextNormal(var FromNVXDTDocTextLine: Record "NVXDT Doc. Text Line"; var ToNVXDTDocTextLine: Record "NVXDT Doc. Text Line"; var IsHandled: Boolean);
  begin
  end;

  Type	Name	Description
  Record "NVXDT Doc. Text Line"	FromNVXDTDocTextLine	[Pass by Reference] The source document text line.
  Record "NVXDT Doc. Text Line"	ToNVXDTDocTextLine	[Pass by Reference] The destination document text line.
  Boolean	IsHandled	[Pass by Reference] If set to true, the execution of the calling function is interrupted.

• OnBeforeFindDocTextLinesCopyTextPosted

  The event is used to filter document text lines in the CopyText function. The event is called before the document text lines are collected from the database.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeFindDocTextLinesCopyTextPosted(FromRecordRef: RecordRef; ToRecordRef: RecordRef; FromNVXDTDocTextLine: Record "NVXDT Posted Doc. Text Line");
  begin
  end;

  Type	Name	Description
  RecordRef	FromRecordRef	The RecordRef that refers to the source document.
  RecordRef	ToRecordRef	The RecordRef that refers to the destination document.
  Record "NVXDT Posted Doc. Text Line"	FromNVXDTDocTextLine	The document text line record.

• OnBeforeInsertCopyTextPosted

  The event is used to set the sequel fields for the document text lines when integrate new document types.

      
  [IntegrationEvent(false, false)]
  local procedure OnBeforeInsertCopyTextPosted(var FromPostedNVXDTDocTextLine: Record "NVXDT Posted Doc. Text Line"; var ToNVXDTDocTextLine: Record "NVXDT Doc. Text Line"; var IsHandled: Boolean);
  begin
  end;

  Type	Name	Description
  Record "NVXDT Posted Doc. Text Line"	FromPostedNVXDTDocTextLine	[Pass by Reference] The source document text line.
  Record "NVXDT Doc. Text Line"	ToNVXDTDocTextLine	[Pass by Reference] The destination document text line.
  Boolean	IsHandled	[Pass by Reference] If set to true, the execution of the calling function is interrupted.

• OnBeforeFindDocTextLinesCopyTextArchive

  The event is used to filter document text lines in the CopyText function. The event is called before the document text lines are collected from the database.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeFindDocTextLinesCopyTextArchive(FromRecordRef: RecordRef; ToRecordRef: RecordRef; FromNVXDTDocTextLine: Record "NVXDT Doc. Text Line Archive");
  begin
  end;

  Type	Name	Description
  RecordRef	FromRecordRef	The RecordRef that refers to the source document.
  RecordRef	ToRecordRef	The RecordRef that refers to the destination document.
  Record "NVXDT Doc. Text Line Archive"	FromNVXDTDocTextLine	The document text line record.

• OnBeforeInsertCopyTextArchive

  The event is used to set the sequel fields for the document text lines when integrate new document types.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeInsertCopyTextArchive(var FromNVXDTDocTextLineArchive: Record "NVXDT Doc. Text Line Archive"; var ToNVXDTDocTextLine: Record "NVXDT Doc. Text Line"; var IsHandled: Boolean);
  begin
  end;

  Type	Name	Description
  Record "NVXDT Doc. Text Line Archive"	FromNVXDTDocTextLineArchive	[Pass by Reference] The source document text line.
  Record "NVXDT Doc. Text Line"	ToNVXDTDocTextLine	[Pass by Reference] The destination document text line.
  Boolean	IsHandled	[Pass by Reference] If set to true, the execution of the calling function is interrupted.

• OnBeforeTestDocTextLineInsert

  The event is used to test the document text line insert.

  	
  [IntegrationEvent(false, false)]
  local procedure OnBeforeTestDocTextLineInsert(var NVXDTDocTextLine: Record "NVXDT Doc. Text Line"; var Result: Boolean; var IsHandled: Boolean)
  begin
  end;

  Type	Name	Description
  Record "NVXDT Doc. Text Line"	NVXDTDocTextLine	[Pass by Reference] The document text line.
  Boolean	Result	[Pass by Reference] The result of the test.
  Boolean	IsHandled	[Pass by Reference] If set to true, the execution of the calling function is interrupted.

• OnTestDocTextLineInsertUnknownTable

  The event is used to test the document text line insert of a non standard Business Central table.

  [IntegrationEvent(false, false)]
  local procedure OnTestDocTextLineInsertUnknownTable(var NVXDTDocTextLine: Record "NVXDT Doc. Text Line"; var Result: Boolean);
  begin
  end;

  Type	Name	Description
  Record "NVXDT Doc. Text Line"	NVXDTDocTextLine	[Pass by Reference] The document text line.
  Boolean	Result	[Pass by Reference] The result of the test.

• OnAfterTestDocTextLineInsert

  The event is used to test the document text line insert.

  [IntegrationEvent(false, false)]
  local procedure OnAfterTestDocTextLineInsert(var NVXDTDocTextLine: Record "NVXDT Doc. Text Line"; var Result: Boolean);
  begin
  end;

  Type	Name	Description
  Record "NVXDT Doc. Text Line"	NVXDTDocTextLine	[Pass by Reference] The document text line.
  Boolean	Result	[Pass by Reference] The result of the test.

• OnAfterResetSequelFields

  The event is used to reset the sequel fields.

  [IntegrationEvent(false, false)]
  local procedure OnAfterResetSequelFields(var NVXDTDocTextLine: Record "NVXDT Doc. Text Line");
  begin
  end;

  Type	Name	Description
  Record "NVXDT Doc. Text Line"	NVXDTDocTextLine	[Pass by Reference] The document text line.

• OnAfterResetSequelFieldsArchive

  The event is used to reset the sequel fields for the archive.

  [IntegrationEvent(false, false)]
  local procedure OnAfterResetSequelFieldsArchive(var NVXDTDocTextLineArchive: Record "NVXDT Doc. Text Line Archive");
  begin
  end;

  Type	Name	Description
  Record "NVXDT Doc. Text Line Archive"	NVXDTDocTextLineArchive	[Pass by Reference] The document text line archive.

• OnSetExtTextHeaderDocTypeFiltersSales

  The event is used to set the filter for the extended text header for sales.

  [IntegrationEvent(false, false)]
  local procedure OnSetExtTextHeaderDocTypeFiltersSales(var ExtendedTextHeader: Record "Extended Text Header"; TableID: Integer; DocType: Enum "NVXDT Document Type")
  begin
  end;

  Type	Name	Description
  Record "Extended Text Header"	ExtendedTextHeader	[Pass by Reference] The extended text header.
  Integer	TableID	The Table Id for this document.
  Enum "NVXDT Document Type"	DocType	The document type.

• OnSetExtTextHeaderDocTypeFiltersPurchase

  The event is used to set the filter for the extended text header for purchase.

  [IntegrationEvent(false, false)]
  local procedure OnSetExtTextHeaderDocTypeFiltersPurchase(var ExtendedTextHeader: Record "Extended Text Header"; TableID: Integer; DocType: Enum "NVXDT Document Type")
  begin
  end;

  Type	Name	Description
  Record "Extended Text Header"	ExtendedTextHeader	[Pass by Reference] The extended text header.
  Integer	TableID	The Table Id for this document.
  Enum "NVXDT Document Type"	DocType	The document type.

• OnSetExtTextHeaderDocTypeFiltersService

  The event is used to set the filter for the extended text header for service.

  [IntegrationEvent(false, false)]
  local procedure OnSetExtTextHeaderDocTypeFiltersService(var ExtendedTextHeader: Record "Extended Text Header"; TableID: Integer; DocType: Enum "NVXDT Document Type")
  begin
  end;

  Type	Name	Description
  Record "Extended Text Header"	ExtendedTextHeader	[Pass by Reference] The extended text header.
  Integer	TableID	The Table Id for this document.
  Enum "NVXDT Document Type"	DocType	The document type.

• OnSetExtTextHeaderDocTypeFiltersJob

  The event is used to set the filter for the extended text header for job.

  [IntegrationEvent(false, false)]
  local procedure OnSetExtTextHeaderDocTypeFiltersJob(var ExtendedTextHeader: Record "Extended Text Header"; TableID: Integer; DocType: Enum "NVXDT Document Type")
  begin
  end;

  Type	Name	Description
  Record "Extended Text Header"	ExtendedTextHeader	[Pass by Reference] The extended text header.
  Integer	TableID	The Table Id for this document.
  Enum "NVXDT Document Type"	DocType	The document type.

• OnBeforeSetSequelFieldsSales

  The event is used to set the sequel fields for sales.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeSetSequelFieldsSales(var NVXDTDocTextLine: Record "NVXDT Doc. Text Line"; FromNVXDTDocTextLine: Record "NVXDT Doc. Text Line"; MakeNew: Boolean; var IsHandled: Boolean);
  begin        
  end;

  Type	Name	Description
  Record "NVXDT Doc. Text Line"	NVXDTDocTextLine	[Pass by Reference] The document text line.
  Record "NVXDT Doc. Text Line"	FromNVXDTDocTextLine	The document text line from which the sequel fields are copied.
  Boolean	MakeNew	Make a new document text line.
  Boolean	IsHandled	[Pass by Reference] If set to true, the execution of the calling function is interrupted.

• OnAfterSetSequelFieldsSales

  The event is used to set the sequel fields for sales.

  [IntegrationEvent(false, false)]
  local procedure OnAfterSetSequelFieldsSales(var NVXDTDocTextLine: Record "NVXDT Doc. Text Line"; FromNVXDTDocTextLine: Record "NVXDT Doc. Text Line"; MakeNew: Boolean);
  begin        
  end;

  Type	Name	Description
  Record "NVXDT Doc. Text Line"	NVXDTDocTextLine	[Pass by Reference] The document text line.
  Record "NVXDT Doc. Text Line"	FromNVXDTDocTextLine	The document text line from which the sequel fields are copied.
  Boolean	MakeNew	Make a new document text line.

• OnBeforeSetSequelFieldsPurchase

  The event is used to set the sequel fields for purchase.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeSetSequelFieldsPurchase(var NVXDTDocTextLine: Record "NVXDT Doc. Text Line"; FromNVXDTDocTextLine: Record "NVXDT Doc. Text Line"; MakeNew: Boolean; var IsHandled: Boolean);
  begin        
  end;

  Type	Name	Description
  Record "NVXDT Doc. Text Line"	NVXDTDocTextLine	[Pass by Reference] The document text line.
  Record "NVXDT Doc. Text Line"	FromNVXDTDocTextLine	The document text line from which the sequel fields are copied.
  Boolean	MakeNew	Make a new document text line.
  Boolean	IsHandled	[Pass by Reference] If set to true, the execution of the calling function is interrupted.

• OnAfterSetSequelFieldsPurchase

  The event is used to set the sequel fields for purchase.

  [IntegrationEvent(false, false)]
  local procedure OnAfterSetSequelFieldsPurchase(var NVXDTDocTextLine: Record "NVXDT Doc. Text Line"; FromNVXDTDocTextLine: Record "NVXDT Doc. Text Line"; MakeNew: Boolean);
  begin        
  end;

  Type	Name	Description
  Record "NVXDT Doc. Text Line"	NVXDTDocTextLine	[Pass by Reference] The document text line.
  Record "NVXDT Doc. Text Line"	FromNVXDTDocTextLine	The document text line from which the sequel fields are copied.
  Boolean	MakeNew	Make a new document text line.

• OnBeforeSetSequelFieldsService

  The event is used to set the sequel fields for service.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeSetSequelFieldsService(var NVXDTDocTextLine: Record "NVXDT Doc. Text Line"; FromNVXDTDocTextLine: Record "NVXDT Doc. Text Line"; MakeNew: Boolean; var IsHandled: Boolean);
  begin        
  end;

  Type	Name	Description
  Record "NVXDT Doc. Text Line"	NVXDTDocTextLine	[Pass by Reference] The document text line.
  Record "NVXDT Doc. Text Line"	FromNVXDTDocTextLine	The document text line from which the sequel fields are copied.
  Boolean	MakeNew	Make a new document text line.
  Boolean	IsHandled	[Pass by Reference] If set to true, the execution of the calling function is interrupted.

• OnAfterSetSequelFieldsService

  The event is used to set the sequel fields for service.

  [IntegrationEvent(false, false)]
  local procedure OnAfterSetSequelFieldsService(var NVXDTDocTextLine: Record "NVXDT Doc. Text Line"; FromNVXDTDocTextLine: Record "NVXDT Doc. Text Line"; MakeNew: Boolean);
  begin        
  end;

  Type	Name	Description
  Record "NVXDT Doc. Text Line"	NVXDTDocTextLine	[Pass by Reference] The document text line.
  Record "NVXDT Doc. Text Line"	FromNVXDTDocTextLine	The document text line from which the sequel fields are copied.
  Boolean	MakeNew	Make a new document text line.

• OnBeforeSetSequelFieldsJob

  The event is used to set the sequel fields for job.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeSetSequelFieldsJob(var NVXDTDocTextLine: Record "NVXDT Doc. Text Line"; FromNVXDTDocTextLine: Record "NVXDT Doc. Text Line"; MakeNew: Boolean; var IsHandled: Boolean);
  begin
  end;

  Type	Name	Description
  Record "NVXDT Doc. Text Line"	NVXDTDocTextLine	[Pass by Reference] The document text line.
  Record "NVXDT Doc. Text Line"	FromNVXDTDocTextLine	The document text line from which the sequel fields are copied.
  Boolean	MakeNew	Make a new document text line.
  Boolean	IsHandled	[Pass by Reference] If set to true, the execution of the calling function is interrupted.

• OnAfterSetSequelFieldsJob

  The event is used to set the sequel fields for job.

  [IntegrationEvent(false, false)]
  local procedure OnAfterSetSequelFieldsJob(var NVXDTDocTextLine: Record "NVXDT Doc. Text Line"; FromNVXDTDocTextLine: Record "NVXDT Doc. Text Line"; MakeNew: Boolean);
  begin
  end;

  Type	Name	Description
  Record "NVXDT Doc. Text Line"	NVXDTDocTextLine	[Pass by Reference] The document text line.
  Record "NVXDT Doc. Text Line"	FromNVXDTDocTextLine	The document text line from which the sequel fields are copied.
  Boolean	MakeNew	Make a new document text line.

• OnBeforeSetSequelFieldsJobPlanningLine

  The event is used to set the sequel fields for job planning line.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeSetSequelFieldsJobPlanningLine(var NVXDTJobTextLine: Record "NVXDT Job Text Line"; MakeNew: Boolean; var IsHandled: Boolean);
  begin
  end;

  Type	Name	Description
  Record "NVXDT Job Text Line"	NVXDTJobTextLine	[Pass by Reference] The job text line.
  Boolean	MakeNew	Make a new job text line.
  Boolean	IsHandled	[Pass by Reference] If set to true, the execution of the calling function is interrupted.

• OnAfterSetSequelFieldsJobPlanningLine

  The event is used to set the sequel fields for job planning line.

  [IntegrationEvent(false, false)]
  local procedure OnAfterSetSequelFieldsJobPlanningLine(var NVXDTJobTextLine: Record "NVXDT Job Text Line"; MakeNew: Boolean);
  begin
  end;

  Type	Name	Description
  Record "NVXDT Job Text Line"	NVXDTJobTextLine	[Pass by Reference] The job text line.
  Boolean	MakeNew	Make a new job text line.

• OnAfterSetSequelFields

  The event is used to set the sequel fields.

  [IntegrationEvent(false, false)]
  local procedure OnAfterSetSequelFields(var ToNVXDTDocTextLine: Record "NVXDT Doc. Text Line"; var FromNVXDTDocTextLine: Record "NVXDT Doc. Text Line"; MakeNew: Boolean);
  begin
  end;

  Type	Name	Description
  Record "NVXDT Doc. Text Line"	ToNVXDTDocTextLine	[Pass by Reference] The document text line.
  Record "NVXDT Doc. Text Line"	FromNVXDTDocTextLine	The document text line from which the sequel fields are copied.
  Boolean	MakeNew	Make a new document text line.

• OnExtTextToDocTextOnBeforeFindExtendedTextLines

  The event is used to filter extended text lines when converting extended text to document text.

  [IntegrationEvent(false, false)]
  local procedure OnExtTextToDocTextOnBeforeFindExtendedTextLines(var ExtendedTextHeader: Record "Extended Text Header"; var ExtendedTextLine: Record "Extended Text Line"; TableID: Integer; DocType: Enum "NVXDT Document Type"; DocNo: Code[20]; DocLineNo: Integer; TextType: Enum "NVXDT Text Type")
  begin
  end;

  Type	Name	Description
  Record "Extended Text Header"	ExtendedTextHeader	[Pass by Reference] The extended text header.
  Record "Extended Text Line"	ExtendedTextLine	[Pass by Reference] The extended text line.
  Integer	TableID	The Table Id for this document.
  Enum "NVXDT Document Type"	DocType	The document type.
  Code[20]	DocNo	The document number.
  Integer	DocLineNo	The document line number.
  Enum "NVXDT Text Type"	TextType	The text type.

Codeunit - NVXDT File Management

• OnBeforeExportOnBeforeDialog

  The event is used to export the file before the dialog.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeExportOnBeforeDialog(ClientFileName: Text[1024]; var TempBlob: Codeunit "Temp Blob"; var IsHandled: Boolean)
  begin
  end;

  Type	Name	Description
  Text[1024]	ClientFileName	The client file name.
  TempBlob	[Pass by Reference] The temporary blob where the binary stream is to be saved.
  IsHandled	[Pass by Reference] If set to true, the execution of the calling function is interrupted.

• OnAfterExportOnAfterExport

  The event is used to export the file after the export.

  [IntegrationEvent(false, false)]
  local procedure OnAfterExport(ClientFileName: Text[1024]; var TempBlob: Codeunit "Temp Blob")
  begin
  end;

  Type	Name	Description
  Text[1024]	ClientFileName	The client file name.
  Codeunit "Temp Blob"	TempBlob	[Pass by Reference] The temporary blob where the binary stream is to be saved.

• OnBeforeImportOnBeforeDialog

  The event is used to import the file before the dialog.

  [IntegrationEvent(false, false)]
  local procedure OnBeforeImportOnBeforeDialog(ClientFileName: Text[1024]; var TempBlob: Codeunit "Temp Blob"; FilterString: Text[250]; ExtFilterString: Text[250]; var IsHandled: Boolean)
  begin
  end;

  Type	Name	Description
  Text[1024]	ClientFileName	The client file name.
  Codeunit "Temp Blob"	TempBlob	[Pass by Reference] The temporary blob where the binary stream is to be saved.
  Text[250]	FilterString	The filter string.
  Text[250]	ExtFilterString	The extension filter string.
  Boolean	IsHandled	[Pass by Reference] If set to true, the execution of the calling function is interrupted.

• OnAfterImport

  The event is used to import the file after the import.

  [IntegrationEvent(false, false)]
  local procedure OnAfterImport(ClientFileName: Text[1024]; var TempBlob: Codeunit "Temp Blob")
  begin
  end;

  Type	Name	Description
  Text[1024]	ClientFileName	The client file name.
  Codeunit "Temp Blob"	TempBlob	[Pass by Reference] The temporary blob where the binary stream is to be saved.

Codeunit - NVXDT Placeholder Mgt.

• OnBeforeConvertPlaceholder

  The event is used to convert the placeholder.

  [BusinessEvent(true)]
  local procedure OnBeforeConvertPlaceholder(var Text: Text; var RecordRef: RecordRef; var IsHandled: Boolean)
  begin
  end;

  Type	Name	Description
  Text	Text	[Pass by Reference] The text to be converted.
  RecordRef	RecordRef	[Pass by Reference] The RecordRef that refers to the document.
  Boolean	IsHandled	[Pass by Reference] If set to true, the execution of the calling function is interrupted.

• OnAfterConvertPlaceholder

  The event is used to convert the placeholder.

  [BusinessEvent(true)]
  local procedure OnAfterConvertPlaceholder(var Text: Text)
  begin
  end;

  Type	Name	Description
  Text	Text	[Pass by Reference] The text to be converted.

Codeunit - NVXDT Report Management

• OnGetReportText

  The event is used to get the report text.

  [IntegrationEvent(false, false)]
  procedure OnGetReportText(var RecordRef: RecordRef; NVXDTTextType: enum "NVXDT Text Type"; AsHTML: Boolean; var Output: Text; var IsHandled: Boolean);
  begin
  end;

  Type	Name	Description
  RecordRef	RecordRef	[Pass by Reference] The RecordRef that refers to the document.
  Enum "NVXDT Text Type"	NVXDTTextType	The type of the text.
  Boolean	AsHTML	True if the text is in HTML format; otherwise, false.
  Text	Output	[Pass by Reference] The output text.
  Boolean	IsHandled	[Pass by Reference] If set to true, the execution of the calling function is interrupted.

Docs  /  App  /  NAVAX Document Text  /  Information for Developers
 Events

Docs  /  App  /  NAVAX Document Text  /  Appendix
 NAVAX License Management

Trial Version

Request License

Activate/Update License

Terms & Conditions

https://www.navax.app/EULA.php?L=en

Data Security

https://www.navax.app/privacyStatement.php?L=en

Submit Rating

Docs  /  App  /  NAVAX Document Text  /  Appendix
 Installation Notes

Publish and Install the Extension

[Microsoft Learn] Business Central - Publishing and Installing an Extension

System Requirements

• Microsoft Dynamics 365 Business Central - Version 21.0 or higher
• Permissions: SUPER user or corresponding permissions for extension management
• Internet Connection: Required for installation via AppSource

Dependencies

• NAVAX Document Text Base

  ID: 2f97a39f-60f1-45d1-8bb2-7497bee60684

• NAVAX Extension Base

  ID: 2f4cb42d-6e2a-4708-a5e2-3ec5f32f20e9 For more information, see [Docs] NAVAX Extension Base

On-Premises

• 70714775 NCDT Document Text by NAVAX
• 1010860 Extension Base by NAVAX

Installation

Installation via AppSource (Cloud)

1. Open Microsoft Dynamics 365 Business Central
2. Search for Extension Management via "Tell me what you want to do"
3. Click Marketplace and search for "NAVAX Document Text"
4. Click Free Trial or Get it now, depending on the licensing model
5. Follow the installation instructions
6. After installation: Open the Document Text Setup and perform the basic configuration For more information, see Setup, Document Text Setup.

Installation On-Premises

1. Ensure that the required Granules (see above) are available
2. Download the extension file (.app)
3. Open Extension Management in Business Central
4. Click Upload and select the .app file
5. Click Deploy to install the extension
6. After installation: Open the Document Text Setup and perform the basic configuration For more information, see Setup, Document Text Setup.

Troubleshooting Installation

Problem: Extension cannot be installed

• Check whether NAVAX Extension Base is installed
• Ensure that you have SUPER permissions
• Check the Business Central version (at least version 21.0 required)

Problem: Document Text Setup is not visible after installation

• Check in Extension Management whether the extension is shown as "Installed"
• Sign out and sign in again
• Check your permissions

Problem: On-premises installation fails (Granules)

External Addresses

• https://www.navax.app

  For licensing, calling the online help and performing some actions, access to https://www.navax.app must be granted.
  
  Public IP from www.navax.app for setting firewall access:
  94.136.22.236, Port: TCP/443
  
  Checking the connection to https://www.navax.app using PS:
  Test-NetConnection navax.app -port 443
  (PS must be performed with the M-Tier service user)
  
  CRL Servers
  In addition, the following CRL Servers must also be accessible for the certificate check:
  https://certificates.godaddy.com/*
  http://crl.godaddy.com/*
  or their IP: 192.124.249.36

Support and Contact

• General, NAVAX Document Text
• Working with the App, FAQ and Troubleshooting

Docs  /  App  /  NAVAX Document Text  /  Appendix
 Release Notes

Version 26.3.3.1

• Note

  This version is also available as a downgrade version for Business Central 21.

• Corrections

• • The upgrade routine has been optimized to perform the update to the new version faster and more efficiently.

Version 26.3.3.0

• Improvements

• • NAVAX Document Text now also supports prepayment documents.
  • New events added for extensibility for partners and customers. Information for Developers, Extending NAVAX Document Text

• Modifications

• • Field Payment Terms Text added to the Posted Purchase Invoice.
  • Instead of the field Project Quote, the standard field Project is now used. An upgrade routine was created so that existing extended texts used for project quotes are switched to the new field.

    Note

    This does not apply to the downgrade version for Business Central 21. The Project Quote field remains in place there.

• Corrections

• • Tooltips on the Document Text Lines page corrected.

Version 26.3.2.1

• Improvements

• • Improved rendering of document text lines in posted documents: formatting (indentation, padding, styles, line breaks) is now applied consistently with open documents and reports for better readability on pages and printouts.
  • Text Editor is now also available in posted documents.
  • The automatic license renewal no longer tries to update the license directly, but instead automatically starts a job queue. During this process, all licenses for which automatic license renewal is enabled are checked and updated if necessary. For more information, see Appendix, NAVAX License Management.

Version 26.3.2.0

• Improvements

• • Archiving functionality of project document texts added.

• Modifications

• • NAVAX Extension Base extension update.
    For more information, see [Docs] NAVAX Extension Base - Release Notes

• Corrections

• • Error when selecting placeholders via the standard text modules corrected.

Version 26.3.1.0

• Important

  For On-Premises an update of the License or the following granules is required:

  • 70714775 NAVAX Document Text

• Improvements

• • New feature: Salesperson/Purchaser prefix and suffix texts.
  • Archived document texts are now available in all available archive areas.
  • Field Payment Terms Text added to the Project Card.

• Modifications

• • The event methods have been adapted to the requirements of Business Central Version 26 and extended with additional parameters to improve functionality and integration flexibility. For more information, see Information for Developers, Extending NAVAX Document Text.
  • The actions Beginning Text and Ending Text have been organized into the appropriate action groups on the relevant pages, making them clearer and accessible according to the standard navigation of Business Central.
  • The field Shipment Method Text was displayed on some pages even when the associated Shipment Method field was still hidden and only became visible after clicking Show more. The visibility of both fields has now been unified.
  • NAVAX Extension Base extension update.
    For more information, see [Docs] NAVAX Extension Base - Release Notes
  • Removal of outdated code parts.

• Corrections

• • When creating project planning lines, the function for document texts was not applied. Instead, lines of type Comment were inserted according to the configured Standard Text Code.

    Important

    This bug fix requires at least Application version 26.2.34746.35167 of Business Central, as some event subscribers necessary for it were not available in previous versions.
  • When printing the Proforma Invoice, the associated document texts were not displayed in the NVXDT Standard Layout.
  • Display errors in the Project Quote report have been fixed so that all relevant fields and texts are now displayed correctly. In addition, the layout has been revised and adapted to the current Business Central standard.

Version 21.3.0.2

• Corrections

• • An error in the upgrade and installation routine has been fixed.

Version 21.3.0.1

• Corrections

• • An error in the upgrade and installation routine has been fixed. This error caused an incorrect entry in the license management.

Version 21.3.0.0

• New product name

• • The NCDT Document Text extension has been renamed to NAVAX Document Text.

• Improvements

• • New events added for extensibility for partners and customers. Information for Developers, Extending NAVAX Document Text

Version 21.2.2.2

• Improvements

• • New events added for extensibility for partners and customers. Information for Developers, Extending NAVAX Document Text

• Corrections

• • Fixed error when adding new lines in project planning and service item lines.

Version 21.2.2.1

• Improvements

• • New events added for extensibility for partners and customers. Information for Developers, Extending NAVAX Document Text

• Modifications

• • Placeholders that are not filled in the document are now replaced with empty values.
  • Removal of outdated code parts.

• Corrections

• • Fixed an error when creating a service document.

Version 21.2.2.0

• Improvements

• • New events added for extensibility for partners and customers. Information for Developers, Extending NAVAX Document Text

• Modifications

• • Removal of outdated code parts.
  • The resourceExposurePolicy settings of the extension have been changed.
  • Adjusted column widths for all text lines where formatting is available.
  • New report extension Purchase - Order added.
  • Change of relevant captions (descriptions) in the projects area.

• Corrections

• • Missing indentation option added to the posted document text lines.

Version 21.2.1.0

• Improvements

• • New feature padding top/bottom added. With these new formatting options, you can expand the lines upwards or downwards to create spacing between the lines.
  • New feature indentation added. This new formatting option can be used to implement an indent at the beginning of the line.

• Modifications

• • The summaries in the report layouts have been set.
  • Renamed Job to Project according new Business Central name convention.

• Corrections

• • Correction of the event subscribers triggering the appending of document lines to prevent errors when adding new document lines.
  • When creating a sales order or a sales invoice, texts that were intended for the proforma invoice or the invoice draft (sales invoice) were not appended. This made it impossible to print these documents with the corresponding text lines.

Version 21.2.0.3

• Improvements

• • The Shipment Method Text has been added on the Service Order page.
  • New functions Disable sequel fields and Enable sequel fields to simultaneously enable/disable the document sequel fields in the Extended Texts.

• Modifications

• • The logo of the extension has been changed.

• Corrections

• • When posting a warehouse shipment with option delivery or delivery and invoicing out of a service order, the error message 'Service Shipment Line' does not exist. Identifying fields and values: Document no.='xxxxxx',Line no.='xxxxxx'
  • As a result of an error message, it was not possible to create a service order or a service invoice directly from the customer card or customer list.
  • The document sequel fields for the line texts of the service item lines were not shown or filled correctly.
  • The payment terms text was not automatically pulled in service documents.

Version 21.2.0.2

• Corrections

• • Error when posting a service order when using the Ship or Invoice options.
  • In the Service Contract Quotes and Service Contracts, the field Service Contract Group Text was not included, so it could not be used when creating custom layouts.