How to create a Lead with Custom id | Community
Skip to main content
A
Anonymous
September 18, 2013
Solved

How to create a Lead with Custom id

  • September 18, 2013
  • 5 replies
  • 1387 views
I would like to use one of my custom SFDC field as foreignSysPersonId  for creating/updating leads.
say SFDC field name is "Domain_Name__c"  which stores domain name for a customer.

A customer can register any number of domains with same email id, hence domain name is the only suitable candidate for uniquely identifying the leads.

I am setting doing following in my java code -

leadRecod.setForeignSysType(ForeignSysType.CUSTOM);
leadRecord.setForeignSysPersonId("anyDomainName");

this lead gets created . next time when I create another lead with same email id and different domain name the old lead gets updated.

leadRecod.setForeignSysType(ForeignSysType.CUSTOM);
leadRecord.setForeignSysPersonId("SecondDomainName");

I am passing email as set of attributes while creating a new lead record.
attrs.put("Email" , "dx@xx.com");

looks like email is still taking precedence over ForeignSysPersonId.  Am I doing anything wrong here ?


This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by
<ForeignSysPersonId> </ForeignSysPersonId>
and
<ForeignSysType> </ForeignSysType>

The choices for ForeignSysType are:
<xs:enumeration value="CUSTOM"/>
<xs:enumeration value="SFDC"/>
<xs:enumeration value="NETSUITE"/>

The Marketo Id takes precedence over all other keys. If both ForeignSysPersonId and the Marketo Id are present in the lead record, then the Marketo Id will take precedence and the ForeignSysPersonId will be updated for that lead. If the only ForeignSysPersonId is given, then it will be used as a unique identifier.

5 replies

A
Anonymous
Accepted solution
September 18, 2013
<ForeignSysPersonId> </ForeignSysPersonId>
and
<ForeignSysType> </ForeignSysType>

The choices for ForeignSysType are:
<xs:enumeration value="CUSTOM"/>
<xs:enumeration value="SFDC"/>
<xs:enumeration value="NETSUITE"/>

The Marketo Id takes precedence over all other keys. If both ForeignSysPersonId and the Marketo Id are present in the lead record, then the Marketo Id will take precedence and the ForeignSysPersonId will be updated for that lead. If the only ForeignSysPersonId is given, then it will be used as a unique identifier.

A
Anonymous
September 18, 2013
Can you tell me what does these various options  mean ?

<xs:enumeration value="CUSTOM"/>
<xs:enumeration value="SFDC"/>
<xs:enumeration value="NETSUITE"/>
A
Anonymous
September 18, 2013
CUSTOM, SFDC and NETSUITE are the values for <ForeignSysType> such as

<ForeignSysType>CUSTOM</ForeignSysType>


A
Anonymous
September 18, 2013
I wanted to ask what CUSTOM, SFDC,NETSUITE ForeignSysType relate to?  If i understand it correctly then -

1. CUSTOM -  any custom id that we want to specify as ForeignSysPersonId
2. SFDC  - SFDC Lead id will be used as ForeignSysPersonId
3. NETSUITE  - No idea
A
Anonymous
September 19, 2013
Netsuite provides cloud infrastructure to allow businesses running business management applications in the cloud. It is also an ERP, CRM and eCommerce vendor.

In the Marketo SOAP API context it primarily enables integration between NetSuite account, Marketo Lead Management and 3rd party systems.


Terms & ConditionsAccessibility statement

Loading footer...