Fixed Issue Cannot read properties of Undefined While Importing BAPI to Create Message Type #
There is an issue that occurred while you connected to import BAPI to create the message type. Then get a message alert “TypeError: Cannot read properties of undefined (reading ‘Name’)” because it will not able to read type as ‘undefined’. This issue has been fixed.
Not Able to Save TransportRoute Record #
When you have a long password, you will not be able to save or create TransportRoute records, and an issue will be raised with the error message: ‘Error: Upsert failed. First exception on row 0; first error: CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY, skyvvasolutions.trgTransportRoute: data changed by trigger for field Password: data value too large: (value has been hidden): []’. This issue occurs due to the small size of the password field length. However, this issue has been resolved by increasing the length.
Fixed Apex Heap Size Error on Bulk Control Board #
There is an issue when dealing with a large number of records in multiple baskets (New Baskets and Current Processing Baskets) and history baskets (Processed Baskets) on the Bulk Control Board. This issue leads to an ‘Apex heap size’ error due to the query and processing of History basket records. The serializedString converting the History Baskets exceeds the apex limit. However, we have successfully resolved this issue by implementing a solution that involves splitting the query when loading Bulk Basket records and Basket History for each section.
Not Able to Open Message Monitoring #
There is an issue that arises when attempting to open the Message Page for Monitoring. Upon opening the page, it automatically reloads, and an error message is displayed: ‘Uncaught Error in SA.getCallback0 [Cannot read properties of undefined (reading ‘reportid’)]. Callback failed: apex:/skyvvasolutions.IMessageController/ACTIONSgetMessageReport’. This issue occurs because the browser does not support the lower version of jQuery that is being utilized. However, I am pleased to inform you that this issue has been resolved by upgrading the jQuery library.
Note: It’s important to note that other screens may also encounter issues due to the outdated version of jQuery.
To avoid the error without upgrading the version to resolve the issue, you can disable the ‘Use Lightning Web Security for Lightning web components and Aura components’ option. Please follow the instructions below:
=> Setup => Session Settings under Security => unchecked “Use Lightning Web Security for Lightning web components and Aura components” option => Click Save Button
Before you disable or enable this option, please refer to the Lightning Web Security document: https://developer.salesforce.com/docs/platform/lightning-components-security/guide/lws-intro.html
Fixed Cannot Save Auto-Mapping Records #
The issue occurred when the source tree had an attribute field and auto-mapping without expanding the node. Consequently, when attempting to save the mapping, an error message was displayed: ‘validate AndSaveMappings> ERROR: TypeError: Failed to execute ‘appendChild’ on ‘Node’: parameter 1 is not of type ‘Node’.’ To resolve this issue, we have implemented a solution that automatically expands the node when the user selects it.
CDT with sObject V3 hierarchy Mapping #
When processing CDT outbound with sObject V3 hierarchy Mapping and the SAP CPI adapter, and subsequently sending the CP records as a response asynchronously, you may encounter a pending message and experience an issue in the log: ‘skyvvasolutions.ISAPCalloutService.ISAPCalloutException: The executed method does not support the SAP CPI adapter type.’ However, I am pleased to inform you that this issue has been resolved by supporting V3 without message type.
Missing GETCORRELATIONID field value in the Payload #
When you post an inbound message request and execute the outbound response interface in Asynchronous mode, the outbound message will copy the ‘system_external_id__c’ and return the value to the request payload using the mapping formula ‘GETCORRELATIONID(system_external_id__c)’ on the outbound interface. There was an issue where the payload was missing this mapped formula value field. However, I am pleased to inform you that this issue has been fixed.
Resolved Issue: Field Inside Selected Field Not Found #
When performing the outbound interface and completing the mapping, the query will be automatically generated. The query field statement will include the ‘Selected Field’ when using a formula during mapping. However, there was an issue where this field was missing on the source field when selecting the ‘Selected Field’ in the source tree. This issue has been resolved by displaying all query field statements that have been queried.
