Get “Too many query rows: 50001” on Bulk Processing Basket #
When you have numerous bulk baskets with over 50000 basket records and you set the scheduler to process them, the system will query all the bulk baskets and filter them for processing. However, this can lead to an issue where an error message is raised stating ‘Too many query rows: 50001’. Fortunately, this issue has been fixed.
Fixed Various Issues Regarding Find & Replace Function #
- The Interface may not refresh the interfaces on the Find & Replace the second time cause you may make a change to the interface. For example, you remove or create an interface. This issue has been fixed by refreshing the interface after clicking the Find & Replace Tab again.
- Previously, when there were failed messages with no iData on the outbound interface, an error alert was displayed after selecting the outbound interface. This issue has now been fixed, and instead of the error alert, a warning message “No Failed or Pending Messages are Available” is shown.
- In the previous version, the formula headers in both the mapping and workflow functionalities displayed the complete formula. This resulted in some issues. However, in the current version, the formula headers in both the mapping and workflow functionalities now only show the field names of the formula, rather than the full formula, in the header of the find and replace function.
- This error occurs when the interface’s source name is defined with an external object in Salesforce, causing the error when it cannot query the value of the source field in that interface. This issue has since been resolved
Direct Link Message Waiting for First Message Process in V2 Processing #
In our message flow, when the first message fails, the second message has the same external ID as the previous one. It will be pending and will wait until the first message is processed. The second message will not provide a direct link to the failed first message. This issue has been resolved by providing the direct link to the first failed message in the comment.
Fixed Check Adatper Status Before Creating the Message of InvokeCalloutV3() Processing #
In the previous version, the InvokeCalloutV3() function did not check the adapter status while creating the message. However, in the adapter, it would follow the status rules. If the status was not active, we would not have created the message before calling InvokeCalloutV3(). This issue has been fixed, and we have now provided validation to create the message based on the status of the adapter.
Fixed Update skyvvasolutions__BulkReprocessScheduledJobId__c Field Issue on Interface Records #
Previously, the scheduler would update the ‘skyvvasolutions__BulkReprocessScheduledJobId__c’ field on the interface record with the Schedule Job Id. This field was used to store the job ID for the scheduler. However, this was caused by users auto-modifying the interface record. The field was used in an earlier version of our bulk feature but is no longer needed in the current version, as we now store the job ID directly on the skyvvasolutions__IScheduler_Setting__c object instead. This issue has been resolved, and the interface records are no longer updated with the Schedule Job ID.
Fixed Issue with Test Formula on CDATE #
During testing, we encountered an issue with the formula mapping that uses the CDATE function. The issue was caused by the ‘IF’ condition, which could produce unexpected results. For example, the formula: IF(Field = ‘#N/A’, ”, IF(Field = ‘Purchased’, ”, CDATE(Field, ‘m/d/y’))) was resulting in the error message: “Output Line:1587>CDATE>dataText [Purchased] does not correspond to the format [m/d/y]”. This issue has been fixed.
Fixed Various Issues on the Batch Control Board #
- When attempting to filter by Comment, an error message previously popped up stating “Error: field ‘skyvvasolutions__Comment__c’ cannot be filtered in a query call, causing the application to get stuck with a spinner. The issue has been resolved by removing the filter on the ‘Comment’. This is because the ‘Comment’ field is a text area field that cannot be specified in the WHERE clause of a queryString in a query() call.
- Fixed an issue where users could not delete all history baskets on General History Baskets, which would raise an error and display the message “Fail to delete basket history!”. This issue has been fixed.
Resolving Scheduler Display Issues on the Agent Control Board #
In the previous version, we encountered an issue where the Salesforce agent’s next-run scheduler would fail, and the scheduler records did not display on the scheduler tab of the agent control board. This issue has now been fixed. The scheduler records and their associated comments are now correctly displayed on the scheduler tab, with any issues or errors marked in red.
Issue Fixed – Saving Name Edits on Restore Interface Screen #
We previously encountered an issue where users would receive an error message when attempting to save edits made to the name field on the Restore Interface screen. The error message stated: ‘TypeError: Action failed: skywvasolutions:ImportSKYVVASobjectsScriptScontroller$handleSaveEdition [mapping[j]( sn + “Full Source_ Path_c’)] is undefined]. This issue has been resolved.
Fixed Issue related to “Delete child not present in the payload” While Using Workflow #
We previously encountered an issue where the deletion of child records was affecting parent records that were updated through different target interfaces in the workflow. For example, if you had defined an interface called ‘AccountIn’ with the ‘Ichiain Contact (Delete child not in the payload)’ option, and then defined another workflow target called ‘AccountParentIn’, any contacts associated with accounts that were updated through the ‘AccountParentIn’ interface would be incorrectly deleted. This issue has been resolved by ensuring that the child records are not deleted if the interface does not have the ‘Delete child in the payload’ option set.
Fixed Issue Edit Field Inside Interface Details Page #
We have an issue with the edit field on the interface detail page. After saving the value, an error message appears. This issue has been resolved.
Fix for IStructure Deletion When Updating Query Old Design Outbound Interface #
There was an issue where, upon updating the query of the old design outbound interface, the old IStructure created by the Agent would be deleted immediately. This issue has now been fixed, preventing the deletion of the Agent’s IStructure.
Resolved Issue: Unable to Open Adapter List #
We have an issue when entering the Apdater list, it will raise an error message pop-up alert “Cannot read properties of undefined (reading ‘Name’)]) The issue arises when the adapter queries the Connection Destination Name, which does not exist in Salesforce. This issue has been resolved.
Resolved Error: ‘Too Many Query Rows (50001)’ on Bulk Control Board #
There is an issue when accessing the Bulk Control Board. A Message Error Alert appears with the text “skyvvasolutions: Too many query rows: 50001”. This error occurs due to the large number of baskets being queried. For example, the Bulk Control Board queries 50,000+ Baskets and History Baskets. To resolve this, we have set a limit of 10,000+ History Baskets to display on the screen.
Automated Replacement of Dots in IStructure Field Causing Data Synchronization Issues #
We have identified an issue with the dot (.) character in your IStructure field, for example, ‘Account.Name’. Previously, our system would automatically replace the dot (.) with a dollar sign (!$!) symbol during the Source_Long__c field mapping, which resulted in incorrect data synchronization. We have now fixed this issue by removing the automatic replacement of the dot (.) with the (!$!) symbol. However, in the existing cases where the replacement has already occurred, the Set Context Function still remains with the automatically generated dollar sign (!$!) symbol.
Fixed Bug on Rebuild Cache Function #
When you click to rebuild the cache, an issue occurs: the caches appear briefly and then disappear. This issue has been by deleting the old cache and recreating it to ensure that the cache is clean and functions work properly.
Duplicate WHERE Clause Generated in Query After Removing Mapping #
We encountered an issue when removing a field from the mapping. The SOQL query generated additional WHERE clause conditions. This issue has been resolved.
Fixed CSV File Import via Email Adapter #
We encountered an issue when importing CSV files with data payloads containing quotes (“). This caused the CSV format to be invalid. The problem has been resolved by removing all quotes and inserting only the values without them.
Fixed Duplicate Sequence in Mapping Records #
We encountered duplicate sequences in the mapping records, which caused the payload to be generated incorrectly. This issue has been resolved by generating the numbers in order, ensuring that duplicate numbers are no longer generated.
