Mapping is Always Lost After Updating BAPI Message Type #
An issue arises when attempting to update the message type by reimporting the BAPI Metadata. After reimporting, the existing message type gets updated, leading to the loss of mapping. However, this issue has been resolved by ensuring that the ‘Source/Target Message Type’ is not removed from the interface during the metadata re-import process.
Fixed Issue Exporting CSV Files with Data Loader including the special character ‘#’ hash #
We encountered an issue when exporting the CSV file that contains the ‘#’ symbol within the data. This was causing errors, resulting in an incorrect format and missing data. Fortunately, this issue has been resolved.
Resolved Issues in the Search Filter of the Interface List on the Integration Page #
- Fixed issue cannot filter interface name records where the interface name field contains the word search. You can search only a specific interface name. Now you can search for both of them.
- Issue fixed: Filtering and retrieving interface names outside of this Integration.
Various Enhanced On Mapping Tool #
- We have improved the view Source Field by displaying a more readable value. For example, if you have set a filter on the field, the original value ‘SF!$!Contact.SF!$!Case.SF!$!Subject_FirstName’ might have been unclear. We have now updated it to ‘SF.Contact.SF.Case.SF.Subject_FirstName’ for better understanding.
- Significantly enhanced the capability to set the Ext Id on mapping for inbound V3 by simply selecting the ‘Ext Id’ checkbox. Notably, you can now set the checkbox without the need to define the External Key using new approaches.
- We have implemented a custom alert message to enhance user-friendliness on the mapping tool.
Fixed Various Issues Update incorrect Message Status #
- We have encountered an issue during the Request and Response process with the SAP CPI Adapter. Specifically, when receiving a failed response, the API message does not update its status from ‘completed’ to ‘Partial Completed.’ This issue occurs when using the invokeCalloutV3 method in various modes such as Future, Queueable, Batch, Auto, and message_only.
- Incorrect Update of API Message: After reprocessing the message, the API Message incorrectly updates as ‘failed’ even though some business messages are completed successfully while others have failed. This issue has been resolved by updating the status to ‘Partial Completed.
- We encountered another issue when calling the ‘SAP CPI’ adapter and performing the ‘Get’ operation without mapping (only querying data for inbound processing) using callout modes such as Future, Queueable, Batch, Auto, and message_only. As a result, both the request business message and API Message remained in a pending status. However, we have resolved this issue by updating the message statuses correctly.
Fixed Issue: Unable to Add Interface to Interface Group #
This issue occurs when attempting to add an interface to an interface group that contains multiple interface records within the integration. It results in an error message alert stating, ‘Please enter the value in Sequence.’ The issue arises during the interface trigger when verifying and validating the source name of the interface. We have resolved this problem by using Type.forName(‘xxxxxxx’) instead of Schema.getGlobalDescribe().get(‘xxxxxxx’). This approach provides faster performance and prevents validation checks during interface updates within the Interface group.
Fixed Issue of the MessageReprocessPerInterfaceGroup Scheduler #
We have resolved the issue with the MessageReprocessPerInterfaceGroup scheduler that was causing a mix-up between inbound and outbound reprocessing messages that caused an incorrect setting of Processing Package size to outbound.
To fix this issue, we implemented the following solutions:
- Ensured that inbound and outbound processes are not mixed within the same scheduler of the interface group. When the interface group contains only outbound interfaces, the scheduler will execute the outbound worker job (IServiceBatchCallout) to reprocess the outbound messages.
- Similarly, when the interface group contains only inbound interfaces, the scheduler will execute an inbound worker job (IServiceBatchReprocess) to reprocess the inbound messages.
- The issue with the scheduler on the interface group that reprocesses outbound messages with a processing package size greater than 1, even when the Processing Package Size is blank, has been resolved. The issue occurred due to a mix-up in the scheduler’s reprocessing of request/response messages (outbound/inbound messages) within the same group. When the ‘Processing Package Size’ setting is blank, the following default values will apply:
- For outbound message reprocessing, the setting will be 1.
- For inbound message reprocessing, the setting will be 10.
Fixed exceeded 100000 distinct who/what’s of inbound processing with event object #
This issue may arise when using ‘List<SObject> lst = [SELECT Id FROM SObjectX WHERE IsDeleted = false LIMIT 0];’ in Inbound Processing with Event sObject. If you exceed the limit 100000, you will encounter an error message stating ‘First error: exceeded 100000 distinct who/what’s’. To resolve this issue, consider using ‘List<SObject> lst = new List<SObject>();’ instead.
Overlapping Interface Text on View Screen on Compact Mode #
We have encountered an issue where the text on the interface view screen overlaps when the screen size is small and the input text field contains a long value on Compact Mode. This problem has been addressed by implementing a responsive interface detail screen, ensuring that the text view is displayed properly without any overlapping.
Resolved Frozen Data Loader Screen When Selecting All Records, Appending Their Child Records, and Pushing Records with Raw Upload File #
We have identified an issue that occurs when selecting all records and appending their child records using the Raw Upload File. After pushing these selected records, you may experience a frozen Data Loader screen. We are pleased to inform you that this issue has been successfully resolved.
Error Encountered When Navigating Back to the Interface Group Tab #
When you click on the Interface Group Name link in the Interface Group List of Integrations, you will be directed to the Interface Group Detail Page with a new tab. However, upon returning to the Interface Group List, you may encounter a pop-up error screen displaying the message: “Cannot read properties of undefined (reading ‘split’).” We are pleased to inform you that this issue has been resolved.
Resolution of Update Issue with Integration Records in the Presence of Multiple Interfaces #
We have identified an issue when updating integration records in the presence of multiple interfaces. During this process, you may encounter the following error message: “skyvvasolutions.trgBI_Integration: System.limitException: skyvvasolutions: Too many SOQL queries 101.” We are pleased to announce that this issue has been successfully resolved.
