F&O Entity Mapping Guide

Objective

The development of the entity-mapping framework was enhanced in RU38 for the Virtual Entities coming from Finance and Operations (F&O).

This framework is giving the possibility to map attributes between two different Dataverse entities with different attribute conversion methods, limiters and much more.

This mapping mechanism aims to minimize as much as possible the effort required by a developer or a D365 customizer to define a mapping relationship between two Dataverse Tables, especially between Hubdrive (xrm1) and Finance and Operations Virtual Tables (mserp). The framework supports both unidirectional and bidirectional data integration between Dataverse Tables.

We highly recommend the Entity Mapping be done by IT personnel.

Prerequisites

  • You are System Admin or System Customizer
  • HR for Dynamics is installed
  • The addon D365 F&O Human Resources Integration is installed (you can find the Download in our Customer Portal)

Click Through

  • Open PowerApps
  • Make sure the correct environment is selected in the top bar
  • Create a new solution with + New Solution
  • Add a display name
  • Add a name
  • Select a publisher (select the one you use for customizations)
  • Click on Create
  • Select the newly created solution and open it
  • Click on Add existing (top ribbon)
  • Select Table from the dropdown
  • Select the desired table
  • Click on Next
  • Click on Add
  • In the left side menu, select the table that was added
  • Click on Columns in the table view
  • Add a new column + New Column
  • e.g. we want to map it to the mserp_education field with Worker (mserp) Virtual Table: Screenshot
  • Now open your Dynamics environment
  • Open the advanced find tool
  • Look for Hubdrive Integration Mappings
  • Click on Results
  • Select and open the Integration Mapping for the entity you want to customize e.g. xrm1_employee
  • Set the "Record Maintained by" to Self-Maintained
  • Now you can edit the XML Mapping content on the right side of the Form
  • Update the XML for the newly created field to be mapped.

Hint

For custom fields, the Data Type has to be specified in the AttributeMapping tag inside the XML. The Property Name is "DataType", and the Possible Values are:

Field Type (Dataverse) DataType (XML)
Text String
Whole Number Int
Decimal Decimal
Lookup CustomLookup
Choice OptionSetValue
Yes/No Bool
Date and Time DateTime
Float Double
Currency BOMoney

Result

Image
HR