Legacy Partner Connect Object and Field Integration Considerations for Partners

Map All Your Required Fields to a Required Field in the Vendor's Org

Make sure that all required fields on your object are mapped to a field on the vendor’s side that is also required. Otherwise, records can’t be saved and the import fails.

In many cases, vendors and partners have the same required fields, and you can simply map each together. But if you introduced custom required fields and your vendor hasn’t shared logical matches, consider these options. 

• Set default values for required fields on your Lead and Opportunity objects so a placeholder value is available if no vendor data is imported. Default values aren’t available for all required fields but are available for custom fields and standard picklists. If the vendor record provides a value, the default value you set is overwritten. Default values are supplied when all records are created, even manually by users. But users can update the default value later. See Define Default Field Values.
• Create an auto-launched Flow that makes before-save updates to populated required fields on imported records. See Record Triggers for Flows that Make Before-Save Updates.
• Ask your vendor to share a field with similar data or to create one to represent it. The vendor must set a default value for the field in their org or make the field required.

If one of your vendor’s required fields isn’t required in your org, you aren’t required to map it.

Compare Field Types with Your Vendor

• Mapped fields must have the same field type. If the field you use to track something is a different field type than your vendor’s, consider creating a field on your object to receive the vendor’s data. Or choose not to import that field from your vendor. 
• If your vendor proposed any fields of the field type Picklist, verify that you have similar picklist options to select in your org. If you don’t, create them. 
• If your vendor proposed any fields of the field type Currency, make sure that both orgs are using the same currency or currencies for those objects. See Manage Multiple Currencies.
• If a vendor proposed the Account Name and Primary Campaign Source lookup fields on the Opportunity object, you can import only the name of the referenced field.

Compare Data Tracking Processes with Your Vendor

Review your vendor’s fields and field descriptions. Confirm that you and your vendor agree on the information that you expect to track with each field that you’re integrating. Don’t forget to train your users on any data tracking process changes.

Take Note of the Fields that Trigger Updates Across Orgs

Vendors choose whether updates for integrated fields are sent and received between orgs.

Note The Account Name and Primary Campaign Source lookup fields on the vendor’s Opportunity object don’t support sending or receiving updates.

If you want to store the read-only updates sent from the vendor, you must configure storage for each field the vendor selects on the Connected External Lead or Connected External Opportunity objects. But even if you don't want to store the vendor's field data, your org's field data is still shared with the vendor.

Select a Default Assignee for Imported Records

When mapping fields, you must select a default user in your org to whom all imported records are assigned. Select a user who’s responsible for triaging and assigning work. Or create a nonhuman placeholder user to act as owner until a real person can be assigned. You can choose different default users for each object. The default user must have Read and Write permissions to the object that it’s responsible for.