Doc Summary 
⚠️ Important #
Changes to Web Connect in a production environment are sensitive and may cause integrations to stop working if configured incorrectly.
We strongly recommend testing all changes in a test/sandbox environment first.
If you are unsure, contact us before making changes.
Short answer #
Set Unique Identifier Action to No Action for the customer object in Web Connect Incoming Data.
This ensures that Web Connect does not update existing customer records when the identifier already exists in Microsoft Business Central.
When is this useful? #
This setup is commonly used when handling both B2C and B2B customers.
Typical example #
B2C (Web customers)
- Customers are mapped per market, for example:
WEB-SE(B2C Sweden)WEB-NO(B2C Norway)
- Web Connect should:
- Reuse the same customer
- Update invoice address and delivery address from the incoming order
B2B (Business customers)
- Customers are fully maintained in Business Central
- Incoming orders should not overwrite:
- Addresses
- Payment terms
- Other master data
- In this case, No Action should be used
How to configure it #
- Go to Web Connect Incoming Data
- Filter on the Web Object you want to change (for example: Customer)
- In the Object Tree, select the row where the identifier is defined and click edit incoming field mapping
- On the mapping line where Unique Identifier is enabled:
- Set Unique Identifier Action = No Action
This means:
- If the customer already exists → nothing is updated
- If the customer does not exist → normal creation rules apply
What does “No Action” mean? #
When Unique Identifier Action = No Action:
- Web Connect checks if the record exists
- If found → the record is left untouched
- No update, no overwrite, no validation error
Important notes #
- This setting only applies when the record already exists
- It is typically used for B2B customers
- B2C customers usually use Update/Create instead