10.2.1.2 vs. the new Salesforce API <SOLVED>

[squish88]

Hey guys,

    So, we're getting this weird problem when connecting to SOME of the objects via the new API to our instance of SalesForce.  More specifically, when we try to connect to the Case, User, or Lead objects, we get this message when we hit "Finish" to create/validate the new query subject:

"XQE-V5-0020 "Encountered "Case" at line 602, column 41. Was expecting one of: "absolute", "absent", "action", "aggregate", "anytype", "asc", "bit", "cascade", "collation", "columns", "content", "data", "date", "day", "desc", "document", "empty", "first", "flag", "following", "general", "global", "hour", "ignore", "index", "input", "install", "java", "java_object", "key", "last", "local", "long", "minute", "month", "name", "names", "next", "nfc", "nfd", "nfkc", "nfkd", "nil", "nulls", "number", "option", "ordinal", "ordinality", "passing", "path", "period", "preceding", "precision", "preserve", "public", "remove", "respect", "second", "sequence", "sets", "size", "string", "strip", "style", "temporary", "time", "timestamp", "unbounded", "view", "whitespace", "year", "zone", <IDENTIFIER>" 

   Now, we know it's not how we've set up the environments, 'cause we're able to successfully create query subjects for, and connect to, validate, and get test data for almost 20 other objects.   The person in charge of our Salesforce connection claims that those 3 problem tables are correctly exposed (just like all of the other objects) on the SF side of things, so we know it's not that....

   So, we pared it down to pull in only the "Id" field to try to narrow down what it may be that is causing the issue, and it seems to be choking on the "case" table name...  Which makes us think it may be a problem with how their code handles reserved words, but that's just a guess.

   We tried again with a simple, standard SOQL kinda query:  "SELECT Id FROM Case"  in native, and pass through to see if that might work, but no luck there either.

  Based on what we've gotten from IBM support thus far, we "may" have discovered a bug in their code, though they haven't committed to that quite yet.

Anyone have any ideas??   Has anyone else run into this issue with those tables by any chance?

Thanks in advance for any help!!

[squish88]

In the event that anyone else runs into this issue, the "fix" for it was to highlight the data source, expand "Type" in the properties panel, and add "ERP-SFDC" into the Interface property.   Once we did that, the Lead, Case, etc. objects worked properly as long as the table names had quotes around them.

For example:

Select Id
From [SalesForce API]."Lead" AS "Lead"