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 Always Alert Failed Message While “Switch Off Message Processing Alert” is True #
We have a DoAlert Scheduler to process alerts when the scheduler accidentally stops and gets a failed message. Currently, when you enable the “Switch Off Message Processing Alert”, the message failed still alert. 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.
Fixed the Issue of Having Huge Baskets on the Generic Basket Page #
An issue occurred in the Basket Generic Page, where when there are many baskets (around 50,000 or more), clicking on the Basket Generic tab would result in an error alert stating “JSON string exceeds heap size limit”. This issue has been resolved by adding pagination and limiting the records displayed to 10,000. Each pagination page now displays 100 records.
Fixed Return -1 Day on Query Param with Last Run Date Scheduler call of Sage 100 Adapter #
We have resolved an issue that was occurring in scheduled outbound interfaces where the dynamic query parameters were being built incorrectly. Specifically, the sage 100 adapter logic was subtracting one day from the scheduler’s last run date and time, causing the operations to be performed with the wrong date and time values. We have corrected this logic to properly utilize the accurate scheduler’s last run date and time, eliminating the unintended date adjustments and ensuring the scheduled interfaces operate as expected.
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.
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 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 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.
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.
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.
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 Alert When Not Run Function #
In the previous version, setting up an alert configuration with multiple sObjects inside an integration could cause issues. For example, if you had already set up an interface and an interface group, resulting in an error when querying the InterfaceControlRuntimes. This would then prevent the alert notification from being triggered when the scheduler didn’t run. Fortunately, this issue has been fixed in the current version.
Fixed Not Allow to Create the Second Interface Control Runtime #
The error in the trigger when creating a second Interface Control Runtime arises error: ‘Not allow to add Interface Control Run Time more than one record per interface’. This occurs when the first Interface Control Runtime, linked to a specific Integration/Interface Group/Interface, is set as ‘Alert When Not Run’. and you try to create another Interface Control Runtime with a different record type that links to the same interface/Interface group/Integration will trigger an error. This issue has been resolved.
Fixed Text Overlapping in Another Column When Switching to ‘Swap Text’’ #
Fixed an issue in the Agent Cache data table where selecting “Wrap Text” caused the data in the “Swap Text” column to overlap with other columns.
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.
