Not able to delete more than 1000 message records
There is an error occurred when to user deleted the message including filters such as Interface Name and Comment Content and the message records are more than 1000. After you click the “Delete All” button, you will get the message error “Error line:711:unexpeced token: And”. This issue has been fixed.
Fixed issues of mapping generating path and runtime processing
Fixed several issues related to mapping that generate the wrong path and not working with the runtime processing.
Getting an error while backup IMapping on the interface
While backup of IMapping on the interface it will get an error text=”<![CDATA[#{ctx.skyvvasol]]>” EL Expression Unbalanced: … #{ctx.skyvvasol]]>. This issue is fixed.
Not able to update the MetaData Name
There is an error occurred while the user try to update the MetaData Name. The error is caused by IStructure being the names. This issue has been fixed.
Update Bulk API to Version 50 on Skyvva App
In the previous version, the Skyvva app use version 30 for the Bulk API calls. Salesforce will retire API usage till version 30 in Summer 23. Therefore we have updated it to version 50. The user also set the version by executing this snippet code in the developer console. For example, skyvvasolutions.IServicesUtilConst.setKey(‘BULK_API_VERSION’, ’51’);. It will work only on the deletion message that executes from the salesforce bulk API.
Getting error “ListExceptionRow with duplicate Id at index: XX”
Getting an error “ListExecptionRow with duplicate Id at index:xx” while you do V3 inbound processing IntegrateWithIMessage that external id has a concat formula with parent field and itself. The external id’s parent field value will get null. This issue has been fixed.
The asynchronous call got the error “null input to JSON parser” with mode “Batch Apex” #
There is an error that occurred when the user pushed the record containing more than 131072 lengths with the Asynchronous call of Batch Apex Mode. The message’s data is too long. Therefore, It will write the records into the ContentVersion. The problem happens the message’s data cannot be read from the file and it raises an error message “First error: null input to JSON parser” on the apex job. This error has been fixed.
Skyvva Data Loader faced an issue with Salesforce limit parsing Data #
There is an issue that occurred while the user imported the CSV file with a large amount of data. Therefore our Data Loader does not import the data and gets a non-stop spinner due to an issue with Salesforce limit parsing Data. This issue has been fixed by splitting data into small amounts in order to avoid this error happening.