You are here:
Prepare Legacy Partner Connect Objects for Connected External Records
To let your users see and track the progress of shared leads and opportunities, you can opt to store a read-only version of the other org’s record in your own org. The Connected External Lead and Connected External Opportunity objects store these read-only records. Learn how vendor and partner admins can prepare the connected external objects to make sure they're ready to save the read-only records for Partner Connect.
Required Editions
| User Permissions Needed | |
|---|---|
| To set up Partner Connect in the vendor org: | Customize Application |
| To set up Partner Connect in the partner org: | Customize Application AND Set Up Partner Connect for a Partner Org |
Before you prepare the connected external objects for storing records, we recommend that vendors and partners review their field mapping plans together. Doing so lets you know for which fields you’re sending and receiving updates and the field types required to save the updates locally.
Vendor admins decide whether record updates are sent and received between vendor and partner orgs when they set up Partner Connect. Vendors can opt to send and receive updates on up to 10 fields for each object that they integrate with a partner.
Then, to give users access to their peers’ record updates, vendor and partner admins must create fields to store the read-only data on the connected external objects.
- From Setup, in the Quick Find Box, enter Partner Connect. Vendor admins select Partner Connect for Vendors. Partner admins select Partner Connect.
- Create fields on the connected external objects for storing each field that you want users
to see from your org.
- Under Configure, find the section for preparing objects for record storage. If you’re storing updates on any Lead fields, go to the object manager for Connected External Lead. If you’re storing updates on any Opportunity fields, go to the object manager for Connected External Opportunity.
- From the Object Manager, create a field on the connected external object for every field
that you’re planning to store for your users. Each connected external field that you create
must have the same field type as the integrated vendor field and partner field it's storing.
Important Field names for external connected fields can be different from both the vendor and partner org's Lead and Opportunity field names.If you create any connected external fields that are picklists, we recommend deselecting the Restrict picklist to the values defined in the value set setting. Or, if you want to restrict picklist values for the connected external field, the values must exactly match the Opportunity or Lead picklist values that represent the same data from your own org. Otherwise, Partner Connect can't save the picklist value from the other org to the connected external record.
- Repeat steps 2a and 2b for every integrated object for which you're sharing updates that you want to store locally.
To store the standard opportunity field Stage, you must create a field to store that data on the Connected External Opportunity object. Say the other company uses the field name Status for that field. You can name the Connected External Opportunity field Stage, Status, or something else entirely. But the connected external field type must be Picklist. Deselect the Restrict picklist to the values defined in the value set setting, unless you want to create a connected external picklist value to exactly match each of your Opportunity Stage picklist values.
After vendors and partners finish preparing their connected external objects, they’re ready to connect orgs.
