Hide Forgot
Steps to Reproduce: 1 - deploy the attached VDB, SFTestVDB.vdb 2 - execute query "SELECT Name,CreatedDate,MondayStartTime FROM SFTest.salesforce.BusinessHours" project_key: SOA Query the BusinessHours table imported from Salesforce, which contains columns with 'time' datatype. For example, the query: SELECT Name,CreatedDate,MondayStartTime FROM SFTest.salesforce.BusinessHours Results in: Error Code:ERR.003.029.0025 Message:Failed to transform String to Time. Expected format = hh:mm:ss for 08:00:00.000Z It looks like the code in QueryExecutionImpl.getCellDatum needs to handle translation of the salesforce time format Other issues: - nil string values will be returned as empty instead of null. - non-join criteria of the form column1 = column2 is rendered inappropriately (however it is not supported by SF we should look at restricting criteria support to literals) - IN predicate time/date/timestamp values are not formatted correctly - timezones are ignored on returned time/timestamp values. So unless the server is in the same timezone as the values (typically Z/GMT) the local value will be incorrect. - a timezone is not included on literal times, which has the same issue as above. - IS NULL support should be added using col = NULL
Link: Added: This issue Cloned from TEIID-1852
Security: Added: Public
Link: Added: This issue is a dependency of SOA-3656
Link: Added: This issue Cloned to SOA-3658
Link: Added: This issue is a dependency of SOA-3658
Link: Removed: This issue Cloned to SOA-3658
Link: Removed: This issue is a dependency of SOA-3656
Steven Hawkins <shawkins> updated the status of jira TEIID-1852 to Closed
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Errors were appearing when using tables from the Salesforce Translator. When querying a BusinessHours table imported from Salesforce, an error was thrown indicating a transformation failure. This has been fixed so the Salesforce time format is handled correctly. The tables will display as expected.
I verified this using ER5. It works.