1. Home
  2. Dokumente
  3. Release Notes – SKYVVA Winter ’20 V 2.44
  4. 7. Patch V2.44.7
  5. 4. Bug Fixed

4. Bug Fixed

Missing a few fields while Exporting and Importing

Fixed various issued in exporting and importing

  • While the Integration/interface has been imported and exported, the direction field is missing in the adapter. The issue has been fixed.
  • Fixed missing a few fields in interface object after export and import such as Bulk Version, Bulk Processing Mode, and Bulk Integrate Time Interface.

Not able to update API message inbound processing

API Message is a group of messages after processing with request and response Rest/Soap in v3 processing. It will be get partial completed status while the child message has mixed-status such as completed and failed. The user is able to processing failed message with reprocess button in Message Monitoring after the child has been completed all, but the API message will not update the status from partial completed to completed status. This is issue has been fixed.

Disable to display interface using SFDC Bulk API 1.0 and SFDC Bulk API 2.0 in Bulk Control Board

There is an error that occurred while the users choose the bulk version as SFDC Bulk API 1.0 and SFDC Bulk API 2.0 with checked bulk flag. Therefore, the interface will be displayed in the bulk control board. The SFDC Bulk mode is processing directly to salesforce; therefore, we don’t need it in Bulk Control Board.  The issue has been fixed by display only SKYVVA Bulk 1.0 and none choosing.

Some error while the governor limit exception is raised

Fixed various issues in governor limit exception are raised:

  • Alert message successful while the workflow is not able to save into salesforce due to storage limitations. Fixed issued by alert error “Upsert failed. First exception on row 0, first error: STORAGE_LIMIT_EXCEEDED, storage limit exceeded: []”
  • Not create message while pushing records using manual load during the storage limit exceeded. Fixed issue by alert status details in apex job “First error: STORAGE_LIMIT_EXCEEDED, storage limit exceeded”
  • Send an email that import script is successful, however, the MetaData Provider is not able to import into Salesforce due to storage exceeded. Fixed issue with sending email for alert failed to import “The import script failed! Please go to apex job to see the error detail.”
  • Alert message error as “Error Insert IStructure” and Error Insert Message Type” while importing the MessageType and IStructure was in upload file in the repository because of storage limit exceeded. The alert error will change to “Upsert failed. First exception on row 0, first error: STORAGE_LIMIT_EXCEEDED, storage limit exceeded: []”.
  • Not create the scheduler was in the Integration page, therefore the storage has been exceeded. Fixed issue by alert error message “error:Upsert failed. First exception on row 0; first error:STORAGE_LIMIT_EXCEEDED, storage limit exceeded: []” when the user click the scheduler tab and refresh button.
  • Not create scheduler was in the CDC Control Board page, therefore the storage has been exceeded. Fixed issue by alert error message “error:Upsert failed. First exception on row; first error:STORAGE__LIMIT_EXCEEDED, storage limit exceeded: [] ” when the user clicks the scheduler tab and refresh button.
  • Change alert message error from “Error changing default log file name” to “error:Upsert failed. First exception on row; first error:STORAGE__LIMIT_EXCEEDED, storage limit exceeded: []” while the user changes log file name was in Process Logs (Attachment) section of Integration page due to storage limit.
  •   Not able to export metadata provider while the storage limit. Fixed issue by change alert from “Some error occurred while processing” to “Insert failed. First exception on row 0; first error: STORAGE_LIMIT_EXCEEDED, storage limit exceeded: []”.

Missing Source Field on IWorkflow

The user is able to choose the source field to build filter conditions on workflow; however, the source field has been lost in the parent interface. This issue has been fixed.

Getting Error while uploading XML HIERARCHY with the wrong format of Mapping

There is an error that occurred while uploading the XML hierarchy was in Manual load that is not the same format of Mapping in the Mapping tool. Therefore, it will get error “TypeError: Error in $A.getCallback() [data is undefined] Callback failed:apex://skyvvasolutions.ClsFiletegrationController/ACTION$getInterfaceStructure”. This issue fixed by adding an alert message “The file that upload is the different file in Mapping!”.

Fandest du diesen Artikel hilfreich? Ja Nein

Wie können wir helfen?