Doc Summary 
Swedish: Web Connect Text-mappning
Overview #
Web Connect Text Mapping is used to transform values between external systems and Business Central.
It acts as a translation layer that ensures all connected platforms (eCommerce, POS, WMS, ERP, marketplaces etc.) use a clean and standardized value model inside Microsoft Business Central and vice versa.
You use Text Mapping when:
- The incoming value does not match the Business Central value
- External systems send different variants of the same meaning
- Business Central values need to be transformed before sending data out
- Values require normalization, translation or standardization
- You want a no-code way to handle differences between systems
Text Mapping is used in:
- Web Connect Outgoing Data LÄNK
- Outgoing data mapping LÄNK
- Web connect Incoming data
How Text Mapping Works (Incoming vs Outgoing) #
Text Mapping behaves differently depending on the direction of the integration.
This is crucial because incoming value does not always mean “from the external system”.
Incoming Text Mapping #
Used when data is moving into Business Central.
| Definition | Meaning |
|---|---|
| Incoming Value | Value from the external system (message) |
| Mapped Value | Value that should be stored in Business Central |
Examples:
| Incoming Value | Mapped BC Value | Purpose |
|---|---|---|
"1" | "MAIN" | Warehouse standardization |
"adyen_checkout" | "Adyen" | Payment method cleanup |
"DHL_TRANSPORT" | "DHL HOME" | Shipping method mapping |
"wholesale" | "B2B" | Sales channel classification |
Outgoing Text Mapping #
(Web Connect Outgoing Data LÄNK)
Used when data is moving from Business Central out to an external system.
| Definition | Meaning |
|---|---|
| Incoming Value | The BC value before transformation |
| Outgoing Value | What the external system expects |
Examples:
| BC Value (Incoming) | Outgoing Value | Purpose |
|---|---|---|
"Adyen" | "adyen_checkout" | Payment code format expected by Centra / Shopify |
"MAIN" | "1" | WMS warehouse identifier |
| | Carrier codes for shipping APIs |
"B2B" | "wholesale" | Marketplace sales type |
Direction Summary #
| Context | Incoming Value | Outgoing Value |
|---|---|---|
| Incoming Data | External → BC | Standardized BC value |
| Outgoing Data | BC → External | Expected external format |
This dual-direction logic is key for integrations that both read and write data.
Why Text Mapping Is Needed #
External platforms use inconsistent naming conventions:
- Shopify:
"adyen_checkout" - Centra:
"adyen_api" - Stripe:
"adyen_payment" - Marketplaces:
"ad_paid" - BC prefers:
"Adyen"
Text Mapping ensures one clean internal standard, regardless of:
- Language
- Format
- Upper/lower case
- Numeric vs alphanumeric codes
- Marketplace-specific variations
- WMS requirements
Common Use Cases (Retail & eCommerce Focused) #
Warehouse Codes #
Many systems use numeric IDs:
| From Source | BC Value |
|---|---|
"1" | "MAIN" |
"2" | "SECONDARY" |
"EU" | "EU-WHS" |
Payment Methods #
| Source | Mapped BC |
|---|---|
"cc" | "CREDITCARD" |
"card_payment" | "CREDITCARD" |
"klarna_pay_later" | "KLARNA" |
"invoice" | "INVOICE" |
Shipping Methods #
| Incoming | BC Value |
|---|---|
"FDX" | "FEDEX" |
"UPS" | "UPS" |
"1-3 days" | "STANDARD" |
"EXP" | "EXPRESS" |
Order Types #
| Source Value | BC Value |
|---|---|
"wholesale" | "B2B" |
"web" | "B2C" |
"marketplace" | "MARKETPLACE" |
How Text Mapping Works Internally #
Each entry contains:
| Field | Description |
|---|---|
| Source Value | Value received (incoming) or BC value (outgoing) |
| Mapped Value | Standardized BC value OR external-required value |
| Format | Text, Number, Code |
| Case Sensitivity | Whether matching is strict |
| Description | Documentation for maintainability |
You can create unlimited mapping rows for any field.
Example – Full Value Transformation #
Incoming JSON:
{
"paymentMethod": "card_payment",
"warehouse": "1",
"shippingCarrier": "FDX"
}
After Text Mapping:
| Incoming | Output | Used For |
|---|---|---|
"card_payment" | "CREDITCARD" | Payment Method Code |
"1" | "MAIN" | Location Code |
"FDX" | "FEDEX" | Shipping Agent Code |
When Not To Use Text Mapping #
Use Condition List when:
- Logic depends on ranges or thresholds
- Mapping should only happen if something is true
- Document behavior changes based on conditions
Use Incoming Data Mapping when:
- You are setting numeric fields
- You need to map JSON fields directly
- You modify multiple fields based on the same value
Use Objects when:
- You modify structures — not values
Best Practices #
- Keep Values clean
Choose a company language and keep them in all systems - Create mappings for both directions when using Outgoing Data
BC → External is often forgotten - Use Text Mapping before evaluating Condition List
Consistent values reduce condition complexity - Document your mappings
Simple comments save hours later
Related Documentation #
- Web Connect Incoming Data Mapping LÄNK/Related docs
- Web Connect Condition List LÄNK/Related docs
- Web Connect Incoming Data Web LÄNK/Related docs
- Web Connect Outgoing Data LÄNK/Related docs
- Web Connect Objects LÄNK/Related docs