Multi Entity Management

Replication Template vs. Replication Schema

Version: September 2026 / Multi Entity Management 8.9.x / Business Central 28.x

1. Preamble

What is the difference between Replication Template and Replication Schema?

Multi Entity Management contains two different sets of tables that both handle replication setup. They belong to two different implementations of the same functionality:

• Replication Template (new functionality) – tables “XTEMEM Repl. Template Header” (5397803) and “XTEMEM Repl. Template Line” (5397804)
• Replication Schema (legacy functionality) – tables “XTEMEMReplication Schema Name” (5397824) and “XTEMEMRepl. Schema Alloc Table” (5397825)

The legacy tables are kept only for backward compatibility.

2. Where do I find each functionality?

Replication Template (new functionality) Role center “Master Data Manager” → Multi Entity Management → Replication Template

Replication Schema (legacy functionality) From the Replication Templates page → Actions → Replication Schemas

3. Important configuration rule

Both functionalities may exist side by side in the same Multi Entity Management setup, but the same replication code must never be configured in both places at the same time.

If the same code is maintained in both the new Replication Template functionality and the legacy Replication Schema functionality, the two configurations can interfere with each other. They may update subscribers independently, so the subscribers end up out of sync with either configuration.

This can explain unexpected behavior on subscribed tables.

4. Recommended handling

1. Identify the replication codes currently in use.
2. Use the new Replication Template functionality for new and migrated setups.
3. Check whether any code exists in both implementations.
4. Remove or deactivate the corresponding setup in the legacy tables for codes that are managed through the new functionality.
5. Avoid maintaining the same code in both places.
6. After correcting the configuration, review the affected subscribers and, if necessary, synchronize or reinitialize them using the normal Multi Entity Management procedure.

The legacy tables do not need to be removed from the database, since they may still be required for backward compatibility. However, each replication code must only be maintained in one of the two implementations at a time.