LookupObjects ( at most 1 ) doesn't work for date or datetime field types

christianjosephvarriale commented 4 years ago

Summary

The lookupObject.js file currently doesn't differentiate between a date / datetime field and a string. As per the documentation on SOQL queries, date objects should not be enclosed in quotation marks which is why the error above is thrown. When the SOQL query is generated, it is in the form of "query WHERE 'custom_field__c = '{{date_str}}' "

I have attached my current solution used for the deleteObject.js code in a screenshot.

Steps to reproduce

Select the Salesforce Component function 'Lookup Object ( at most 1 )'
Select any object and field which is either type date or datetime
You will receive a similar error after populating the dynamic field with a string whether or not it's in the proper format for an Apex date/datetime field

Relevant screenshots

Screenshot from 2020-02-11 12-33-27 Screenshot from 2020-02-11 15-46-06

bennmcgregor commented 4 years ago

This has been addressed in this PR: https://github.com/elasticio/salesforce-component/pull/109

stas-fomenko commented 4 years ago

~~@bennmcgregor~~ ~~Not sure if LookupObjects ( at most 1 ) doesn't work for date or datetime field types bug fix works correctly, I'm still getting the same error for the following input:~~ UPD: the wrong branch was taken

elasticio / salesforce-component