• Cliff Gilley
  • NEWBIE
  • 0 Points
  • Member since 2015

  • Chatter
    Feed
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 1
    Questions
  • 2
    Replies
We're in the process of building workflow integration with Salesforce, but one of the key asks from our stakeholders is the ability to trigger a conversion event from leads to opportunities.  This functionality is available through the SOAP API but not the REST API, which we would prefer to use in order to re-use existing technology that we have.  Is there any plan to update the REST API to include this and other features offered by the SOAP API?

We're trying to create an OAuth-based solution that is generically applicable to our various clients, based on an unattended workflow process.  We need to be able to programmatically convert the entity and move on to the next step.  As noted, this capability exists in the SOAP API, but not the REST API; we'd rather not have to deal with WSDL and other SOAP overhead, as we have an existing REST infrastructure that we'd prefer to re-use.
I have a connected app in one sandbox with the client id/secret. The same clientid/secret is working when connecting to another sandbox. Are connected apps shared? if that's the case, should i not create them in every sandbox? and why is that. Any help would be appreciated.
We're in the process of building workflow integration with Salesforce, but one of the key asks from our stakeholders is the ability to trigger a conversion event from leads to opportunities.  This functionality is available through the SOAP API but not the REST API, which we would prefer to use in order to re-use existing technology that we have.  Is there any plan to update the REST API to include this and other features offered by the SOAP API?

We're trying to create an OAuth-based solution that is generically applicable to our various clients, based on an unattended workflow process.  We need to be able to programmatically convert the entity and move on to the next step.  As noted, this capability exists in the SOAP API, but not the REST API; we'd rather not have to deal with WSDL and other SOAP overhead, as we have an existing REST infrastructure that we'd prefer to re-use.