The Active (background) integration method also detects changes in real time, but offloads the queueing work to a separate background session. This reduces the performance impact on user transactions.
How it works
- Like the Active method, database triggers intercept changes to monitored tables in real time.
- Instead of writing to an Integration Entry table, the system creates a lightweight Integration Task record and immediately schedules it for background execution using Business Central's Task Scheduler.
- The background task creates the corresponding Synchronization Queue entry and queues any related records, all outside the user's session.
- If the Task Scheduler is unavailable (e.g., during upgrade), the task falls back to running in the current session.
Characteristics
| Aspect | Detail |
| Change detection | Real-time (during the user's database transaction) |
| Performance impact | Low, only a lightweight task record is created in the user session; heavy processing runs in the background |
| Queue population | Near real-time, background tasks process within seconds |
| Monitoring options | Monitor Insertions, Modifications, Deletions, Renames (all configurable per entity) |
| Inventory triggers | Supported, with additional filter conditions (up to 4 field/value filters per entity) |
Setup
- Open the Commerce 365 Setup page.
- Set Integration Method to Active.
- Open the Table Setup page to review or configure monitored tables.
- For each entity, configure:
Active: Enable for entities that should be monitored.
Monitor Insertions / Modifications / Deletions / Renames: Enable the operations you want to track.
Queue Changes: Enable to include the entity in the polling cycle.
Job Queue Category Code (optional): Assign a category code to group entities for a specific job queue entry. This allows you to split synchronization across multiple job queue entries for better performance.
Priority: Controls the order in which entities are synchronized (lower = earlier).
Inventory Update Trigger: When enabled with field mappings and filters, inventory will be recalculated for any polled record that matches the filter criteria.
Differences from Active
- User transactions complete faster because queueing is done in the background.
- No intermediate Integration Entry table is used — tasks go directly to the queue.
- This is a Preview feature and may be subject to changes.