Using the Field Mapping Detail View

Infor CRM Back Office Extension only. Use the Detail view to see information for a selected record.

The system administrator and users with the appropriate role can access these features.

To open the ION BOD Mapping Detail view, on the Navigation Bar, click ION Field Mappings to open the Field Mappings List view. If necessary, use the Lookup to locate a field mapping, and then click the field mapping Name.

Note: To customize the selected field mapping, click the Customize link. The Customize link is replaced with the Edit link which indicates that the selected field mapping is customized.

To switch to the List view, on the toolbar click list_view (List View), or click the Current Group tab.

Information Fields

The information boxes contain the primary information about the ION field mapping. Some information can be edited, however other information cannot be added after the field mapping is created or is for display only and must be added or edited in the integrated application. For specific questions please refer to the documentation for the integrated application or contact the administrator.


Field	Description	Can be edited?
Field Mapping	A descriptive BOD field mapping name that is unique relative to the parent BOD mapping. When adding a new ION field mapping, type a unique and descriptive name for the field mapping.	On insert only
BOD Mapping	The parent BOD mapping with which the field mapping is associated.	No
Entity	The Infor CRM SLX entity, or record type, being mapped. Note: If creating custom BOD Field Mappings, see the Any Bod chapter in the Infor CRM Back Office Extension Customization User Guide.	On insert only
Parent Entity	The Infor CRM SLX parent entity for the specified entity. This value can be null for top level entities. Note: If creating custom BOD Field Mappings, see the Any Bod chapter in the Infor CRM Back Office Extension Customization User Guide.	On insert only
Entity XPath	The BOD element XPath for this entity. In order to edit this field, refer to the Any BOD chapter in the Infor CRM Back Office Extension Installation Guide.	On insert only
Bod Element Sequence	The sequence number used by the outbound BOD template generation logic.	On insert only
Default Value	Specifies a default value if this field is required by Infor CRM SLX For inbound processing, the default value is loaded into the entity.property if the specified BOD element is not found in the BOD. For outbound processing, the default value is loaded into the outbound process BOD if the current content of the specified `entity.property` is null.	On insert only
Active	Use this option to turn on or turn off synchronization for this field mapping.	On insert only
Custom	Identifies whether or not a field mapping is custom. Custom field mappings may be modified. Standard BOD mappings are read only and have the custom flag cleared.	No
Required	Use this option to identify if the field is required by Infor CRM SLX.	On insert only
Property	The field name of the entity being mapped. Type the Infor CRM SLX property name being mapped. Note: If creating custom BOD Field Mappings, see the Any Bod chapter in the Infor CRM Back Office Extension Customization User Guide.	On insert only
Property XPath	Specify the BOD element where you can find the field mapping information from the Infor CRM BOD Mapping (Inbound) guide. The value specified must correspond with the related Xpath from the noun element in the BOD XML message. For example, specify /PartyIDs/ID. In order to edit this field, refer to the Any BOD chapter in the Infor CRM Back Office Extension Installation Guide.	On insert only
Sync Direction	Identifies how information is synchronized between Infor CRM SLX and the integrated product. Specify one of these options: Both: for inbound and outbound BODs In: for inbound BODs Out: for outbound BODs	On insert only
Include In Search	If the BOD Mapping has a System of Record as CRM use this option to indicate if the field mapping should be used as match criteria when processing Inbound process BODs to determine if matching records should be merged or if no match exists, then a new record is created. This option and the Search Clause option are used together to define the search criteria if multiple field mappings are to be used as match criteria.
Search Clause	If the BOD Mapping has a System of Record as CRM and the Include In Search option is selected for the current field mapping and at least one other field mapping, then use this option to indicate how a match is determined. AND - When more than one field mapping is to be used as match criteria and the record must match all criteria in order to merge records. If all match criteria is not met, then a new record is created. OR - When more than one field mapping is to be used as match criteria and the record must match any criteria in order to merge records. If none of the match criteria is met, then a new record is created.

To save the changes, click (Save).