Partner Connect Object and Field Integration Considerations for Vendor

• Verify that the vendor org has a partner account that represents the partner company.
• Verify that the vendor org has a partner user who represents the partner admin and can access the vendor’s Experience Cloud partner site. The partner user must be added as a related contact on the partner account that represents the partner company.
• Verify that the vendor org includes a partner user for each user whom the vendor wants to export records.
• Share the objects and fields you plan to integrate, along with the integration details with your partner admin. Adjust objects, fields, or settings as needed to accommodate data storage differences between Salesforce orgs.
• For the fields you share, indicate these details.
• • If not obvious, a description of how you use the field
  • Required fields
  • Field types. Not all field types are available for mapping. See Partner Connect Limits and Limitations.
  • For picklist fields, the picklist options that you provide for users to select
  • For currency fields, the type of currency
  • The fields for which you plan to send and receive updates across Salesforce orgs. You can send and receive updates on up to 10 fields per object. Vendors choose fields for update on behalf of both companies.

After sharing your plan, wait to hear back from your partner admin on how your objects and fields map to their own. Be prepared to coordinate on a plan for adjusting objects, fields, or customizing other settings to accommodate discrepancies. Don’t forget to train your users on any process changes so that your users are aware of how you plan to track data.