---
title: Language module
slug: hyper-portal/language-module
docTags: 
createdAt: 2021-12-15T10:34:39.000Z
---

Thi module will import languages from XDMS to HyperPortal

### Mappings

The NMlang field in XDMS contains the name of the language&#x20;

::Image[]{src="https://api.archbee.com/api/optimize/5goaGPkGyPYxtK7K75CEC/Qo3l9ON9h0o5GNyZjmibE_image.png" size="62" width="354" height="358" position="center" showCaption="false"}

It can be mapped to the 'title' property of the language entity in HyperPortal, or any other property where it\`s needed

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



It\`s important to map the 'CDlang' value from XMDS, because XDMS requires this value to determine the language during pushes to XMDS.

::Image[]{src="https://api.archbee.com/api/optimize/5goaGPkGyPYxtK7K75CEC/oK4wagyEw_Z6HldSIRVC2_image.png" size="70" width="356" height="363" position="center" showCaption="false"}

It is recommended to store this code in the 'xdmsExteralRef' property of the language entity. There is also an issue with storing the first item in the language list, as you can see on the screenshot the count starts from blank space. The value should be stored as '0' in Hyper Portal, so we use this expression - REGEXREPLACE(CDlang, '^$', '0'). The expression replaces '^$' (blank space) with '0' if the value that comes from XDMS is blank.

Example of the mappings -> [https://vankasteren.hyperportal.org/settings/integrations/xdmsIntegration/xdmsLanguageModule](https://vankasteren.hyperportal.org/settings/integrations/xdmsIntegration/xdmsLanguageModule)



&#x20;

