Doc Summary 
Web Connect Villkorslista
Overview #
The Web Connect Condition List is where you define logical rules that influence how incoming data is interpreted, mapped or transformed before Business Central creates or updates records.
Conditions allow Web Connect to behave dynamically for example:
- Change the Order Type based on the store name
- Select different customers, payment methods, or shipping agents
- Trigger different flows depending on values in the incoming message
- Evaluate data both before and after field mapping
- Combine multiple conditions using logical operators (AND, OR, NOT)
Conditions are referenced from Web Connect Incoming Data Mapping where each condition determines when a mapping rule should be executed.
When Conditions Are Used #
Conditions are required when:
- Incoming data varies by market, store, sales channel, platform or warehouse
- You need to route different data to different fields, documents or customers
- Business logic depends on ranges, thresholds, empty/not empty etc.
- Data must behave differently when mapping, creating or updating documents
Examples include:
- Retail vs wholesale logic
- Map shipping agent based on service code
- Identify POS vs eCommerce orders
- Create Return Orders only when total is negative
- Choose appropriate payment method
- Set dimensions based on incoming metadata
How Conditions Work #
A condition is evaluated for every incoming object.
If the condition returns TRUE the associated mapping rule will execute.
A condition can evaluate:
- Incoming message values (JPath)
- Fields being mapped inside Microsoft Business Central (after mapping)
- Dynamic FlowFields (Microsoft Business Central standard function)
- Integration Variables
- Expressions combining multiple conditions
Conditions are evaluated in sequence using logical operators (AND / OR / NOT).
Condition Structure #
Condition Header (General) #
| Field | Description |
|---|---|
| Code | Unique identifier used in mapping |
| Description | What the condition does |
| Web Object | Which object this condition applies to |
| Table No. | Which BC table the condition interacts with |
Condition Lines #
Each condition consists of one or more lines that define the logic.
| Field | Meaning |
|---|---|
| Operator | AND, OR, NOT, AND NOT, OR NOT |
| Set to TRUE | Manually force condition to true (for testing) |
| Calculated Condition | Shows result of the evaluated line |
| JPath Value | Value taken from incoming message |
| Field No. / Field Name | Optional: compare against a BC field value |
| Dynamic FlowField | Allow comparison against a calculated field |
| Cut Out / Max Length | Transform incoming values before comparison |
| Comparison Operator | =, <>, >, <, >= |
| Logic Value Format | Text, Number, Boolean, Date, DateTime |
| Logic Value | The expected value in the comparison |
Supported Operators #
| Operator | Description |
|---|---|
| AND | All conditions must be true |
| OR | At least one condition must be true |
| NOT | Inverts the condition result |
| AND NOT | True if previous lines are true AND this line is false |
| OR NOT | True if any previous line is true OR this line is false |
Comparison Operators #
| Comparison | Meaning |
|---|---|
| = | Equal |
| <> | Not equal |
| > | Greater than |
| < | Less than |
| >= | Greater or equal |
Logic Value Formats #
| Format | Example |
|---|---|
| Text | “WEB”, “UPS”, “store1” |
| Number | 1, 10.25 |
| Boolean | true / false |
| Date | 2025-12-05 |
| DateTime | 2025-12-05T12:30:00Z |
Practical Examples (Retail + Ecommerce Oriented) #
Example – Store-Based Routing (Wholesale vs Retail) #
Goal: If store.name = “wholesale”, set Order Type = Wholesale Order
Used when a client receives orders from multiple sales channels.
Condition Lines:
| JPath | Comparison | Value |
|---|---|---|
| store.name | = | wholesale |
Condition result = TRUE → Incoming Data Mapping sets Order Type.
Example – Payment Method Based on Currency #
Goal:
If the order currency is EUR, use the payment method coming from paymentMethod.uri.
| Source | Comparison | Value |
|---|---|---|
| Currency Code (table value) | = | EUR |
Condition result triggers mapping:
→ Map paymentMethod.uri → Payment Method Code
Example – Create a Sales Invoice Only When Total ≥ 0 #
Useful for POS or marketplace orders.
| JPath | Comparison | Value | Format |
|---|---|---|---|
| moneytotal_gross_all | >= | 0 | Number |
If TRUE → Create Sales Invoice
If FALSE → Could trigger Return Order logic
Example – Shipping Agent Selection (FDX vs UPS) #
Based on incoming shipping code.
| JPath | Comparison | Value |
|---|---|---|
| shippingAddress.country.code | = | FDX |
| OR shippingAddress.country.code | = | UPS |
Condition triggers different mapping rules:
- FDX → Shipping Agent = FedEx
- UPS → Shipping Agent = UPS
Example – Split Logic Based on Document Totals #
Used to differentiate return flows from positive sales.
| JPath | Comparison | Value | Meaning |
|---|---|---|---|
| total.amount | < | 0 | Negative → Return Flow |
Example – Dimension Assignment Based on Market #
| JPath | Comparison | Value |
|---|---|---|
| store.country | = | DK |
Condition triggers:
→ Set Dimension “MARKET” = “DENMARK”
Best Practices #
- Keep condition logic simple
Use multiple condition lines rather than complex expressions. - Always preview values using “Show Source”
This ensures your JPath references are correct. - Combine with Text Mapping
Often required for cleaning incoming values before comparisons. - Use Table Field values when conditions depend on mapped BC data
Example: Currency Code, Document Type, Location Code. - Name conditions by business purpose
ExampleWEB_ORDER_TYPEPOS_PAYMENT_RULERETURN_FLOW_TRIGGER
Related Documentation #
These docs should be linked:
- Web Connect Incoming Data Mapping LÄNK/RELATED DOCS
- Web Connect Incoming Data LÄNK/RELATED DOCS
- Web Connect Text Mapping LÄNK/RELATED DOCS
- Web Connect Objects LÄNK/RELATED DOCS