ver 0.1 (0.4)

This release introduces enhancements and improvements focused on usability and functionality, particularly in data synchronization, field selection, and character limits. The enhancements in this version include the following:

Improved usability: Enables easier selection of the correct API fields with subheadings.
Expanded field lengths: Prevents truncation of Salesforce API field names.
Better synchronization: Enables broader data synchronization capabilities to support the Individual object.
Extended object mapping: Enable mapping for the Individual, Campaign Member, and Service Appointment objects.

What's New?

The following are the new features and improvements introduced in this version:

Support for new standard objects

Individual, Campaign Member, and Service Appointment are now available for synchronization. This provides broader data alignment and integration capabilities.

Enhanced field selection

To enable the selection of the appropriate field during configuration, the API names (the programmatic or system-specific names used for integration or development purposes) are now shown as subheadings in the Salesforce Field list:

Increased character limits

To support more extensive data inputs, the character limit for the API names in the Salesforce Field on the Mapping object and other fields on packaged objects has been increased.

info

Information

Some objects require special attention while mapping fields. Ensure that the following mandatory mappings are configured for smooth data synchronization:

Campaign member: Map the Lead ID (API Name: LeadId) or Contact ID (API Name: ContactId) to an event attribute. These fields are available in the Others section.
Service appointment: The Earliest Start Permitted (API Name: EarliestStartTime) and Due Date (API Name: DueDate) fields are mandatory and must be mapped to event attributes containing values in Unix epoch time.
- The Parent Record (API Name: ParentRecordId) is also mandatory and must be mapped under the Others section. The Parent Record is a polymorphic field. MoEngage can process record IDs for the Work Order, Work Order Line Item, Account, Opportunity, Asset, Lead, and Case objects.

By ensuring these mappings, you can efficiently synchronize the data between MoEngage and Salesforce while handling the scenarios above.