2. Enhancement

Enhanced V3 Inbound Mapping to Support the Inbound Copy Node Function

We have enhanced Inbound Mapping V3 to support the Copy Node function.

Previously, Inbound Mapping V3 did not support copying nodes. With this enhancement, users can now copy nodes in the inbound mapping target structure, including copying multiple nodes with the same name. This functionality is useful when working with flat data that needs to be mapped into repeated child records. For example, one Account record may contain data for two Contact records, such as Contact 1 fields and Contact 2 fields in a flat table, flat JSON, or flat XML structure. In this case, users can copy the Contact node and map each set of Contact fields separately. This makes it easier to map one parent record to multiple child records in Inbound Mapping V3.

After this enhancement:

• The Copy Node function is supported in Inbound Mapping V3.
  
• Users can copy one or multiple nodes as needed.
  
• Users can create copied nodes with the same node name.
  
• This provides more flexibility when configuring inbound mappings with repeated or similar node structures.

Enhancement: Inbound Processing Supports CSV Payload Without Headers

In previous versions, inbound CSV processing required a header row. This has now been enhanced to support CSV payloads without headers. To use this feature, users must define a Message Type. The CSV column/header structure is determined from the related MsgTypeFieldEntry__c records, ordered by Sequence__c. For V4/integrate, pass csvHasNoHeader=true as a request parameter. For V3/integrate, include csvHasNoHeader: true in the request body.

Migrated Bulk Delete message processing to Salesforce Bulk API 2.0

In previous versions, bulk message deletion used the legacy Salesforce Bulk API behavior. This could cause failures when users delete many messages from Message Monitoring, especially during Delete All processing. The delete flow now uses Salesforce Bulk API 2.0 REST ingest processing. SKYVVA creates a JSON bulk job, uploads the delete records as CSV data, and closes the job with UploadComplete so Salesforce can process the deletion asynchronously. This improves compatibility with the current Salesforce Bulk API behavior and supports bulk delete processing through the newer REST-based Bulk API 2.0 flow.