Modules with Hard Coded fields

In order to facilitate specific functionality, we have made the assignment of certain Server Field Names to certain other Data Source Fields mandatory. Below is outlined which modules require specific mappings of fields to enable functionality.

Activities

The activities module can be set up in one of two ways. It can be displayed as a regular module or it can be a list of today/this week/this month's appointments with a filter for Type (this is referred to as the functionality Call List) 

In order to display activities this way, several steps must be taken.

1. To set the Call List, set the system key use.calllist.function to Yes. See Configuring System Keys for information regarding setting system keys.
2. Map the activity module to the server module named CRM_CALENDAR
3. Map the following fields using the following Server Field Names. Order does not matter.

Tasks

The Tasks module may be set up in a similar fashion to the Activities Module in that it may also be set up in one of two ways: It can be displayed as a regular module or it can be a list of today/this week/this month's appointments in a Calendar Display. 
To activate the Calendar Display:

1. Set the System Key 'use.tasklist.function' to Yes.
2. Map the activity module to the server module named CRM_TASKS.
3. Map at minimum the following fields using the listed Server Field Names. Order does not matter.

Attachments - CRM On-Demand Only

This functionality only works when using CRM On Demand as your Data Source. In order for Attachments to be mapped properly to the various modules you would like for them to be associated with, it must be mapped one time for each module you'd like it related to. For example, if you want Attachments with Accounts and Attachments with Opportunities, you must map the Attachments module twice. Furthermore, you must map it in a specific fashion:

1. Edit the Module Properties
   1. Select the Module Type to be ModuleTypeAttachment
   2. If you'd like it associated with the Accounts module, you would set the WebService Configurations to be: <?xml version="1.0" encoding="UTF-8"?><WsConfig><WsObjectName>Attachment</WsObjectName><WsConditionalParentObjectName>Account|AccountId</WsConditionalParentObjectName><SkipFields>AccountId</SkipFields></WsConfig>
2. Map the fields for the attachment.
   1. No fields are returned by the WS when you click on Fetch CRM Fields, so they all need to be added manually.
   2. Add ALL of the fields that are listed under the Data Source Field Name column in the table below. Please ensure the format and spelling is exactly the same.
   3. Once you have added all of the fields, you should now map all of the fields, as per the table below, making sure each data source field is mapped to the corresponding Server Field.
   4. Edit the field properties, and ensure all of the fields have the same configuration, as defined in the table below, making sure all of the readonly/hidden/required conditions are set, and the field types and length.
   5. Other fields may be mapped as necessary and desired. However, their Server Field Name does not have to be a specific one.