Test & Smile Mapping
This page describes which OMD data elements are shared with Test & Smile.
Mapping Elements
| OMD data element | Test & Smile data element | Purpose |
|---|---|---|
| Account number | Customer reference in Test & Smile | Links the visit to the correct customer/account in the portal. |
| Task name | Visit name | Human-readable visit identification. |
| Street | Visit address street | Location context for the visit. |
| Postal code | Visit address postal code | Location context for the visit. |
| City | Visit address city | Location context for the visit. |
| Country | Visit address country | Location context for the visit. |
| Assigned resource external ID | Scheduled resource identifier | Identifies the resource/user for the visit. |
Data Dependency
The transfer depends on the following data being present and valid in OMD:
- A planned task in the active upload window.
- A customer/account reference for the task.
- A scheduled resource with a valid external ID.
- Address details (street, postal code, city, country) for meaningful location data.
If key dependency fields are missing, the task is not part of the outbound connector data set.
Idempotency
The connector can safely resend the same planned visits.
- Repeated upload runs send the current planning state again.
- Repeated push runs send the same pending updates until they are processed.
- This means retries are operationally safe from the OMD side and help recover from temporary transfer issues.