The data value mapping files list the enumeration mappings for fields that have enumerated values.
The P6DVM.xml file located in the data folder, which can be used as a reference, maps the P6 field enumerations to the Gateway field enumerations. The sampleprovider/data folder contains a SampleDVM.xml file that provides an example use of this file to map the Sample provider field enumerations to the corresponding Gateway field enumerations.
Schema file
Dvm.xsd
Contents
A ValueMaps element that contains zero to many ValueMap elements. Each ValueMap element can contain the following elements:
Element | Type | Parents | Description |
|---|---|---|---|
AppName | string | ValueMap | The element that indicates the name of the application for which this mapping applies. This name must match the name of an App that is defined in a *MetaData.xml file.. For example, specify P6 as the content of the AppName element to indicate that the mapping applies to P6. |
PDIObjectName | string | ValueMap | The element that indicates the name of the Gateway object for which this mapping applies. |
PDIFieldName | string | ValueMap | The element that indicates the name of the Gateway field for which this mapping applies. |
AppObjectName | string | ValueMap | The element that indicates the name of the object for which this mapping applies. The object that is specified in this element must reside in the application that is specified by the AppName. |
AppFieldName | string | ValueMap | The element that indicates the name of the field for which this mapping applies. The element that is specified in this element must reside in the application that is specified by the AppName. |
DirectCopy | boolean | ValueMap | The indicator that specifies whether to copy the field directly. Setting this element to true causes the system to copy the field without referring to the enumeration mappings. This element should only be set to true when the values are exactly the same in both side |
Item | ItemType. See the ItemType table below. | ValueMap | The element that maps each AppFieldName field enumeration to its corresponding Gateway enumeration. There can be zero to many item elements. |
ItemType Table
Element | Type | Parent | Description |
|---|---|---|---|
PDIValue | string | Item | The element that provides the enumerated value in Gateway. This element is required if the parent element is present. |
AppValue | string | Item | The element that provides the enumerated value in the application that is specified by the AppName. This element is required if the parent element is present. |
The following is an example of a ValueMap:
<ValueMap>
<AppName>Sample</AppName>
<PDIObjectName>Project</PDIObjectName>
<PDIFieldName>Status</PDIFieldName>
<AppObjectName>Project</AppObjectName>
<AppFieldName>Status</AppFieldName>
<Item>
<PDIValue>Planned</PDIValue>
<AppValue>SamplePlanned</AppValue>
</Item>
<Item>
<PDIValue>Active</PDIValue>
<AppValue>SampleActive</AppValue>
</Item>
<Item default="true">
<PDIValue>Inactive</PDIValue>
<AppValue>SampleInactive</AppValue>
</Item>
<Item>
<PDIValue>What-If</PDIValue>
<AppValue>SampleInactive</AppValue>
</Item>
<Item>
<PDIValue>Requested</PDIValue>
<AppValue>SampleInactive</AppValue>
</Item>
</ValueMap>
Default Attribute
The Item element can include an optional default attribute. In the example above, Inactive, What-If, and Requested are all mapped to SampleInactive. In this case, when going from Gateway to the Sample provider, there is no ambiguity since there is a many to one relationship between the mappings. However, when going from the Sample provider to Gateway, there is a one to many relationship between the mappings. In this case, the system resolves the ambiguity by mapping all of the Sample provider's SampleInactive enumerations for the Status field to the Gateway Inactive enumeration.