I figured it out. Since I am passing a string token to the function, I need to surround the token with single quotes:
PROPER('{{lead.Billing Country}}')
After a good night's rest, I changed up my testing tactic and supplied a literal value to the formula as such:
PROPER('us')
The produced the value of 'Us' correctly.
However, our ...
I installed the Compute Formula service per this user guideall initially looked well, until I attempted to execute an AIO Compute Formula step. I set up a few string fields as inpu...
I've noticed that 10 Custom Objects is no longer the standard limit for all instances. 10 may be still be a global hard limit, but I've seen contracts where the limit is 2 CDOs for...
Confirmed. The use of the lookupField query parameter for the BULK lead import call overrides the Lead Dedupe field rules.
In our solution, we ended up creating a custom field to ...
Ok, it looks like it's something we'll need to test out to confirm.
It would be nice if the API would accommodate multiple lookupField values to support cases where we have a comp...
...and in such a case, how would the example file be processed if email address is selected as the lookupField in the BULK Import call? Will it result in one or two records in the ...
Hi, Sanford.
I'm saying that we did (or will) have support apply the compound dedupe key for upserts using the API. I believe we can apply such rules (dedupe key) for list imports...
In the case where we have a setup with dedupe fields on the Lead object for the API and we're using the BULK API to import Leads, does the the lookupField parameter of the endpoint...