Walkthrough: Using code to define data mapping

Current version: 4.0

When using Data Exchange Framework, the standard approach for mapping data is to configure the mapping in the tenant. In many cases, this approach works well because it reduces the amount of custom code needed. Specific mappings can be added or removed as needed, without having to write any code.

However, there are cases where the mapping logic is too complex to be described through configuration. There are also cases where existing data mapping logic should be reused. In these cases, you need to be able to define data mapping using code.

This walkthrough describes how to build, deploy, and integrate the components needed to implement code-based data mapping.

Do you have some feedback for us?

If you have suggestions for improving this article,