Study guide

1.2 Configuration Packages & RapidStart Worksheets

Microsoft Dynamics 365 Business Central Functional Consultant MB-800

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Company Creation & Data Migration

1.1 Creating Companies & Assisted Setup Wizards 1.2 Configuration Packages & RapidStart Worksheets 1.3 Opening Balances & Data Migration Strategies

2 Chapter 2: Security, Profiles & Auditing

2.1 Users, User Setup & Role Center Profiles 2.2 Permission Sets & Security Group Management 2.3 Security Filters, Change Log & Security Auditing

3 Chapter 3: Core System Configuration, Number Series & Copilot

3.1 Company Information, Number Series & Job Queues 3.2 Report Layout Management & Copilot AI Capabilities

4 Chapter 4: Dimensions Architecture & Governance

4.1 Dimension Concepts & Dimension Values 4.2 Global Dimensions vs Shortcut Dimensions 4.3 Default Dimensions, Combinations & Priorities

5 Chapter 5: Workflows & Approvals

5.1 Native Workflow Templates & Approval Hierarchy 5.2 Workflow User Groups & Notification Configuration

6 Chapter 6: Financial Setup, Periods & Currencies

6.1 General Ledger Setup & Accounting Periods 6.2 Payment Terms, Payment Methods & Deferrals 6.3 Multi-Currency Setup & Exchange Rates

7 Chapter 7: Chart of Accounts, Categories & Allocations

7.1 Chart of Accounts Structure & G/L Account Cards 7.2 Account Categories, Subcategories & Financial Reporting 7.3 General Ledger Allocation Accounts & Sharing

8 Chapter 8: Posting Groups & Posting Setup

8.1 Specific Posting Groups: Customer, Vendor, Bank & Inventory 8.2 General Posting Groups & General Posting Setup Matrix 8.3 Inventory Posting Setup & Alternative Posting Groups

9 Chapter 9: General Journals & Recurring Methods

9.1 Bank Account Cards & Posting Setup 9.2 General Journal Templates, Batches & Number Series 9.3 Recurring General Journals & Allocation Methods

10 Chapter 10: Accounts Payable & Accounts Receivable Setup

10.1 Purchases & Payables Setup & Vendor Master 10.2 Sales & Receivables Setup & Customer Master 10.3 Payment Journals, Cash Receipts & Payment Registration Setup

11 Chapter 11: Fixed Assets Setup & Depreciation Books

11.1 Fixed Asset Setup, Classes & Depreciation Books 11.2 Fixed Asset Cards, Main/Component Assets & Depreciation Methods

12 Chapter 12: Inventory Setup, Costing & Locations

12.1 Inventory Setup, Item Types, Categories & Variants 12.2 Costing Methods (FIFO, LIFO, Average, Standard) & Ledger Architecture 12.3 Locations, Transfer Routes & Stockkeeping Units (SKUs)

13 Chapter 13: Logistics Master Data, Pricing & Discounts

13.1 Shipping Agents, Locations & Vendor Lead Times 13.2 Sales Prices, Purchase Prices & Price Lists 13.3 Line Discounts, Invoice Discounts & Thresholds

14 Chapter 14: User Interface, Views, Inspection & Excel

14.1 Personalization, Profile Customization & Designer 14.2 Searching, Advanced Filters, Saved Views & Page Inspection 14.3 Edit in Excel, OneDrive & Data Analysis Mode

15 Chapter 15: Purchase & Sales Order Execution

15.1 Purchase Orders, Receiving, Over-Receipt & Undo 15.2 Purchase Invoicing, Recurring Lines & Blanket Orders 15.3 Sales Quotes, Availability Checks & Order Conversion 15.4 Sales Shipping, Invoicing, Undo & Blanket Orders

16 Chapter 16: Invoices, Credit Memos & Document Corrections

16.1 Direct Invoices, Credit Memos & Document Reopening 16.2 Correct, Cancel & Corrective Credit Memo Procedures 16.3 Combined Shipments/Receipts & Prepayment Workflows

17 Chapter 17: Cash Management, Bank Reconciliation & Ledger Applications

17.1 Processing Payment Journals & Cash Receipt Registrations 17.2 Applying, Unapplying & Reversing Customer/Vendor Entries 17.3 Bank Account Reconciliation & Statement Matching Rules

18 Chapter 18: Operational Adjustments, Inventory & Asset Accounting

18.1 Exchange Rate Adjustments & Dimension Corrections 18.2 Inventory Adjustments, Transfers & Physical Counting 18.3 Fixed Asset Acquisitions, Depreciation Runs & Disposals

1.2 Configuration Packages & RapidStart Worksheets

Key Takeaways Explain This Topic AI

RapidStart Services utilizes Configuration Packages to stage, validate, and commit legacy data into Business Central tables via structured Excel templates.

Configuration Worksheets organize migration projects hierarchically into Areas, Groups, and Tables while tracking real-time record counts and promoted entities.

Calculated FlowFields (e.g., Customer Balance) and system-managed fields (SystemId, Timestamp) must be excluded from packages to avoid fatal import errors.

The Validate Field setting executes AL OnValidate triggers to enforce relational integrity, verifying foreign keys and code formatting during staging and application.

Data migration packages must be imported in a strict four-tier dependency sequence: Foundation Setup, Posting Architecture, Master Data, and Transactional Openings.

Last updated: September 2026

1.2 Configuration Packages & RapidStart Worksheets

Quick Summary: RapidStart Services provides the core data migration and bulk configuration engine in Dynamics 365 Business Central. Consultants organize data migration using the Configuration Worksheet (structured by functional Areas, Groups, and Tables) and build Configuration Packages to export and import data via Microsoft Excel templates. When configuring tables, calculated FlowFields and system-managed metadata fields must be excluded. Data moves through an intermediate staging area where validation errors are diagnosed and resolved in the Config. Package Errors window before records are committed into live application tables.

RapidStart Services Architecture & Core Terminology

In Dynamics 365 Business Central, bulk data onboarding and setup replication are governed by RapidStart Services . RapidStart provides an auditable, two-stage data ingestion pipeline:

Staging / Intermediate Layer: Legacy data imported from external sources (typically Microsoft Excel workbooks) is loaded into staging tables ( Config. Package Record and Config. Package Data ). At this stage, no live application tables or ledgers are modified.

Validation & Application Layer: The staged data is validated against Business Central business logic. Once all schema, data type, and relational integrity constraints pass, the data is "applied" to the live operational tables.

This architecture ensures that corrupt, unvalidated, or structurally incomplete legacy records cannot directly breach the operational database.

The Configuration Worksheet: Planning & Project Scoping

The Configuration Worksheet ( Alt+Q -> type Configuration Worksheet ) provides a hierarchical project management interface for planning and monitoring data migration across the entire ERP deployment. Configuration Worksheet Hierarchy:

  • Line Type: Area -> [FINANCE] (Functional Domain)
  • Line Type: Group -> [GENERAL LEDGER] (Functional Subsystem)
  • Line Type: Table -> Table ID 15: G/L Account (Database Table Entity)
  • Line Type: Table -> Table ID 98: General Ledger Setup
  • Line Types in the Worksheet

Area: Defines the broad functional domain (e.g., Financials , Sales , Purchasing , Inventory , Fixed Assets ). Used strictly for grouping and visual hierarchy.

Group: Establishes a logical subsystem under an Area (e.g., Receivables , Payables , Cost Accounting ).

Table: Represents an actual Business Central database table, referenced by its unique integer Table ID (e.g., Table 15 G/L Account , Table 18 Customer , Table 23 Vendor , Table 27 Item , Table 92 Customer Posting Group ).

Key Worksheet Columns & Operational Metrics

Table ID & Table Caption: Identifies the underlying database table.

No. of Records: Queries the database in real time to display the total count of existing records in that table. This metric allows consultants to immediately confirm whether a table is currently empty or already populated.

Promoted Table: A boolean flag designating critical path tables that should appear highlighted and prioritized during package compilation.

Package Code: Identifies which Configuration Package currently manages the table.

Assigned User ID: Enables project managers to assign specific functional tables to designated team members for data cleansing and sign-off.

Configuration Package Definition & Table Selection

A Configuration Package ( Alt+Q -> type Configuration Packages ) is the actual deployment artifact that bundles selected tables, field mapping rules, filtering parameters, and data payloads.

When a consultant adds tables to a Configuration Package Card, fine-grained field and validation controls must be established under the Tables subpage: UI Navigation Path:

  • Tell Me (Alt+Q) -> Configuration Packages -> Open Package Card -> Tables FastTab -> Action: Table -> Fields
  • Field Selection & Excluding Invalid Field Types

Selecting Table -> Fields opens the Config. Package Field List . By default, Business Central selects every field in the table. However, consultants must explicitly deselect specific field types to avoid fatal import failures:

FlowFields (Calculated Fields): Fields such as Balance (LCY) on Table 18 (Customer) or Net Change on Table 15 (G/L Account) do not exist as stored data columns in SQL. They are dynamically calculated at runtime by querying underlying ledger tables (e.g., Detailed Customer Ledger Entries). Attempting to import values into a FlowField triggers a validation failure because calculated fields are strictly read-only.

FlowFilters: Dynamic runtime filtering parameters (such as Date Filter or Global Dimension 1 Filter ) used in FlowField calculation formulas. They do not store data and must be excluded.

System-Managed Metadata Fields: Internal system columns maintained exclusively by the platform kernel, including SystemId , SystemCreatedAt , SystemCreatedBy , SystemModifiedAt , SystemModifiedBy , and timestamp . These fields cannot be manually updated or written via RapidStart.

Table Filters

Under Table -> Filters , consultants can define export filter criteria. For example, when exporting existing Customer master records to build a migration template, adding the filter Blocked = No prevents inactive or obsolete legacy accounts from being extracted into the workbook.

Field Validation Rules: The "Validate Field" Toggle

On the Config. Package Field List , every field has an Include Field checkbox and a Validate Field checkbox:

Include Field: Determines whether the field is exported to the Excel template and parsed during import.

Validate Field: Controls whether the Business Central application server executes the AL OnValidate trigger code when data is imported into that field.

When Enabled (Standard Best Practice): Business Central enforces business logic rules, verifies that referenced foreign keys exist in parent tables (e.g., verifying that a Customer Posting Group entered in the customer record actually exists in Table 92), and formats strings.

When Disabled (Bypass): The data is inserted directly into the table without executing validation code. While this can expedite processing or permit temporary ingestion of non-standard codes, it bypasses database integrity checks and can cause corrupt foreign key relationships. It should only be disabled under strict, exceptional circumstances.

Processing Rules & Processing Codeunits

Under Table -> Processing Rules , consultants can assign custom AL processing codeunits. This enables custom data transformations, conditional record generation, or automated assignment of default dimensions during the package application phase.

The RapidStart Data Migration Lifecycle: Step-by-Step

The end-to-end execution of a Configuration Package follows a disciplined five-stage lifecycle: RapidStart Execution Pipeline:

  • [1. Define Package & Tables]
  • │
  • ▼
  • [2. Export to Excel Template]
  • │ (Populate cleansed legacy data)
  • ▼
  • [3. Import from Excel]
  • │ (Loads data into Staging Tables)
  • ▼
  • [4. Validate & Diagnose] ──► [Config. Package Errors Window]
  • │ (Fix in staging or re-import)
  • ▼ (0 Errors)
  • [5. Apply Package] ──► [Live Business Central Tables]
  • Stage 1: Exporting the Excel Template

On the Configuration Package Card, selecting Package -> Export to Excel generates an .xlsx workbook. Each table included in the package becomes an individual worksheet tab named after the Table ID and Caption. The workbook incorporates built-in schema definitions:

Column headers contain field captions, technical field IDs, data types (e.g., Text[50] , Code[20] , Decimal , Boolean ), and maximum field lengths.

Primary Key fields are marked with an asterisk ( * ) to indicate that they are mandatory unique identifiers.

Stage 2: Data Cleansing & Excel Guidelines

When populating the Excel template, consultants must adhere to strict formatting conventions:

Do Not Modify Sheet Names or Headers: Renaming worksheet tabs, deleting technical header rows, or reordering columns can cause the import parser to reject the file.

Leading Zeros in Code Fields: Account numbers, postal codes, and customer codes with leading zeros (e.g., 00123 ) must be formatted as Text in Excel. If formatted as General/Number, Excel strips the leading zeros, creating invalid master codes.

Case Sensitivity on Code Fields: Values in Code fields are automatically converted to uppercase by Business Central, but referenced foreign keys must match existing setup codes exactly.

Date Formats: Dates must conform to standard ISO formats ( YYYY-MM-DD ) or the regional settings of the Business Central user account.

Stage 3: Importing from Excel into Staging

Selecting Package -> Import from Excel reads the populated workbook into Business Central. The records are placed into intermediate staging tables. At this stage, the No. of Package Records column reflects the imported row count, while live database tables remain completely untouched.

Stage 4: Error Diagnosis in the Package Errors Window

Upon import, Business Central automatically executes schema and type validation. If errors occur, the No. of Package Errors column highlights the total error count in red text.

Drilling into the error count opens the Config. Package Errors window, which provides comprehensive diagnostic data:

Field Caption: Pinpoints the exact field that failed validation.

Invalid Value: Displays the rejected text or number from the Excel cell.

Error Text: Provides the exact AL error message (e.g., "The field Customer Posting Group of table Customer contains a value (RETAIL) that cannot be found in the related table (Customer Posting Group)." ).

Consultants have two options for resolving errors:

Direct In-App Staging Correction: Open the Config. Package Records subpage, correct the invalid value directly in the grid, and select Validate .

Template Correction & Re-Import: Correct the source Excel spreadsheet and re-import the file. Business Central updates the existing staged records based on primary key matching.

Stage 5: Applying the Package

Once the error count reaches zero, the consultant selects Apply Package (or Apply Data for an individual table). Business Central commits the staged records into the live database tables, creating operational records.

Relational Data Migration Sequencing & Dependency Tiers

Because Business Central rigorously enforces relational database integrity during validation, importing tables out of order results in cascading validation failures. Data migration must proceed through four sequential tiers:

Tier Migration Category Representative Table IDs Dependency Rationale

Tier 1: Foundation Setup System parameters, units, currencies, and codes Table 4 Currency ; Table 10 Country/Region ; Table 204 Unit of Measure ; Table 308 No. Series ; Table 3 Payment Terms Must exist before any financial setup or master data can reference currency codes, postal addresses, or payment conditions.

Tier 2: Posting & Accounting Infrastructure Chart of Accounts and posting matrices Table 15 G/L Account ; Table 92 Customer Posting Group ; Table 93 Vendor Posting Group ; Table 252 General Posting Setup ; Table 352 Default Dimension Master data (Customers, Vendors, Items) cannot be validated without valid G/L accounts and posting groups assigned to them.

Tier 3: Master Data Core business entities Table 18 Customer ; Table 23 Vendor ; Table 27 Item ; Table 14 Location ; Table 5600 Fixed Asset Master entities require Tier 1 codes and Tier 2 posting groups. They must be fully established before transactional opening journals can be created.

Tier 4: Transactional Openings Opening balances and unposted journals Table 81 Gen. Journal Line ; Table 83 Item Journal Line ; Table 5621 FA Journal Line Journals reference Master Data (Customer No., Item No.) and Posting Groups. They represent the final stage of data migration.

Warning

Circular Dependency Pitfall: In some implementations, circular dependencies emerge (for example, a Customer record requires an assigned Salesperson/Purchaser code, while the Salesperson requires a User or G/L Account). In such scenarios, consultants import the primary entity with non-mandatory fields blank, import the secondary entity, and execute a second update package to populate the cross-referenced fields.

Loading diagram... RapidStart Services Data Migration Architecture and Pipeline