Mappings

Mappings within KeyNamics are used to provide 'startup' data to your Keyfax diagnostic scripts and to retrieve information from the Keyfax 'export' data in order to populate entity form fields on completion of the script.

Mappings can...

• Be defined at Global or overridden at Entity level (Entities represent different forms/case types e.g. Sales Order, Enquiry, Repair, Complaint)

• Use ‘FetchXml’ queries for deep extraction of hierarchical/other data within Dynamics

• be grouped by Entity, Send/Receive or any other element for ease of access

• Support Date, Boolean, Option Set, Option Pairs, Lookup data types

• supply default values

TIP If you create Mappings which send data to Keyfax, to use this data within your scripts you will need to define Import XML databoxes using Keyfax Administrator Tools.

Here is an sample set of Global mappings. These mappings apply across all entities unless overridden by entity-level mappings with the same Target:

Similarly, a sample set of entity-level mappings. The first few mappings can be seen as 'SEND to Keyfax'; these are used to provide startup data for Keyfax:

There are some Minimum Mapping Requirements that are required by Keyfax and these will normally be created at the global level. These define the basic settings required to launch Keyfax. Note: There is no limit to the amount of data you can send to Keyfax for consumption by your scripts. The amount of data available for mapping into Form fields is only limited by the data that is generated by your Keyfax scripts. To expand upon this, it may require additional scripting techniques such as the inclusion of Notes which can easily export any script data that you wish to use in Dynamics. For further information, contact Support.

See Also

• Creating Mappings

• Minimum Mapping Requirements

• Mapping Entity Form Fields

• Mapping Examples