We are working on upgrading from Rockaway 8.15.17 to Brooklyn 9.5.6 (we have a dev and qa sandbox, dev is using Brooklyn and qa is still on Rockaway). We have some custom components that stopped working in our dev environment after the upgrade to Brooklyn and we’ve got most of the issues ironed out except for one, which appears to be a bug with Skuid’s sfdc.search(…) function.

Our code is virtually identical to what’s in the documentation here: https://docs.skuid.com/latest/en/skuid/api/skuid_sfdc.html

However, even though we pass the same request object in both Rockaway and Brooklyn, the sosl that the search(…) function builds is wrong…the sosl isn’t complete and we get an “unexpected token: ‘’” error as a result.

Example:

The sosl in Rockaway:

• 
  ```
  FIND 'CasePriority*' IN NAME FIELDS RETURNING Skuid_Picklist_Value__c(Name,Value__c)
  ```
  

• 
  ```
  FIND '*' IN NAME FIELDS RETURNING
  ```
  

skuid.$.when(skuid.sfdc.search({
query: "CasePriority",
searching: "NAME FIELDS",
returning: {
"objectName": "Skuid_Picklist_Value__c",
"fields": "Name", "Value__c"]
}]
})).done(function(searchResult) {
/* skipping the complex stuff that would normally be here, for the sake of this email, and just logging the result */
console.log("SEARCHRESULT:");
console.log (searchResult);
}).fail(function(searchResult) {
console.error('Search failed: ' + searchResult.error);
}).always(function(searchResult) {
console.log('Raw SOSL generated: ' + searchResult.sosl);
console.log('Original search request');
console.log(searchResult.request);
});

Any thoughts? Thanks in advance.