Web Connect Incoming Data Web

Svenska: Web Connect inkommande data webb

Web Connect Incoming Data Web is the central place where all incoming payloads regardless of whether they are pushed to Business Central or fetched from an external API enter the system. Each incoming message is parsed, evaluated, broken down into objects and transformed into Business Central records based on your integration setup.

This page gives you a high-level understanding of how incoming data flows through Web Connect before it becomes actionable business data.

---

Default headers in incoming data #

This is the default view of Web connect Incoming data:

Download Date time – shows which time and date specific data has been received

Web Object – shows which object (highest level) this data is connected to

Status – which step in the process is this data

External ID – often item-, order or shipment number from

Record ID – when an messages is fully handled you can see the document Web connect has created

Error – if there is an error this will be marked and error message will be shown

How Incoming Data Works #

This specifec the steps and how incoming data is re-structed, mapped and processed.

Processing via Job Queue #

All incoming messages are processed by Web Connect Job Queue Transactions, which you configure to run at the desired intervals. This fully automates your inbound data flow

---

Data arrives #

Incoming payloads can originate from any connected system: eCommerce, POS, WMS, ERP, PIM, custom apps, etc

Incoming Type	Result Document in Business Central	Notes / Variations
Order	Sales Order or Transfer Order
Return Order	Return Order → Return Shipment → Sales Credit Memo	Full return flow is automated
POS Sale	Sales Invoice
Outbound Shipment	Sales Shipment → Sales Invoice or Transfer Shipment	Depends on whether shipment relates to Sales Order or Transfer Order
Inbound Shipment	Purchase Receipts or Transfer Receipt	Depends on whether shipment relates to Purchase Order or Transfer Order
Stock Adjustment	Inventory Journal Line	Supports positive/negative adjustments
Item	Item record created (with attributes, dimensions, metadata)	Supports size/variant models based on mapping
Voucher / Gift Card Use	Applied to Sales Line or Header	Created via mapping rules

*Automatic posting is always supported in Web Connect, function is fully configurable by customer.

If you use Web Connect WMS, incoming documents will trigger Web Connect WMS Documents to create logistics flows. Read more in Web Connect WMS LÄNK

---

The Object Tree — How Web Connect Breaks Down the Payload #

Once data enters Web Connect the payload is automatically split into an object hierarchy.
This ensures that every logical part of the message can be mapped and validated independently.

Example (simplified incoming JSON) #

{
  "invoiceAddress": { ... },
  "deliveryAddress": { ... },
  "products": [
      { "qty": 2, "unitPrice": 14.11 },
      { "qty": 1, "unitPrice": 12.11 }
  ],
  "payment": {
      "auth": { ... },
      "capture": { ... }
  }
}

How Web Connect structures this internally #

ORDER
 ├─ INVOICE_ADDRESS
 ├─ DELIVERY_ADDRESS
 ├─ LINES
 │    ├─ LINE 1
 │    └─ LINE 2
 ├─ CA_PAYMENT
 │    ├─ AUTH
 │    └─ CAPTURE
 └─ CA_VOUCHERS
      ├─ VOUCHER 1
      └─ VOUCHER 2

Each object can be opened, validated and mapped individually.

If you want to inspect a specific section of the payload, select the object and click Show Source.

---

Mapping Incoming Data to Business Central #

Each object in the tree can be mapped to Business Central fields using:

Web Connect Incoming Data Mapping #

This is where you define:

• Which JSON field maps to which BC field
• Priority order
• Whether values should be set directly on the record
• Validation order
• Conditional logic
• Text transformations

Separate documentation: Web Connect Incoming Data Mapping

Conditional Logic – Web Connect Condition List #

Used when different incoming values should trigger different mappings.
Examples:

Incoming value	Condition	Mapped to BC
"Retail"	Store type = Retail	Customer No = WEB
"store"	Contains store name	Sell-to Customer No = Account ID

Separate documentation: Web Connect Condition List LÄNK

Text Transformations – Web Connect Text Mapping #

Used to convert external values into internal codes.

Examples:

Incoming	Output in BC
"1"	"MAIN WAREHOUSE"
"SE"	"Sweden"

Separate documentation: Web Connect Text Mapping LÄNK

---

Processing Statuses #

Every incoming document moves through the following statuses:

1. New – received but not yet evaluated
2. Not Validated – object tree created, pending validation
3. Validated – validated, ready for processing
4. OK – successfully created or updated a document in BC

Error handling #

If validation fails:

• Status remains Validated
• The row turns red
• Error flag is set
• Error Message explains what went wrong

Web Connect retries processing 4 times by default.

To correct a specific message:

1. Select the row → Edit Data

2. Adjust incoming data/
3. Go back → Actions → Unmark Errors

4. Run Process Marked or wait for the scheduled job

To fix the issue for all future messages, update the Incoming Data Mapping instead.

---

Inspecting Payloads #

You can inspect the incoming message:

• Via Show Source on the header

• Via Show Source on any node in the object tree (shows only that segment)

• Via the FactBox (right panel) it will always displays the full payload

Filtering:

---

• Use Not OK filter to quickly find failed messages

Next Steps #

To configure or troubleshoot incoming data, continue to the following documents:
📄 Web Connect Condition List – LÄNK/RELATED DOCUMENT
📄 Web Connect Text Mapping – LÄNK