Known Issues · Salesforce to Salesforce
After Spring'19, Salesforce Standard User receives the "Insufficient Privileges" error when stopping an External Sharing in Salesforce to Salesforce. If they have "View Setup and Configuration" permission, they can stop it.
Scheduled - Spring '20 ·Reported By 2 ·Updated 19 days ago
When using cross org connect and trying to access External Object record in lightning OR trying to run a SOQL on the external object filtering on Id, gives an Internal Salesforce Error.
Scheduled - Spring '20 ·Reported By 3 ·Updated 2019-10-07
Salesforce to Salesforce will show a communication error when clicking on the "Subscribe/Unsubscribe" button.
Fixed - Winter '19 ·Reported By 11 ·Updated 2018-10-13
When certain start and end dates are used on a quote containing Yearly MDQ products, there will be an extra segment with small or zero price.
No Fix ·Reported By 0 ·Updated 2018-05-30
Class implementing SandboxPostCopy executes on create of sandbox but not refresh. Unexpected exception in queue processing is found. An additional aspect of this issue: If the source of a sandbox is changed on refresh, a sandbox completion email will not be sent.
Fixed - Summer '18 Patch 3.0 ·Reported By 5 ·Updated 2018-05-05
In orgs with many roles not all contacts associated to an account are sent through the salesforce to salesforce connection.
No Fix ·Reported By 4 ·Updated 2018-04-14
Time Limit Exceeded when adding Salesforce-to-Salesforce Connection to existing Queue
No Fix ·Reported By 2 ·Updated 2018-04-14
Converting the source for projects containing Joined Reports seems to drop the XML namespace within reports with joinTables, resulting in the error "Error parsing file: The prefix "xsi" for attribute "xsi:nil" associated with an element type "blockId" is not bound"
Fixed ·Reported By 4 ·Updated 2018-04-02
When you are trying to do Org Sync to sync metadata, the process will fail with IndexOutOfBoundsException error
No Fix ·Reported By 0 ·Updated 2017-11-20
In Salesforce to Salesforce sharing, if a record is inserted/updated and then immediately updated again, the second update may not be sent to the partner who shares the record with you. This rare issue is caused by the way the core messaging queue works. There is a small window of time when the first...
No Fix ·Reported By 28 ·Updated 2017-06-27
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.