Forum Discussion
Hey @Henchway,
Try adding a mapper in front of the SQL Execute, and map all of the configuration fields in there. Than you can simply use those fields in the query itself without using expressions. So you can understand me better, here’s your query transformed in the way I’m suggesting:
SELECT $salesforceGPDeliveryNumberField,$salesforceGPOperationsNumberField,Id FROM Opportunity WHERE $salesforceOpportunityIdField = $opportunityId
Regards,
Bojan
Could you elaborate this one a bit?
When i specify this in a mapper beforehand, i could only do it in a non-expression field, therefore plaintext only. I’m putting this in a variable ‘query’, of course then it’s solely text.
When using this in a REST GET snap , it won’t evaluate the lib piece, but simply fail with http 400. I suppose the difference here could be that you’re strictly referring to a SQL Snap, but i’m sending the SQL statement via REST to Salesforce.
When activating the expression evaluation in the mapper, it fails as it won’t recognize e.g. ‘SELECT’ as a proper command.
Best regards
Thomas- alex_panganiban4 years agoContributor
It seems like you need to encapsulate the static portions of your expression in quotation marks, and then concatenate your lib expression by turning on the equal sign toggle button to the left of your expression. Anything that needs to be evaluated should not be surrounded by quotation marks. In the end, your element called, $query, should contain a valid SQL statement. It should look something like this.
Related Content
- 2 years ago
- 2 years ago
- 11 months ago
- 2 years ago