Issue with SOQL Variable Handling in Salesforce Query Calls | Clay

Issue with SOQL Variable Handling in Salesforce Query Calls

Hi Clay S., We're having an issue in using Salesforce SOQL, Here is the table. The thing is we're trying to make a call for each row using SOQL in Salesforce but it seems it does not read the {{variable}} in the SOQL itself. But when we try hard coding the SOQL itself it will then proceed. Hope you could help us on this one! ❤️

14 comments

Channeled
APP
·
·
It looks like you're experiencing an issue with variable interpolation in your SOQL query. This is likely a syntax issue with how the variables are being formatted in the query. When using variables in Clay's Salesforce SOQL action, you need to ensure proper formatting. The most common cause of this issue is that the variable tags aren't being properly parsed before the query is sent to Salesforce. Try these solutions: 1. Make sure all your data is updated before running the SOQL query 2. For dynamic values in SOQL queries, create a formula column that properly formats your variable for SOQL first, then reference that column in your query 3. Check for any hidden characters or syntax errors in your query Could you share your exact SOQL query with the variables so I can help troubleshoot further?
Sources: HTTP API integration overview | Documentation | Clay University Salesforce integration overview | Documentation | Clay University
Mark L.
·
·
Hey Christopher, thanks for raising this. I think I see the issue that's happening. When using the {{Field_Name}} variables, Clay automatically includes them in quotes, as 'Value Inserted'. The problem that's creating is that. in LIKE clauses, the % symbol remains outside the quotes. I'm going to raise this to our engineers to review. This is likely and unintended side effect of other changes, and in any case, it does make things harder for you. I'll report back what I learn.
1
Christopher O.
·
·
Thank you very much! ❤️
Christopher O.
·
·
Hi Mark L., Just want to check in how can we move forward? ❤️
Daniela D.
·
·
Hey Christopher! Apologies for the delay. The team is working on a fix for this. For context, the integration does not currently support the %/_ operators. The update we’re working on will address this, and we’re aiming to release it by the end of this week. We’ll follow up here as soon as it’s deployed. Really appreciate your patience🙏🏾.
Christopher O.
·
·
Thank you very much for this info! It really help us alot. We also tried on our end to "escape" those single quotations. But its difficult on our part to debug when we actually don't know what's happening on the backend. But hey~ Thank you very much for this at least I can follow you up on this by EOW ❤️
❤️1
Daniela D.
·
·
Happy to help!
1
❤️1
Christopher O.
·
·
Hi Daniela D.. Good day to you! I hope you had a great day today! Just want to followup on the status of this request. ❤️ Is it feasible for this to be resolved today or early next week?
Daniela D.
·
·
Hey Christopher! Thanks for the message✨. I just followed up with the team. We'll get back with an update before EOD🙏🏾.
Daniela D.
·
·
Hey Christopher! Thanks for your patience. The team rolled back the action to the previous version to accommodate this format. You should now be able to run the integration with the %/_ operators. Let us know if you run into any issues.
Christopher O.
·
·
Hi Daniela D., Thank you for awesome work! ❤️ But can I get another help. I tried using this query and its not working, maybe you can help me a bit more 🙂
Bo (.
·
·
Hey,
It looks like you’re still referencing the previous query—we’ve since removed that and are now using the updated version. Let me know if you can find it! :)
(67 kB)
❤️1
Christopher O.
·
·
thank you Bo! will surely try this! ❤️
Channeled
APP
·
·