Salesforce to Salesforce - Publish but not Subscribe?

[cjhouse13]

Hi all,

I'm curious if anyone else has run into this and how you've approached it.

We currently have two instances of Salesforce (acquisition).  Rather than try to merge the two databases together we're looking at Salesforce to Salesforce as a way to leverage the two systems and not overlap our efforts.  We have set up leads in the Publish / Subscribe model and that is working very well.

Now we want to set it up so that the two instances can share their customer lists (one is US one is EU - so it is possible that they are working the account in the EU but we have already sold to them in the US and we could leverage the knowledge of the US to help win the EU).  However, I don't want the EU to be able to update the Account Records for the US and vice versa.  It is my understanding (I've tried this, and also have spoken to Salesforce PS) that you can not just Publish account data and not Subscribe to the other's account data if you still want them to be able to send you accounts.  And, you can't set up two connections with the same system.

That being said, has anyone else found a similar business need, and if so what have you done to circumvent?  (record types, custom fields, etc?).

Thanks in advance,

Courtney

[adi kuruganti · Accepted solution]

 if the requirement is that either instance may forward the account record but once a record is forwarded you don't want any updates back from the target, then your best option is to use a simple apex trigger. I know customers with similar use cases that have done just that. All you need to do is write a before update trigger that will ignore updates from the 'Connection User' if the record is in 'Sent' status. What this will do is allow either instance to forward the record, allow the target to accept the record and allow the source to send updates to the target. However this will prevent the source from receiving updates from the target despite 'subscribing' to updates. If you don't want to receive any updates, whether source or target, then make the criteria less stringent - just check if the update is being done by the 'connection user' without checking the sent/received status. If you have specific questions on how to do this send you questions to: s2s@salesforce.com and we can take this offline