Rick_Segura1

Level 2

Joined the community 18-09-2019

Level 2

Badges

Accepted Solutions

View leaderboards

Filter by user contributions

Re: Compute Formula execution issues

by Rick_Segura1 11-02-2023

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}}')

Discussions

1272 0 0
Re: Compute Formula execution issues

by Rick_Segura1 11-02-2023

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 install of Compute Formula is not accepting what seems to be a valid token such as:PROPER({{lead.Billing Country}})This pro...

Discussions

1274 0 1
Compute Formula execution issues

by Rick_Segura1 11-02-2023

I installed the Compute Formula service per this user guide all initially looked well, until I attempted to execute an AIO Compute Formula step. I set up a few string fields as input fields for the service, but no matter how simple of formula I supply, when the AIO Compute Formula step executes, it...

Discussions

1285 0 2
Re: Custom Object Field Limit - Changed?

by Rick_Segura1 10-20-2021

Many thanks, @Michael_Florin . This is the kind of news I was hoping to hear. I'm having my folks reach out to support.

Discussions

2574 0 1
Custom Object Field Limit - Changed?

by Rick_Segura1 10-20-2021

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 an instance, but with the option to increase the limit up to 10. Along with this change, is there also now an option ...

Discussions

2589 0 4
Re: Lead Dedupe Rules and BULK REST API (Import) Lookup Field

by Rick_Segura1 05-28-2021

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 store a GUID generated outside of Marketo. This "GUID" field is passed as the lookupField parameter value.

Discussions

3992 0 0
Re: Lead Dedupe Rules and BULK REST API (Import) Lookup Field

by Rick_Segura1 03-24-2021

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 compound dedupe key.

Discussions

4136 0 1
Re: Lead Dedupe Rules and BULK REST API (Import) Lookup Field

by Rick_Segura1 03-24-2021

...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 Lead database? Basically, I'm trying to determine if making the compound dedupe key request to support is worth the eff...

Discussions

4141 0 3
Re: Lead Dedupe Rules and BULK REST API (Import) Lookup Field

by Rick_Segura1 03-24-2021

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 (UI), form fills and the API separately. Thanks,Rick

Discussions

4144 0 4
Lead Dedupe Rules and BULK REST API (Import) Lookup Field

by Rick_Segura1 03-24-2021

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 have any impact on the import process? For example, let's say for the API that we set up email address and UserType (th...

Discussions

4157 0 6

API BULK Lead Import dedupe rules Lookup field