To avoid revisiting the Partner Connect setup, we recommend that vendors and partners
agree on a clear plan to integrate objects and fields across Salesforce orgs. Vendor admins kick
off planning by creating a list of the items that they want to integrate into the partner’s org.
Sometimes admins from either org need to customize their Lead or Opportunity objects to
integrate records smoothly.
Required Editions
Available in: Lightning Experience
Available in: Enterprise, Performance, and Unlimited
Editions in Agentforce for Sales with Partner Ecosystem Management - Members, Partner
Ecosystem Management - Login and PRM add-on license. Partners aren’t required
to purchase any licenses to use Partner Connect.
Partner Connect Object and Field Integration Considerations for Vendor Share key details about your object and field integration with your partner admin. Sometimes you must adjust objects, fields, or customize other settings to accommodate discrepancies in how each Salesforce org stores data.
Partner Connect Object and Field Integration Considerations for Partners Review your vendor’s plan for integrating objects and fields. Then decide how you want to map your objects and fields to your vendor’s selections. Sometimes, you can decide not to import or store fields that you don’t want, even if your vendor opted to share them. To import data into your Salesforce org successfully, make sure that you understand how your vendor uses each shared field. And verify that your selections meet the mapping requirements.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.