The mapping describes where each field in the destination will get its data. Use the Integration Mapping window to create a mapping. From this window, you can select rules, specify the source, or set rule properties—all of which define where the information for an item in the destination originates.
When you create the mapping, you will need to set up a rule for each required field in the root recordset of the destination. You also can set up mapping options. Required fields and mapping options for each adapter are described in Adapters and Destination Mappings.
Use the following procedure to map your source data to the destination.
The Integration Mapping window opens.
The upper left pane of the Integration Mapping window shows the destination in terms of recordsets. There are three types of recordsets in an Integration Manager destination: root recordsets, one-to-many child recordsets, and one-to-one child recordsets.
Root recordset The root recordset is the top level of the destination. For example, the root recordset of the Customer destination is called Customer and it contains the Customer ID and Customer Name fields (plus a number of additional fields). Each destination has only one root recordset.
One-to-many child recordset A one-to-many child recordset is represented by a folder icon and may contain more than one record for each record in its parent recordset. For example, in the Microsoft Dynamics GP Customer destination, the Addresses recordset is a child of the root recordset. Each customer can have many addresses. Therefore, the Addresses recordset has a one-to-many relationship with its parent.
One-to-one child recordset A one-to-one child recordset is represented by a cylinder icon. This recordset contains only one record for each record in its parent. For example, in the Microsoft Dynamics GP Customer destination, the Internet Addresses recordset is a child of the Addresses recordset. Although there can be many addresses for each customer, there can only be one Internet address for each address record. Therefore, the Internet Addresses recordset has a one-to-one relationship with its parent recordset (Addresses).
You need to select a rule for each of the required fields in the root recordset for the selected destination. Required fields are those fields in a destination recordset that need to be mapped for the integration to run successfully. Some of the child recordsets also contain required fields. You do not need to map the required fields for child recordsets if you do not map any of the other fields in that recordset.
For example, in the Customer destination, Customer ID is a required field for the root recordset (Customer). You need to select a mapping rule for the Customer ID field. In addition, if you select mapping rules for any of the fields in the Addresses recordset, you will need to select a mapping rule for the Address ID field, since it is a required field for the Addresses recordset.
The mapping tables in Adapters and Destination Mappings contain lists of required fields by recordset for each destination. You also can view a field’s attributes in the bottom pane of the Integration Mapping window to determine which fields are required.
A destination mapping is composed of rules. A rule defines where the information for an item in the destination originates. There is one rule for each field in the destination. To specify the type of rule to use for a field, choose the Rule column and select a value from the list.
As you click each row, information about that field is displayed at the bottom of the Integration Mapping window. This information includes the type of field (such as String, Numeric, and so on), the field length, and if the field is a required field.
|
You also can view the properties for a field in the Integration Mapping window. Right-click a field and choose Field Properties to view the properties, which helps you determine the data type, field size, and whether the field is required. |
Integration Manager has the following rules.
|
Rule |
Description |
|
The information for the field originates from one of the sources that is part of the integration. A Lookup button appears in the Source column, allowing you to open the Source Object window and select a field. |
|
|
You can type a value into the Source column. This value is used for every record created or updated when you run the integration. |
|
|
For date fields, the field in the destination is set to the system date. |
|
|
For debit fields, positive values are imported as they are. Negative values are imported as zero. |
|
|
For credit fields, negative values are imported as the corresponding positive value. Positive values are imported as zero. |
|
|
For newly inserted documents, the default value for that field is used, as determined by the business logic of the destination application. When updating existing records, the default value is typically the value that already exists for the field. |
|
|
For some string fields, the field in the destination is left blank when you run the integration. |
|
|
You’ll attach a Visual Basic script that runs to provide the value for the field. Refer to Using scripts. |
|
|
Solicits input from a user when the integration runs. When you use this rule, you can define the prompt in the Rule Properties section of the Integration Mapping window. If you do not define the prompt, the default prompt for a string field is, “Please enter a value for <name of field>.” If the field uses an enumerated data type, the default prompt is, “Select a value for <name of field>”, where you can select a value from a list. For fields that use dates, the prompt will include a Calendar view from which you can select a date. |
|
The Use Positive Source Field and Use Negative Source Field rules allow you to use the same source field for both the debit and credit value of a transaction. |
|
If you chose the Use Source Field rule, you must specify a source for the field. |
The item you selected appears in the Source column of the Integration Mapping window.
|
You also can drag items from the Source Object window to the Source column in the Integration Mapping window. The Rule column automatically is set to Use Source Field and the Source column displays the item you selected. |
Some rules have additional properties that you specify in the Rule Properties section of the Integration Mapping window.
The following table describes the rule properties.
|
Category |
Property |
Description |
|
Translation |
Allows you to convert an item from a source based on the values in the translation list. |
|
|
Source Field |
The column in a source from which data is read. |
|
|
Script Text |
Indicates whether VBScript code is associated with the field. |
|
|
If Null |
Indicates how Integration Manager handles a null (empty) value. A blank value can be used or the current record (document) can be canceled. |
|
|
Constant Value |
The value to use for the item if the Use Constant rule is selected for the field. |
|
|
Case Conversion |
Indicates whether characters in a string value are converted to uppercase or lowercase characters. |
|
|
Leading Spaces |
Indicates whether leading spaces are removed from a string value. |
|
|
Trailing Spaces |
Indicates whether trailing spaces are removed from a string value. |
|
|
String Truncation |
Indicates how Integration Manager handles string values whose lengths exceed the value allowed by the destination field. The string can be truncated at the maximum allowable length or the current record (document) can be canceled. |
|
|
|
Change Sign |
Indicates whether to change the sign associated with the value. If set to True, all positive values become negative and all negative values become positive. |
|
Shift Decimal Point |
Indicates how the decimal point is shifted for data read from the source. Positive values shift the decimal to the left. Negative values shift the decimal to the right. The value zero leaves the decimal position unchanged. |
|
|
Rounding |
If the value has too many digits to fit into the destination, it must be rounded or truncated. Set this property to Round or Truncate to round or truncate the value. Set the property to Round with Warning or Truncate with Warning to round or truncate the value and generate a warning for the integration. Click Cancel Document to cancel the record (document) if rounding or truncation is required. |
Some destinations have additional options that you specify on the Options tab. These options indicate how Integration Manager handles special circumstances when importing data into a specific destination. Additional mapping options are listed in Adapters and Destination Mappings.
When you select an option, the properties for that option appear in the Rule Properties section of the Integration Mapping window. Use these properties to specify individual options. For more information, refer to Adapter reference.
The default rule for one-to-many child recordsets is Use Default. The first time you map any field in a one-to-many recordset by setting its mapping rule to Use Source Field, Integration Manager automatically changes the Record Source option to Use Source Recordset, and sets the Source Recordset to the appropriate value.
The Record Source option (which is found on the Options tab of the Integration Mapping window) specifies which recordsets in the source will be associated with each recordset in the destination. There are different Record Source options for the different types of recordsets. See Adapters and Destination Mappings for more information.
|
The root recordset does not have a Record Source option. It is always associated with the root recordset of the source. For each record in the root recordset of the source, one record will be created in the destination’s root recordset. |
One-to-many child recordsets may have the following options.
|
Option |
Description |
|
Creates one recordset in the destination for each record in the associated source recordset. |
|
|
For newly inserted documents, the default values for the recordset are used, as determined by the business logic of the destination application. When updating existing documents, the default values typically consist of the records that already exist in that recordset. |
|
|
No records are integrated to this recordset. If the destination application contains business logic that typically would populate this recordset with default data, the default logic is superseded by the Empty Record Source option, and no records are created in this recordset for this destination. |
|
|
A default set of records is generated for this recordset, but some of them may be overwritten by records mapped to this recordset. For example, if you are integrating to Payables Transaction and you select the Default Non Imported rule for the Distributions recordset, a default set of distributions is created based on the business rules in the destination application. Typically this would be a debit to the vendor’s default Purchases account and a credit to the default Accounts Payable account. Mapping a Purchases distribution in this situation overwrites the default Purchases distribution, but leaves the default Accounts Payable distribution intact. |
Recordsets have options that allow you to control how items in the recordset are mapped. (Descriptions for the different recordsets are at the beginning of this procedure.)
One-to-one child recordsets may have the following options.
|
Option |
Description |
|
The mapping rules that appear on the Fields tab of the Integration Mapping window will be applied. |
|
|
This is the same as selecting Use Default as the mapping rule for all fields within that recordset. |