Multi Entity Management

Release note - March 2026

Multi Entity Management for Business Central Cloud

• Released version: 8.3.4.0

Changes in this release

[Feature] Developer Events for Overruling Field Data in External Transactions

New events have been introduced that allow developers and partners to intercept and override field data during external replication transactions. This provides a powerful extension point for customizing how data is written to subscriber companies.

What has been done:

• Added new events that fire during external transaction processing, enabling custom code to override field values before they are applied to the target record
• The events expose the field data and context of the transaction, giving developers full control over what data is written
• This follows the standard Business Central event pattern, making it easy to subscribe to from any extension

Usability notes:

• Partners and developers can now implement custom business logic to transform or override field values during replication — without modifying the core extension
• This is particularly useful in scenarios where subscriber companies require different field values than the publisher, such as different account mappings or localized data
• No impact on existing setups — the events are optional and only active when subscribed to

[Change] Manual Record Update Now Respects Field Setup

When manually updating records using the Manual Transfer functionality, the system now correctly applies the field-level setup defined in the replication configuration. Previously, field setup rules could be bypassed during manual updates.

What has been done:

• Updated the manual update logic to evaluate and respect the field setup (e.g., which fields are included or excluded from replication) when processing manual record transfers
• The behavior of manual updates is now consistent with automatic replication, ensuring field setup rules are always honored

Usability notes:

• Users performing manual record updates can now trust that the same field rules that apply to automatic replication also apply to manual transfers
• This prevents unintended data overwrites in subscriber companies when fields are explicitly excluded from replication in the field setup
• No changes to the user interface — the improvement is applied automatically in the background

Upgrade Considerations

• No breaking changes in this release — upgrading from 8.3.3.0 to 8.3.4.0 is straightforward
• Existing field setup configurations are fully respected after upgrade
• Developers wishing to use the new events should subscribe to them in a separate extension — no changes to existing code are required