3. Bug Fixed

Not able to Export Large Records in the Data Loader

Fixed the issue of encountering the apex job error message 'First error: skyvvasolutions: Too many query rows: 50001' while exporting a large number of records using our Data Loader function. This issue has been resolved.

Fixed Generate SObjectType Node for XSD File

We have fixed the generation of message types to include the SObjectType, ensuring that the structure is generated with the SObjectType filling in the node name for XSD generate MetaData. Otherwise, it will use the message type name. For example, if your MessageType type is Salesforce sObject and the SObjectType is 'Account', it will use the 'Account' value to generate the node name. If they are not Salesforce sObject type, the message type name will be used for the node name of the XSD file.

Fixed various issues in Test Mapping Function

• There is an issue while executing the payload without an external ID in Test Mapping Function, and the result still shows success, but only the node without any fields. This issue has been resolved by adding the error alert message: 'After evaluating the data source 'FieldName', no data was passed for the mapped external ID field 'FieldName'.' for inbound processing.
• The issue of the payload not generating correctly with the SOAP and REST template payload has been fixed for inbound processing.
• Fixed getting a nonstop spinner on Query Editor of outbound processing while querying with the wrong field of the sObject. It was fixed by adding the error message “Error No such column ‘FieldName’ on entity ‘sObject’”
• Fixed test mapping to support XML and JSON file formats when the interface does not use the message type and set V3 to Interface API Version.
• Fixed the functionality of the Refresh button in the Test Mapping feature, ensuring that it works correctly with the outbound interface.
• Select the existing message to execute and observe the error message 'Error: Attempt to de-reference a null object.' This issue has been resolved.
• The issue of not removing the existing file after clicking the cancel button in the Import file functionality has been fixed.
• Due to the fact that Test Mapping does not support Outbound Interface API Version V2, we have removed the 'Test Connection' button and Payload box for the outbound Interface API Version V2.
• While selecting the completed message to be execute in order to get the payload, it will get the message alert error “Attempt to de-reference a null object”. This issue have been fixed.
• Fixed issue of page refreshing while executing the new record and retrieving the existing result payload.
• Fixed the issue where clicking the 'Test Connection' button did not redirect the screen to the Test Connection Page.

Fixed minor bug

• Fixed the filter on the Integration under the Interfaces filters section of the Integration page, which now only allows filtering for the current integration.
• The issue of saving the new interface and losing the tree of the interfaces list has been resolved.

• When creating the sub-interface on the query editor, it generates the wrong Parent Relationship Name / Foreign Field when working with a custom object.

Fixed Generate Payload for Cusotm Processing Class of Rest Adapter

We encountered a small bug in the custom processing class of the REST adapter while generating a request payload to be sent to the actual business server. However, this issue has been resolved.