Doc Summary 
Swedish Business Central view name: Web Connect Destinationer
Overview #
Web Connect Destinations defines what data should be sent from Microsoft Business Central to external systems and how that data should be calculated.
This view is used primarily for:
- Outgoing inventory synchronization
- Outgoing price list synchronization
Destinations do not decide when data is sent.
That is handled by Web Connect Outgoing Sync Triggers.
Destinations decide:
- Which calculated values should be sent
- Which calculation logic should be applied
- Which external purpose the data is intended for (warehouse or price list)
How Web Connect Destinations fit into the outbound flow #
The outbound flow looks like this:
- Inventory or price logic is defined using Dynamic FlowFields
- A Web Connect Destination references those FlowFields
- Outgoing Sync Triggers decide when a change should be sent
- Data is added to Web Connect Outgoing Data Web
- Job Queue creates Web Connect Entries
- Data is sent to the external system
Destinations are therefore the bridge between calculated values and outgoing messages.
Destination types #
Each destination has a Destination Type that defines its purpose.
| Destination Type | Description |
|---|---|
| Warehouse | Used for sending inventory-related data (stock, availability, planning data). |
| PriceList | Used for sending price lists to external systems. |
Fields in Web Connect Destinations #
General #
| Field | Description |
|---|---|
| Code | Unique identifier for the destination. Used internally to reference what should be sent. |
| Destination Type | Defines whether the destination handles Warehouse or PriceList data. |
Inventory-related fields (Warehouse destinations) #
| Field | Description |
|---|---|
| Inventory Dynamic FlowField | The Dynamic FlowField used to calculate the inventory value that will be sent to the external system. |
| Calculate Next Available Date | Calculates the next date when inventory becomes available again, based on purchase orders, transfer orders (in/out), and sales orders. |
| Planning Location Filter | Location filter used when calculating planning data and/or next available date. Multiple locations are separated with ` |
Next Available Date – calculation logic #
The next available date is calculated by evaluating:
- Incoming quantities from Purchase Orders
- Incoming quantities from Transfer Orders (in)
- Outgoing quantities from Sales Orders
- Outgoing quantities from Transfer Orders (out)
If demand exceeds supply on the next receipt, the calculation continues to the next incoming supply date.
BOM and planning extensions #
| Field | Description |
|---|---|
| Calculate Availability From BOM | If enabled, availability is calculated using BOM availability logic instead of the standard Dynamic FlowField. Applies only to BOM items. |
| Add Inventory By Event | Adds Order Planning data as an underlying array from the Item Inventory table. |
| Order Planning Web Object | The Web Object used to expose planning data when Add Inventory By Event is enabled. Creates a fixed relation to planning data. |
⚠️ Planning data is temporary and is created only when the outgoing inventory message is generated.
Use child relations (e.g. Level = 0) to avoid sending full order lists if only summarized data is required.
Price-related fields (PriceList destinations) #
| Field | Description |
|---|---|
| Price Dynamic FlowField | The Dynamic FlowField used to calculate the price for the selected Price List code. |
This allows full control over:
- Which price logic is used
- How prices are calculated
- Which prices are exposed externally
Where calculated values can be reviewed #
The calculated results from Destinations are visible in:
- Web Connect Item Inventory – inventory and availability values – LÄNK RELATED
- Web Connect Item Price – calculated prices – LÄNK RELATED
These views are recommended for verification and troubleshooting before data is sent externally.