Page History

The backward mapping, from the response of the webservice to the ‘Voertuig’ entity, is a little more complex, because values have to mapped from several entities in the response, starting from the ‘AudascanV4’ entity. For this, we have to define ‘Additional context’:

Alert: in the additional context you have to use an expression which returns a single, unique instance. In the 'value/relation mappings' you can reason from this instance.

A common mistake is to define multiple instance mappings , using the ‘Or’, instead of ‘Additional contexts’:

In that case, for each instance mapping, a new instance for the target entity will be created!

From here we can start to map all the data:

As shown above, in the value mapping you can use data-conversion to convert the data into the appropriate format:

Besides that, it is also possible to combine attribute values (e.g. to concatenate strings, do calculations) from the source entities.

The image also shows that you can use conditions to set the values, for example to map a valuelist: