--- schema_version: "1" id: d9caa333966c05e52af798ec5a78017ebe46be22d2d8d4ff880d925a1e0f8560 title: Map Your Preferred Objects and Fields to Your Vendor’s Org collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/slack/264-0-0/prm_pc_prm_pc_setup_partner_map.md canonical_url: https://help.salesforce.com/s/articleView?id=slack.prm_pc_prm_pc_setup_partner_map.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: a8d6ca0edb0864d4621d4e4a3eb97fdff39785a7b881406ef00f0cbfb17bc40f description: After your vendor selects their object and field mappings, you get an email for each object. The emails instruct you on how to complete your mappings. First we guide you through importing your vendor’s object and field selections. Then you select a default user to assign to imported records. Lastly, you select the fields that you want to map to your vendor’s fields. If your vendor elected to send and receive field updates across orgs, you must also review storage options. products: - Sales - Slack - Cross Cloud release: "264" --- # Map Your Preferred Objects and Fields to Your Vendor’s Org After your vendor selects their object and field mappings, you get an email for each object. The emails instruct you on how to complete your mappings. First we guide you through importing your vendor’s object and field selections. Then you select a default user to assign to imported records. Lastly, you select the fields that you want to map to your vendor’s fields. If your vendor elected to send and receive field updates across orgs, you must also review storage options. ### Required Editions
User Permissions Needed
To map objects and fields in the partner org:

Customize Application

AND

Set Up Partner Connect for a Partner Org
Before mapping objects and fields, verify that you’ve planned for mapping objects and fields with your vendor admin and managed your required fields. If your vendor admin elected to send and receive updates for any fields, you must also create the necessary fields to store updates on Connected External Lead and Opportunity. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-slack-salesforce_prm-264-0-0-production-enus/35cdbed0-3c5d-4ddb-94ea-c7445aa90b95/images/icon_note.png) Note The Account Name and Primary Campaign Source lookup fields on the Opportunity object are exceptions. A vendor can propose these fields for integration, but a partner can see only the name of the referenced field. These lookup fields don’t support sending or receiving updates. 1. Check your email for a message or two from Salesforce that says your vendor is ready to map fields. You get a separate email for each object that your vendor wants to integrate. 2. From Setup, in the Quick Find box, enter Integrations, and then select **Partner Connect**. 3. Under Connect, find the vendor company connection that you added. From the Map Objects and Fields to Your Vendor’s Org step, click **Map Objects & Fields**. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-slack-salesforce_prm-264-0-0-production-enus/35cdbed0-3c5d-4ddb-94ea-c7445aa90b95/images/icon_note.png) Note To edit mappings for an object that was previously mapped, select **Edit** from the actions dropdown menu. 4. Select an object that you want to map to one of the objects the vendor proposed to integrate. Then click **Next**. 5. Get your vendor’s proposed mappings. Paste the JSON script from the email that you received from Salesforce into the JSON Script field and click **Next**. 6. Select a default user to whom all imported records for this object are automatically assigned as the owner. Then click **Next**. Select a person who’s responsible for triaging and assigning work. Or create a user to act as a placeholder owner until a user who’s a real person can be assigned. The default user must have Read and Write access to the object you’re mapping. 7. Select the fields that you want to integrate with your vendor’s fields. You must map all required fields to the required field of a vendor. See [Partner Connect Object and Field Integration Considerations for Partners](https://help.salesforce.com/s/articleView?id=slack.prm_pc_setup_partner_manage_req_fields.htm&release=264.0.0&type=5 "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. In some cases, 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 every field they want to share, and verify that your selections meet the mapping requirements."). You’re required to map only the fields that you want to. Mapping a field results in the vendor’s field data being exported to your org when a partner exports a record. If the vendor elected to send and receive updates for that field, mapping it also lets partner data updates on the field flow to the vendor org. Likewise, vendor data updates for the field flow to your org. Updates from the vendor’s org are saved in your org on the Connected External Lead or Opportunity object. 8. For each field in which you want to store your vendor’s field data updates, select the **Store Vendor Updates** checkbox. If the checkbox isn’t available for a field, your vendor didn’t elect to send and receive updates for this field between orgs. 9. For each field that you want to store, select a corresponding field from the connected external object where you want to store this field data locally. Then click **Save**. The last partner admin who saves the field mappings in the partner org gets an email after a partner user exports a selection of records. The email lists the number of successful, unsuccessful, and skipped imports. 10. To integrate another object, click **Map Objects & Fields** from the vendor connection and repeat steps 4 to 9. Salesforce doesn’t notify your vendor admin when you’re done mapping fields, so we recommend confirming when you’re finished. Partner users can’t export records from your vendor site until all vendor and partner setup steps are complete. Check in with the vendor admin to see if they’re ready to roll out Partner Connect to users. #### See Also - [Prepare Legacy Partner Connect Objects for Connected External Records](https://help.salesforce.com/s/articleView?id=slack.prm_pc_setup_prepare_cnnctd_extl_objects.htm&release=264.0.0&type=5 "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.") - [Planning Object and Field Integration for Legacy Partner Connect](https://help.salesforce.com/s/articleView?id=slack.prm_pc_setup_prereq_mapping_plan.htm&release=264.0.0&type=5 "To avoid revisiting your Partner Connect setup, we recommend that vendors and partners meet to agree on a clear plan for integrating objects and fields across Salesforce orgs. Vendor admins kick off planning by creating a list of the items they want to integrate into the partner’s org. Sometimes admins from either org are required to customize their Lead or Opportunity objects to integrate records smoothly.") - [How Legacy Partner Connect Exports, Imports, and Integrates Records Across Orgs](https://help.salesforce.com/s/articleView?id=slack.prm_pc_overview_how_biz_tracked.htm&release=264.0.0&type=5 "Learn about how Partner Connect lets vendors and partners work on shared leads and opportunities independently while still providing cross-org visibility into how each record is progressing.")