Always display Sub-Interface with a few lookups fields

There is an error that occurred while a few fields have been lookup with Sub-Interface such as Parent Interface, Invoke Outbound/Inbound Interface, and Request Interface field in Inbound/Outbound Setup section wherein Interface Details Page. Therefore, the sub-interface should not have displayed and selected on the screen. This issue has been fixed.

Get an error while manually processing the same baskets many times

This issue was in processing manually the same baskets many times. It gets an error with the null value cause the baskets already processing. This issue has been fixed.

Always Delete Child Records while processing the same batch apex execution

Skyvva has Delete First mode in Init Operation on IChained Interface Inbound for deleting child records. There is an error that occurred while the user is processing integration with batch mode. The baskets contain many records; therefore, batch apex will split messages into small packet sizes per batch execution. The records repeat the parent, so the last execute will be deleted the child records of the first execute. This issue has been fixed.

Not able to Pushing Attachment into reference Sobject

To associate two records in a relationship, therefore Skyvva has a vlookup formula in the mapping tool. Vlookup formula is not able to lookup the source field while pushing attachments with Sobject. The error has been fixed.

Not able to read CSV encoding UTF-8 file with Manual Load of Lightning component

To upload records with SKYVVA manual load, and manual load is able to support CSV, XML, and XML hierarchy. The user has a CSV file that is not encoding UTF-8 after the user converts the file to encoding UTF-8. However, the lightning component is not able to get records from the file. The error occurred has been fixed.

Not able to alert error Storage Limit Exceeded with various lightning component

Fixed various issue related storage limitation

• When using manual load to push the records, the status batch apex job shows as completed. However, the records didn’t push. This issue happens when the storage is full. Instead of the success message, the error message will be appearing in the batch apex job.
• To create filter message conditions were on the workflow page. The workflow has been created by the user while the storage was limit. The alert message was showing successfully, however, the workflow didn’t create. Instead of the alert-success message, the alert error message will be appearing on the screen.
• When using the Import MetaData Provider button to import MetaData Provider, the status batch apex job shows as completed. However, the MetaData Provider didn’t import. This issue happens when the storage is full. Instead of the success message, the error message will be appearing in the batch apex job.