Cloud Replicator Documentation
Index

Table Mapping Overview

Table mappings define which Business Central tables are replicated to your cloud destinations. This guide explains the concepts and options available for configuring table mappings.

What is Table Mapping?

A table mapping tells Cloud Replicator:

  • Which Business Central table to replicate
  • Which cloud destination to send the data to
  • How to handle the data (company filters, series tables, etc.)
  • Whether the mapping is active or paused

Accessing Table Mappings

  1. Search for "Cloud Replicator Table Mapping" in Business Central
  2. The Table Mapping list page opens showing all configured mappings

Table Mapping Structure

Each table mapping consists of:

Component Description
Destination Target cloud service (Azure Table, Cosmos DB, AI Search)
Table No. Business Central table number
Index Sequence number (allows multiple mappings per table)
Active Whether replication is enabled
Configuration Company filter, Per Day, SystemId options, etc.

Primary Key

Table mappings are uniquely identified by:

  • Destination + Table No. + Index

This allows you to:

  • Replicate the same table to different destinations
  • Create multiple configurations for the same table/destination combination

Understanding the List Page

The Table Mapping list shows key information:

Column Description
Destination Target cloud service
Table No. Business Central table ID
Table Name Table caption (auto-populated)
Company Filter Which companies to include
Replicate Deletions Replicate deletions from the Change Log
Per Day Creates series tables with daily snapshots
Active Enabled for replication
Field Actions Count of configured field-level actions
Replications Count of historical replication records

The SystemId as RowKey, Add SystemId to All Related, and Additional Partition Key Field columns are hidden by default (show them via personalization). The Index is part of the mapping's key (see Table Mapping Structure above) but is not shown as a column.

Creating Table Mappings

Basic Steps

  1. Open the Table Mapping page
  2. Click "New" or press F3
  3. Select the Destination (or use default)
  4. Enter the Table No. or use lookup to select
  5. Configure additional options as needed
  6. Set Active to Yes when ready

Using Table Lookup

When entering Table No.:

  1. Click the lookup button or press F4
  2. The "All Objects" list appears
  3. Filter or search for your table
  4. Select and press Enter

Configuration Options

Active

Controls whether the table is included in replication runs:

  • Yes: Table is replicated during manual and scheduled runs
  • No: Table is skipped (useful for pausing replication)

Destination

Overrides the default destination for this table (dropdown captions):

  • Azure Table Storage
  • Azure Cosmos DB (TableDB API)
  • Azure Cosmos DB (NO SQL API)
  • Azure AI Search

Company Filter

Filters which companies are included:

  • Leave blank to replicate all companies
  • Enter company names to filter (supports multiple)
  • Uses standard Business Central filter syntax

Example filters:

  • CRONUS* - All companies starting with CRONUS
- `Company A Company B` - Specific companies only

Per Day (Series Tables)

When enabled:

  • Creates an additional "Series" table/container
  • Each day's data is preserved separately
  • Useful for time-series analysis and historical tracking
  • Not available for Azure AI Search

SystemId as RowKey

When enabled:

  • Uses the record's SystemId GUID as the unique key
  • More stable than primary key (survives key changes)
  • Required for Azure AI Search

When enabled:

  • Automatically includes SystemId for related record lookups
  • Works with Unfold and SystemId field actions
  • Useful for maintaining relationships in the destination

Replicate Deletions

When enabled:

  • Monitors Business Central Change Log for deletions
  • Replicates deletion records to the destination
  • Requires Change Log to be enabled for the table
  • Not available for Azure AI Search

Additional Partition Key Field

Adds an extra field to the partition key:

  • Enter the field number
  • Field value is appended to partition key
  • Useful for additional data partitioning

Multiple Mappings per Table

You can create multiple mappings for the same table using the Index field:

Use Cases

  1. Multi-Destination: Replicate to both Cosmos DB (for analytics) and AI Search (for search)
  2. Different Configurations: Different company filters for different purposes
  3. Series and Non-Series: One mapping for current state, another for historical

Example

Destination Table Index Purpose
Cosmos DB SQL Customer 0 Analytics database
Azure AI Search Customer 1 Customer search
Azure Table Customer 2 Archive (different company filter)

Field Actions

Click the Field Actions value to view configured field-level actions:

  • Shows count of fields with non-default actions
  • Drill down to configure field actions

Replication Log

Click the Replications value to view replication history:

  • Shows all replication runs for this table
  • Filter by success/failure status
  • View error messages for troubleshooting

Table Mapping Actions

The action bar provides several operations:

Manual Run Actions

Action Description
Manual Run (All) Replicate all active table mappings
Manual Run (Selected) Replicate only selected mappings (even if not active)

Management Actions

Action Description
Reset Last Replication Clear last sync date to force full resync
See Running Engines View active replication engines
Replication Log View history for selected table

Best Practices

Start Small

Begin with a few important tables, verify they work correctly, then add more.

Use Meaningful Indexes

When creating multiple mappings, use consistent index numbers (e.g., 0 for primary, 1 for search, 2 for archive).

Document Your Configuration

Keep notes on why each mapping exists, especially for complex setups.

Test Before Production

Create mappings in a sandbox environment first, verify data in destinations, then replicate configuration to production.

Monitor Replication Logs

Regularly check the replication log for errors or performance issues.