4. Bug Fixed

Fixed Various Issues regarding the Query Editor of the Inbound Interface with the Agent Database

Some issues have been fixed with the Query Editor  as follows:

• Fixed an issue where, for inbound processing with the Agent Database, opening the Query Editor without a defined query in the interface resulted in the error: status: 500, Index -1 out of bounds for length 0. This issue has now been resolved.
• There was an issue when opening the Query Editor for the inbound interface with the Agent Database adapter behind a non-open firewall. After loading, some entries did not have a table name or fields displayed. This issue has been fixed.
• We identified an issue in which selecting a table twice caused the table to disappear and become unselectable. This defect has been fixed.
• We identified an issue where, during query loading, a field included in the SQL statement was not marked (checked) in the selection box. This has been resolved: fields that appear in the statement are now automatically checked.
• In the Query Editor, queries containing WHERE conditions did not render the WHERE clause correctly after loading. We have fixed the issue; incorrect WHERE clauses are no longer generated."
• After executing the query, a 'SELECT TOP (...)' header was being added to column fields, causing incorrect query results. This issue has been resolved — the header is no longer generated, and the query now returns the database results correctly. 
• While the Query Editor was open, the Execute SQL and Save SQL Query buttons became disabled. This issue has been fixed, and the buttons are now enabled.
• When the Interface contains an empty query, and you open the Query Editor, select a table and paste the SQL statement manually. After executing the SQL and clicking Next page, the data is displayed with an incorrect header.

Fixed Various Issues with the Formula Function

The following issues related to formula functions in mapping have been fixed:

• Fixed an issue where the SPLIT(text, separator [, index]) formula returned an error when the input text was a ‘null’ value. For example, if a mapping passed a null value to accbillingcountry and used SPLIT(accbillingcountry, ",", 1), the formula returned the error 'Unable to evaluate expression!'. This issue has now been resolved, and the formula returns an empty value instead.
• Fixed an issue where mapping records that generated NULL values were incorrectly included in the interface query statement. For example, with the following formula mapping:
  • AccountNumber => AccountNumber
  • Name => Name
  • BillingCountry => CASE(Country, 'Cambodia', 'KHM', 'India', 'IDN', NULL)The query was correctly generated in the interface sObject query field as SELECT Id, BillingCountry, AccountNumber, Name From Account. However, after removing the Name mapping, the query was incorrectly generated as SELECT BillingCountry, AccountNumber, Null From Account. This issue has now been fixed, and Null is no longer added to the query.