Web Connect Objects

Swedish Business Central view name: Web Connect objekt

Web Connect Objects define how incoming or outgoing data is structured when it moves between an external system and Business Central.
Think of them as building blocks that describe what the data contains and how it is organized.

What Web Connect Objects are used for #

Web Connect Objects make it possible to:

• Break incoming JSON/XML into understandable parts
• Build a structure that Business Central can process
• Handle repeated sections such as order lines
• Represent complex data through a clear object tree

Important
Objects define structure and not mapping.
Field-level mapping is done in Web connect Incoming Data or Web Connect Outgoing Data.

Incoming Data -Best Practice #

For incoming messages, the structure originates from the actual payload received from the external system. We recmomend configurating in Web connect Incoming Data.

Outgoing Data -Best Practice #

For outgoing messages, you typically build the structure starting from Web Connect Objects.

Best practice workflow: #

1. Create or adjust objects in Web Connect Objects
2. Go to Outgoing Data LÄNK

3. Use Test Message to preview the final outgoing payload

4. Add or adjust mappings based on the preview
5. Iterate until the outbound message matches the external system’s requirements

The Test Message button is extremely useful, it shows:

• How the object tree translates into JSON/XML
• Which fields are included
• How BC values are populated
• Whether nesting and arrays are correct

This makes it much easier to validate the integration structure before activating it.

Example: How incoming JSON becomes an object tree #

Here’s a simplified version of a typical JSON order payload:

{
  "invoiceAddress": { ... },
  "deliveryAddress": { ... },
  "products": [
      { "qty": 2, "ean": "ABCDEFGHIJKL", "itemText": { ... } },
      { "qty": 1, "sku": "SKUASKUBSKUC", "localizedProdSize": { ... } }
  ],
  "payment": { ... },
  "voucherCodes": ["MyFirstGiftcard", "New10PercentOff"]
}

This message contains multiple levels:

• Address objects
• A product array (multiple lines)
• Sub-objects inside each line
• A payment structure
• A list of voucher codes

How Web Connect breaks this into an object tree #

Web Connect reads the structure and generates a matching object tree.

Example:

CA_ORDER
 ├─ CA_BILLINGADDRESS
 ├─ CA_DELIVERYADDRESS
 ├─ CA_LINES
 │    └─ CA_ITEMTEXT
 ├─ CA_PAYMENT
 └─ CA_VOUCHERS

What each object represents: #

• CA_ORDER → Main order header
  • CA_BILLINGADDRESS → The invoice address section
  • CA_DELIVERYADDRESS → The delivery address section
  • CA_LINES → The repeating product array
    • CA_ITEMTEXT → Nested product details
• CA_PAYMENT → Payment information
• CA_VOUCHERS → Each voucher code

Web Connect then processes each object individually, which ensures:

• New lines are created for each array entry
• Nested data attaches correctly to its parent
• Header-level data and line-level data stay separate

Why the object tree matters #

Business Central cannot process raw JSON on its own.
The object tree defines:

• Which parts exist
• Which parts repeat
• How sections relate to each other

This lets Web Connect transform complex messages into structured BC entities.

What not to do in Web Connect Objects #

Avoid handling:

• Field mappings
• Lookup logic
• Transformations
• Business rules

Objects define structure only.
All logic belongs in Web connect Incoming Data and Outgoing Data LÄNK