Fixed various issues regarding the Import Metadata and Open Editor Function #
- When using the XSD file type and uploading an XSD file on the Import Metadata screen, an error occurs, causing the screen to become stuck after clicking Save. This issue has been resolved.
- There is an issue when uploading a JSON Schema file without the ‘title’ keyword. If you choose the ‘From the keywords ‘title’ option on ‘Choose the name for the root message type’ in order to generate the root message type, it results in an endless spinner. However, this issue has been fixed.
- Select the check header box in the message type section and delete them. However, the checkbox headers remain checked even after they have been deleted. This issue has been fixed.
- When importing a JSON file in the Open Editor, if you input an incorrect file and then save it, the pop-up screen will close and an error message will be displayed. However, when reopening the Open Editor, the screen does not refresh and still retains the previously selected.
- In the JSON Schema Open Editor, if an incorrect file is input and the Next button is clicked, an error message is displayed. However, clicking the Back button takes you to the upload file screen instead of returning to the input text box. This issue has already been fixed.
- In the XML Open Editor, if you input an incorrect XML format, it still allows you to import and create the message type. However, this issue has been resolved by adding an error message stating, ‘Invalid XML text entered.’
- The spinner did not stop while entering to repository page because the user had unchecked “Use Lightning Web for Lightning Web and Aura components Mode”.
- On Open Editor function for import Message type. When selecting JSON Schema/JSON file format gets a pop-up screen error message “Uncaught Assertion Failed!: Descriptor for Config required for registration : undefined”. This issue has been resolved.
Fixed Successful Ping Connection, but Incorrect Alert Message Displayed #
An issue occurred when adding the correct credentials to Microsoft OneDrive. The alert message for the ping connection displayed a code 200 with a failed message alert. We have now resolved this issue by changing the alert message color from red to green and providing a JSON response.
Fixed Created Message Type #
- If your XML file contains prefix namespaces, the prefix namespaces will be included when creating the message type. However, this issue has been resolved by removing the prefix namespaces during the message type creation process.
- If your XML file has many records without a root tag, the import message type will be generated incorrectly. Fixed by adding the message error “XML Parsing Error : This page contains the following errors:error on line x at column x: Extra content at the end of the document Below is a rendering of the page up to the first error.”
- In the previous version of importing message types, namespaces were generated for all message type nodes. However, in the current version, namespaces are only generated for elements that have on themselves.
Apex Heap Size Issue When Deleting Messages with Multiple Child Messages #
You may encounter the apex heap size limit when selecting all messages (10,000 records) that have a large number of child for deletion using the ‘Delete’ or ‘Cancel’ buttons in Message Monitoring. This issue has been resolved by stopping the ‘BatchGenerateMessage’ job to collect messages and pass all messages collected to the ‘BatchDeleteCancelAllMessage’ job instead of using only one job ‘BatchDeleteCancelAllMessage’ to query and delete.
‘Manual Process’ Remains Disabled When Closing the Log #
When you select the main interface, the ‘Manual Process’ button will be enabled. However, after clicking the ‘Log’ button and closing it, the ‘Manual Process’ becomes disabled, even when the main interface is still selected. This issue has been resolved.
Interface Not Refreshing After Delete Inteface on Interface Detail Page #
The interface does not refresh after deleting an interface on the Interface Detail Page. This issue occurs when attempting to delete or edit interfaces, potentially causing problems. There are two scenarios that occur when deleting an interface:
- Deleting a sub-interface will trigger a reload of its parent.
- Deleting the main interface will trigger a self-reload
Fixed to Display Giving Interface Name on Tab Name #
When you edit the interface records on the Interface Detail page and save the changes, the interface will display an automatically generated name. However, this issue has been fixed.
Fixed not being able to search Adapter Name on the Interface Detail #
There is an issue when searching for a name in the adapter settings on the screen interface detail for both the Inbound and Outbound adapters. The search function is not working properly, but this issue has been resolved.
Fixed not being able to retrieve Source Tree value while selecting parent sObject in Hybrid Mode #
When performing the function on the mapping, you can select the Source Tree and Source Fields to apply the Expression Formula. However, if you select the parent nodes in the Source Tree and the Parent Field in the Source Fields, it would only retrieve the Parent field, and the Parent Reference sObject would not be retrieved in Hybrid Mode Mapping. Fortunately, this issue has been resolved.
Fixed SObject row was retrieved via SOQL without querying the requested field: sObject.ExternalId Field #
There was an issue when checking multiple external ID fields in the mapping for the Upsert Operation Type. After pushing the records, the external field would not be queried, resulting in an issue with the comment ‘SObject row was retrieved via SOQL without querying the requested field: sObject.ExternalId Field.’ This issue has been fixed by checking the mapping’s external ID field as Salesforce ID. Consequently, the integration now upserts records using the Salesforce ID value instead of other external ID mapping fields.
Fixed Searching Message Getting alert Message Error “Error Line: 334:Invalid Id: xxxxxxxxxxxx” #
When you have searched for All messages that include the message with an invalid the salesforce id. The issue will be raised and get the failed message alert “Error Line: 334:Invalid Id: xxxxxxxxxxxx”. This issue has been fixed.
