5. Bug Fixed

Fix Missing IData on IMessage for ContentVersion with Outbound Dropbox Adapter

Fixed an issue where outbound V3 processing created IMessage records without the related IData/ContentVersion payload when using the Dropbox Adapter. The root cause was that the ContentVersion data-creation path was only enabled for Agent and Google adapters. Dropbox belongs to the Salesforce-to-other adapter group, so it was skipped. The fix includes adapters from V3OutboundUtils.operationSfToOther in the data-creation check, allowing Dropbox messages to correctly create and link their IData/ContentVersion payload.

Fix Infinite Loading Spinner When Saving Dropbox Adapter Direction changes

Prevent Interface Update Failure Caused by Salesforce High-Assurance Session Requirements

Fixed an issue where updating an Interface could fail when SKYVVA attempted to clean up or abort old scheduler jobs, and Salesforce required extra session verification. In some customer orgs, Salesforce security settings such as Reports and Dashboards = Raise session to high assurance can trigger a “Requires Extra Verification” condition. SKYVVA now handles scheduler-abort failures safely, so the Interface save/update is not blocked if Salesforce requires high-assurance verification during scheduler cleanup.

Refresh mapping grid after saving Mapping Record Details

Fixed the Mapping Tool page so changes saved from the Open Record Details are applied back to the selected mapping grid row immediately. Previously, the mapping record was saved, but the grid could still show old values until the page was refreshed. The update now synchronizes the returned IMapping values with the grid row after save.

Fixed Multiple Issues in the Log File Screen

Fixed multiple issues in the Log File.

Fixed an issue where selected records were removed when users navigated to the previous or next page after selecting records across multiple pages. The selection state is now preserved during pagination, so users can move between pages without losing their selected records.
File selection is preserved when users move between pages in the same folder, and Select All / Clear Selection now apply across all pages instead of only the visible page.
Fixed an issue where the selected file count still showed the old value after users selected all files and deleted them. After the delete action is completed, the selected file count is now cleared correctly and returns to 0.

Fix Outbound XML and form-data Payload Generation When Don’t Export NULL Value is Enabled

Fixed an issue where outbound payloads could still include empty fields even when the interface option Don’t Export NULL value was enabled.

For XML payloads, the previous logic only skipped fields when the value was null. If a mapping or formula returned an empty value, such as an ISNULL formula result, the XML builder could still generate an empty XML node. The logic now checks both null and blank values, so empty XML nodes are not generated when null suppression is enabled.

For application/form-data and application/x-www-form-urlencoded payloads, empty fields were previously still written into the request body as null or empty values. The form-data builder now skips those fields when Don’t Export NULL value is enabled.

For CSV payloads, no field-removal change was applied because CSV must keep the same column structure for every row. If one record has a value and another record has no value, the empty value should remain as an empty cell so the next columns do not shift into the wrong position.

Fixed CSV Adapter Properties Rendering

Fixed an issue where selecting CSV as the adapter type did not display any adapter properties. SKYVVA now shows the CSV file type and separator properties correctly, including separator options for comma, semicolon, Tab, and pipe. This allows users to configure CSV adapter properties properly instead of seeing an empty property list.

Fixed External Key Custom Logic Validation

Fixed an issue in External Key “Customize the logic” mode where missing fields in a custom expression could bypass validation. For example, with logic like (AccountNumber OR BillingCountry) AND BillingCity, if the required field was missing, SKYVVA could fail to match the existing record and create a duplicate record.

SKYVVA now evaluates the custom AND/OR expression before processing. If required external key fields are missing, the message is marked as a process error, and no duplicate record is created. The error message was also improved to show the actual field names, making it easier for users to identify which fields are missing from the payload.

Optimize Skyvva Inbound V3/V4 API processing for Large Payloads

Fixed an issue in the SKYVVA Inbound V3/integrate and V4/integrate API processing where large payloads, such as posting ContentVersion records with PDF file data, could generate excessive debug log output and increase Salesforce heap/string usage.

In this case, messages could remain in New status, and the following error was logged: AbstractIntegrationV3.messageProcessing>startExecuteMapping:a0Z1i000008MkdLEAS>ERROR:String length exceeds maximum: 6000000, line:2485 (skyvvasolutions)

The fix removes unnecessary debug logging from AbstractIntegrationV3.cls, reducing log and heap overhead during large message processing while keeping the integration behavior unchanged.

Fix Pagination on Integration and Metadata Providers List Views

Previously, list view pagination did not always return the expected number of records on subsequent pages. For example, when the page size was set to 10, the first page displayed correctly, but navigating to the next page could show fewer records than expected even when additional records were available.

The pagination logic has been corrected to consistently display records according to the selected page size. The list views have also been optimized to display 20 records per page by default.

This improvement makes it easier to review large Integration and Metadata Provider record lists and ensures pagination behaves consistently across all pages.

Fixed Mapping Tool for Auto Mapping case-insensitive

Fixed an issue where Auto Mapping only matched source and Salesforce fields when the letter case was exactly the same. For example, fields like Name and name were not matched automatically. Auto Mapping now compares field names case-insensitively, so matching fields are mapped even when their uppercase/lowercase letters differ.

Use Processing Package Size for Inbound Batch Apex processing

Fixed inbound processing when the Interface is configured with Inbound Posting Behavior = Batch Apex. Previously, this flow always executed with a batch size of 1, even when users configured Processing Package Size (Number_of_Records_Per_Batch__c) on the Interface. This made the configured value ineffective and could create more batch executions than expected.

SKYVVA now uses the configured Processing Package Size to control how many records are processed in each Batch Apex transaction. If the field is empty, the system safely defaults to 1.