You are here:
Guidelines for Using Salesforce to Salesforce
Review some guidelines for using Salesforce to Salesforce.
Required Editions
| Available in: Salesforce Classic (not available in all orgs) |
Available in: Contact Manager, Group, Professional, Enterprise, Performance, Unlimited, and Developer Editions Workflow is available in: Enterprise, Performance, Unlimited, and Developer Editions |
Important Salesforce to
Salesforce is scheduled for retirement as of Spring ’27. See Salesforce to Salesforce Retirement.
- Salesforce admins can share all records, but most users can only forward records that they or their subordinates own.
- You can stop sharing a related record from its parent record. Select the parent record. In the related list of the record you want to stop sharing, click Manage Connections in the Sent Connection Name column. Then, select the connections that you want to stop sharing within the Selected Connections list. Use the arrows to move the connections to the Available Connections list. Save your changes.
- To stop sharing a record, view the record and click Stop Sharing in the External Sharing related list. You can only stop sharing records that you or your subordinates own. When you stop sharing the record with a connection, changes to the record in your org aren’t reflected on the record in the connection's org. The shared record isn’t deleted from the other org.
- To stop sharing a case comment or attachment, you must make the records private.
- An opportunity product is related to both opportunity and product records. For this
reason, it can only be shared as a child record of a shared opportunity, provided the
associated product is also shared. If all of these criteria are met, opportunity products
are automatically shared with connections.
- The Opportunity Product object type is published to your connection, and your connection has subscribed to the object.
- The opportunity and the product associated with the opportunity product are shared with your connection.
- In the connection's org, the opportunity is associated with an active price book during acceptance.
- In the connection's org, the product is associated with the same active price book as the opportunity.
- In the connection's org, the product is active.
- In both orgs, the opportunity currency is the same.
- You can share a case comment as a child record of a case. The connection automatically
accepts case comments, providing these criteria are met.
- The Case Comment object type is published to your connection, and your connection has subscribed to the object.
- The case to which the case comment is associated is shared with the connection.
- The case comment isn’t marked Private.
- If an error occurs when accepting a record, see the Connection History for details.
- If a related record is edited from an unshared record, the related record is no longer shared with a connection.
- A maximum of 100 tasks per related record can be shared. This maximum includes open and closed tasks.
- After accepting a shared record, if you update a field that your business partner has subscribed to, the field is automatically updated on the record in your business partner's org. Likewise, if your business partner updates a field to which you’ve subscribed, it’s automatically updated in your org. When your business partner updates the record, the Last Updated By field is set to Connection User.
- When your business partner shares child records at a later time using the Manage Connections link in the related list of a record you've already accepted, the child records can be automatically added to your organization.
- Currently, if you edit the stage of multiple opportunity records by performing a global find and replace, that change isn’t reflected in orgs that you had forwarded the records to in Salesforce to Salesforce. For example, suppose you perform a global find and replace that causes the stage of all inactive opportunities to change from Inactive to In Review. If any of the affected opportunities had been forwarded to a business partner in Salesforce to Salesforce, those opportunities are still in the Inactive stage in your partner's org. For the stage change to be reflected in their org, they must open each affected opportunity, click Edit, and click Save.
- When you convert a lead, Salesforce to Salesforce inactivates the shared record and updates the External Sharing related list in your connection's lead record with an Inactive (converted) status. Due to inactivation of the shared record, changes to the Lead Status during conversion aren't reflected in your connection's lead record.
- After you accept a record, you can make it available to other connections in the same way that you can make any record available using Salesforce to Salesforce. In this way, you can work in a multi-tiered business network. In a multi-tiered network, changes made to the shared record in any org updates the information in all the orgs that are sharing the record.
- Because updates to shared records are processed asynchronously and retried if a sync fails, they don't appear in the connected org right away.
- If your connection continually syncs shared records between Salesforce orgs, you can encounter errors.
- Changes to the Last Modified Date field trigger a sync, even if no other field values change.
- When sharing opportunity products, keep these additional rules in mind.
- If quantity or revenue schedules are enabled in the connection's org, the Quantity and Sales Price fields aren't updated in their org.
- If the price book related to the opportunity product is changed or deleted in one org, the opportunity product is no longer shared.
- If the opportunity is no longer shared, the opportunity product is no longer shared.
- If you're expecting to receive large volumes of records from a connection, enable Auto-Accept for the appropriate objects. For example, if a connection shares a large number of leads with your org on a regular basis, select Auto-Accept next to Opportunity on the Add or Remove Subscribed Objects page.
- To see changes made by a connection, enable field tracking on the object and add the history related list to page layouts. Another option is to create a custom history report that includes the Received Connection Name field.
- To automatically assign all incoming leads or cases to a specific
user, create an assignment rule that includes these rule entries.
- Received Connection Name contains name of connection
- Created By contains Connection User
- If you want to assign a case to a connection using an escalation
rule on the case, you must assign the case to a queue where the connection is a member.
For example, say you have a connection that acts as your third-party service agency. To
escalate all cases that meet certain criteria to this connection, you must:
- Create a queue that contains the connection as a member.
- Create an escalation rule with the appropriate criteria.
- Add an escalation action that automatically assigns cases meeting the specified criteria to that queue
Did this article solve your issue?
Let us know so we can improve!
