- The asynchronous call got the error "null input to JSON parser" with mode "Batch Apex"
- Reprocess not work with child Bussiness sObject message
- Fixed Rest Adapter with SOAP XML Format
- Fixed V3 inbound processing while the response payload has an empty node
- Always remove the manual query while saving the outbound mapping
- Fixed not being able to update messages after reprocessing the messages
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.
Reprocess not work with child Bussiness sObject message #
We fixed the reprocessing parent business sObject message that does not take the child message to reprocess. This issue happens only with a message push from Data Loader. For example, you pushed three message levels such as Account, Contact, and Case to reprocess despite you getting the failed reprocessing. The message will have Data Loader Message as the parent of the Account, the Account child’s Contact, and the Contact child’s Case. Then, you reprocessed the failed Account Bussiness sObject Message. Therefore, it does not work with the child message of the Account.
Fixed Rest Adapter with SOAP XML Format #
There is an issue with the rest adapter sending the SOAP XML format e.g. soap envelope in XML syntax is used exclusively in the soap adapter and not in the rest adapter. Fixed this issue by sending and receiving with pure XML (Pure Business Data).
Fixed V3 inbound processing while the response payload has an empty node #
Inbound v3 processing gets an error message “Failed inbound processing, Please check response and inbound interface!” because some systems will respond with an empty node array while the fields did not have any value field map. This issue has been fixed by not creating the message for the node empty anymore.
Always remove the manual query while saving the outbound mapping #
Got a problem removing the manual query while after saving the outbound mapping. Now we have fixed this by merging manually added with an auto-generated query from the mapping.
Fixed not being able to update messages after reprocessing the messages #
Fixed added duplicate message id to the list of updated messages while the users have been reprocessing the message. This issue has been fixed.
Generate Node without mapping request body of Rest Adapter #
There is a problem when the user does not map the source node to the target side message type request body in the Rest adapter and it still was generating the root node using the source object of the outbound interface. Therefore it was creating problems when we are sending requests using the GET protocol. The issue has been resolved.
Auto Mapping parent reference field #
This issue occurred while auto-mapping with the parent note reference field of the child. Therefore, it will generate an extra node and fields for the mapping. This problem has been resolved.
Get message error “Error:skyvvasolution: Too many query rows: 50001” on delete/cancel/ reprocess message function #
This error happened when you processed records by Dataloader or Basket, and you will get a few message root messages containing too many child business messages. Therefore, you will get an error message “Error:skyvvasolution: Too many query rows: 50001” while you try to use the delete, cancel, reprocess function. This issue has been fixed.
Note: if your hierarchical messages are more than 10000 records, it will take only 10000 records to reprocess per batch in per transaction.