Quote:
Originally Posted by ambiguator
This thread has been my primary resource for outbound messaging via SalesForce. Thanks for all the great input.
My client has 2 primary means of accessing their SalesForce data:
1. Through the web at login.salesforce.com, na2.salesforce.com, etc. using SF's snazzy Ajax interface.
2. Through a custom CMS web app designed to talk to salesforce through the web service API.
My question is: apart from having 2 different logins, how do I tell the 2 kinds of requests apart?
Let's take this scenario: I modify the Contact object through the CMS (case 2 above). This forces the CMS to push the changes to the salesforce database. I have an outbound message being triggered for all changes to a Contact object. The outbound message gets triggered and notifies the CMS that the Contact object has changed, even though the CMS initiated the change in the first place.
How do I keep salesforce from generating the outbound message when it was triggered by an event via a webservice API call?
Thanks in advance,
/a
|
When you create an outbound message, you can set who you want to send the outbound message as, a user id, like me (see the attached picture)
Maybe you could use 2 different users to send as, thus two different identifications that you can use to differentiate the two outbound messages.
I did not know that you could kick off a outbound message via an API call, but you can limit it to only being called once!
when you set the Work Flow rule, there is a section:
Evaluate rule How do I choose?
- When a record is created, or when a record is edited and did not previously meet the rule criteria (choose this one)
- Only when a record is created
- Every time a record is created or edited
Hope that helps sir and I hope that I understood your question(s)
If Not then do let me know