---
title: Vehicle module
slug: hyper-portal/vehicle-module
docTags: 
createdAt: 2021-02-22T09:29:34.000Z
---

The customer module can be used to export vehicles from HyperPortal to XDMS. Vehicle import can be configured in the XDMS tab in the [settings](https://app.archbee.io/docs/ffeACTZ47_Cw3ctxvLLBM/_qF1OW_4T6OP_qLlJh0WP).

### Mappings

The expression for any date field should look like this - TEXT(TZ(lastMaintenance, "Europe/Brussels"),"YYYY-DD-MM") where 'lastMaintenance' is a date property.

![](https://api.archbee.com/api/optimize/5goaGPkGyPYxtK7K75CEC/kDIAztRs_xVWuCxbSUmbw_image.png)

The location field (NRwn) should receive a code of the site, to see the list of available site codes you need to open any vehicle and click the icon near the 'site' field.

![](https://api.archbee.com/api/optimize/5goaGPkGyPYxtK7K75CEC/zXz5DR2jNJKTj3gSNAeyg_image.png)

Those site codes are stored in the 'xdmsExternalRef' property of the location entity.

![](https://api.archbee.com/api/optimize/5goaGPkGyPYxtK7K75CEC/Hbt80K71iE9pksr93CrDK_image.png)

The mapping for location, in this case, will look like this - NRwh = location.xdmsExternalRef

![](https://api.archbee.com/api/optimize/5goaGPkGyPYxtK7K75CEC/UJGXxs8zZVBU4Pc3L_8wX_image.png)

NRcust, NRcust2, and NRcust3 (customer) fields should receive the ID of the XDMS customer (Cust.no) 

![](https://api.archbee.com/api/optimize/5goaGPkGyPYxtK7K75CEC/K2YoRrcHtNzjp-fR4OL8X_image.png)

This ID should be stored in the xdmsExternalRef property in the 'Organization' entity on the HyperPortal\`s side. So the mapping will look like that -

Nrcust = organization.xdmsExternalRef

![](https://api.archbee.com/api/optimize/5goaGPkGyPYxtK7K75CEC/wcTQ2u8eP8zXXT-BSONC2_image.png)

Fields like engine(NMother-colr), make(NMbrnd), model(NMmodel), fuel(CDfuel), model year(YYconst), transmission(CDgearbox), and country(CDcnty) are referred by the code property. The code property holds the value that can be accepted by XDMS. To know what values should be pushed to XDMS you just need to find the field that you are mapping and look up existing items. Example - we can see that manufacturers are displayed by their name in XDMS 

![](https://api.archbee.com/api/optimize/5goaGPkGyPYxtK7K75CEC/fSzf0uKIA-457DnbkDsfb_image.png)

This means that we need to push manufacturers\` names to XMDS. Those names are stored in the code property of the 'Make' property. 

![](https://api.archbee.com/api/optimize/5goaGPkGyPYxtK7K75CEC/2o4r_c-YxfrB9BeNgSMb8_image.png)

The mapping will look like this - NMbrnd = make.code

![](https://api.archbee.com/api/optimize/5goaGPkGyPYxtK7K75CEC/6QG8xaipcKDfDyPJfhBy8_image.png)

Color and interior behave the same as the 'make' field and others, but the value is stored in the 'shortCode' property by default 

![](https://api.archbee.com/api/optimize/5goaGPkGyPYxtK7K75CEC/SNESA90Sqb51Fi5oXJlYD_image.png)

![](https://api.archbee.com/api/optimize/5goaGPkGyPYxtK7K75CEC/NAavb1QqsVMhxdjcWde-8_image.png)



The mapping will look like this - CDcolr = color.shortCode



![](https://api.archbee.com/api/optimize/5goaGPkGyPYxtK7K75CEC/_fa3vg_CcyePec0mCpVSq_image.png)

Here is an example of mappings - [https://vankasteren.hyperportal.org/settings/integrations/xdmsIntegration/xdmsVehicleModule](https://vankasteren.hyperportal.org/settings/integrations/xdmsIntegration/xdmsVehicleModule)