Legacy Partner Connect Considerations

Review considerations about Partner Connect support and setup.

• Partner Connect can support record integration with multiple companies. Each org can establish up to 50 connections as a vendor, and up to 50 connections as a partner. But the same two orgs can’t establish multiple connections between them, even if you play a different role in each connection. For example, if you establish a connection as the vendor, you can’t establish a second connection with the same org in which you play the partner.
• Sometimes you’re required to adjust your object and field settings to prepare objects for integration across orgs. To make sure you’re able to make any required adjustments, review the setup prerequisites.
• During setup, vendors select the objects and fields that they want to map with their partner’s org. Then Salesforce sends an email for each proposed object mapping to the partner admin, asking them to respond with their own object and field mappings. Each email contains a JSON script that a partner must import into Setup to view the vendor’s proposal.
  • If the partner admin can’t locate their field-mapping email from Salesforce, the vendor admin can resend the email. Vendor admins can go to their previously saved mappings and select Email Field Mapping from the actions dropdown menu.
  • To locate emails, partners can search for emails with “Partner Connect” in the subject.
  • Vendor admins can edit their fields selected for integration to share additional fields or reduce the fields they’re sharing. But the partner org doesn’t get exports or updates for newly added fields until the partner admin revisits Setup and gets the vendor’s latest mappings. To get the latest mappings, partner admins can update the JSON for that object and then map any additional fields
• Vendor org users can’t export records from the vendor’s partner site to the partner org. Only partner users can export records.
• Each record can be imported to the partner’s org one time only. If partner users attempt to export a record again, that export is skipped. To see which records have been previously exported, partner users can add the Export Status field to their Lead and Opportunity list views, but vendor admins must give them the permission to do so. See Give Partner Users Permission to Use Partner Connect
• After exporting records, a partner user sees a message confirming whether the export attempt was successful. But even successful exports can result in unsuccessful imports to the partner org. Partner Connect sends an email that lists the number of successful, unsuccessful, or skipped imports to the last partner admin who saved the field mappings in the partner org. Admins in either org can prepare a Partner Connect status report to observe export and import issues and evaluate next steps for troubleshooting persistent issues.